[SIPForum-discussion] SIP trunk heartbeat mechanism

Vijay Kumar vj.tech776 at gmail.com
Wed Oct 9 15:30:56 UTC 2013


UAC can send  a INVITE with MAX forwards=0 to a  SIP entity  which is next
hop and SIP entity  will send a 483 too many hops.


On Wed, Oct 9, 2013 at 11:38 AM, Vijay Badola <Vijay.Badola at onmobile.com>wrote:

>  I did not get it, if you can elaborate with some example it will be easy
> for me to understand.
>
>
>
>
>
>
>
> *From:* Vijay Kumar [mailto:vj.tech776 at gmail.com]
> *Sent:* Tuesday, October 08, 2013 5:53 PM
> *To:* Vijay Badola
> *Cc:* discussion at sipforum.org
>
> *Subject:* Re: [SIPForum-discussion] SIP trunk heartbeat mechanism
>
>
>
> Max forwards=0 works (expecting a 483 response as a heartbeat) if the next
> element is the node i.e the SUT.
>
> Regards
>
> Vijay
>
>
>
> On Tue, Oct 8, 2013 at 12:57 PM, Vijay Badola <Vijay.Badola at onmobile.com>
> wrote:
>
> Will it work if some intermediate SIP node rejects (by sending 483) before
> reaching to UAS or to desired SIP node?
>
>
>
> *From:* discussion-bounces at sipforum.org [mailto:
> discussion-bounces at sipforum.org] *On Behalf Of *Vijay Kumar
> *Sent:* Tuesday, October 01, 2013 10:50 PM
> *To:* discussion at sipforum.org
> *Subject:* Re: [SIPForum-discussion] SIP trunk heartbeat mechanism
>
>
>
> Hi
>
> You may use SIP INVITE message with
>
> Max forwards =0 and expect 483 Too Many Hops(heart beat)
>
> Regards
>
> Vijay
>
>
>  ------------------------------
>
>
> DISCLAIMER: The information in this message is confidential and may be
> legally privileged. It is intended solely for the addressee. Access to this
> message by anyone else is unauthorized. If you are not the intended
> recipient, any disclosure, copying, or distribution of the message, or any
> action or omission taken by you in reliance on it, is prohibited and may be
> unlawful. Please immediately contact the sender if you have received this
> message in error. Further, this e-mail may contain viruses and all
> reasonable precaution to minimize the risk arising there from is taken by
> OnMobile. OnMobile is not liable for any damage sustained by you as a
> result of any virus in this e-mail. All applicable virus checks should be
> carried out by you before opening this e-mail or any attachment thereto.
> Thank you - OnMobile Global Limited.
>
>
>
> ------------------------------
>
> DISCLAIMER: The information in this message is confidential and may be
> legally privileged. It is intended solely for the addressee. Access to this
> message by anyone else is unauthorized. If you are not the intended
> recipient, any disclosure, copying, or distribution of the message, or any
> action or omission taken by you in reliance on it, is prohibited and may be
> unlawful. Please immediately contact the sender if you have received this
> message in error. Further, this e-mail may contain viruses and all
> reasonable precaution to minimize the risk arising there from is taken by
> OnMobile. OnMobile is not liable for any damage sustained by you as a
> result of any virus in this e-mail. All applicable virus checks should be
> carried out by you before opening this e-mail or any attachment thereto.
> Thank you - OnMobile Global Limited.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20131009/5e715594/attachment-0002.html>


More information about the discussion mailing list