[SIPForum-discussion] SIP trunk heartbeat mechanism

[Abhisek Acharya]

Bro

I believe RFC 3261 is not  vocal about use of OPTION method as a keep alive
mechanism between nodes.but regarding your question if OPTION gets a 503
what should
SIP server do.

My answer is SIP server assume that the connection is up and running and it
should not mark the connection down as 503 response it self suggests that
OPTION request reached the far end node and far end node replied with a 503
response.

But at times implementation might require a 200 OK response instead of any
other response to mark the connection up and running.


One question is it that your SIP server is marking the connection down up
on receiving 503 ?if yes that might be the way it has been implemented.And
can you send an OPTION to your SIP server manually say from a SIPP script
and see what response it sends.

Lemme know what do you think about this issue


Regards
Abhisek Acharya.









On Wed, Sep 25, 2013 at 7:51 AM, Federico Aicardi <faicardi at gmail.com>wrote:

> Hello all,
>
> I would like to know if there is some RFC that describes the heartbeat
> mechanism in a SIP trunk (device level heartbeat).
> Particularly, I have a doubt, the scenario is the following,
>
>    1. SIP server sends the OPTION heartbeat message
>    2. IP PBX responds with a 503 "Service unavailable"
>
> SIP server should assume that the SIPTG is down or the status should be
> normal as the peer device responds? Is there any RFC which specifies this
> procedure?
>
> Thanks to all.
>
> Best regards,
> Federico
>
>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20130930/81224d53/attachment-0002.html>