[Freeswitch-dev] SIP 503 instead of 480 when fsctl pause

Anthony Minessale anthony.minessale at gmail.com
Mon Apr 7 13:07:12 EDT 2008

ok sure,
update to 8047 and we will send 503

On Mon, Apr 7, 2008 at 11:47 AM, Zelei Csaba <csaba.zelei at gmail.com> wrote:

> Hi all,
> Recently we had a scenario where a cisco router proxy calls to FS servers.
> If we issue fsctl pause (we would like to stop one of the proxy due to
> maintenance) then it send 480 SIP messages back to the cisco which hangup on
> the call.
> We tried it with 503 instead of 480 and in this case the cisco tried the
> next route.
> According to SIP rfc 480 used when "The callee's end system was contacted
> successfully but the callee is currently unavailable" while 503 used when
> "The server is temporarily unable to process the request due to a temporary
> overloading or maintenance of the server"
> Wouldn't it be better to use 503 instead of 480 when the server is goind
> down for maintenance?
> Thanks in advance,
> Csaba Zelei
> _______________________________________________
> Freeswitch-dev mailing list
> Freeswitch-dev at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
> http://www.freeswitch.org

Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/

AIM: anthm
MSN:anthony_minessale at hotmail.com <MSN%3Aanthony_minessale at hotmail.com>
GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com<PAYPAL%3Aanthony.minessale at gmail.com>
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888 at conference.freeswitch.org <sip%3A888 at conference.freeswitch.org>
iax:guest at conference.freeswitch.org/888
googletalk:conf+888 at conference.freeswitch.org<googletalk%3Aconf%2B888 at conference.freeswitch.org>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20080407/eeb1f2a8/attachment-0001.html 

More information about the Freeswitch-dev mailing list