SIP Trunk Problem: Message Option 200 (heartbeat)

Home » Asterisk Users » SIP Trunk Problem: Message Option 200 (heartbeat)
Asterisk Users 1 Comment

Hello;
I am facing a trouble with the SIP service provider, they are saying that there is a problem related to message option 200 (the heartbeat), so what is required to add this for the sip configuration? Below is my sip debug trace log with the them and the sip peer configuration:

[Sep  4 12:42:18]<------------>

[Sep  4 12:42:18]Scheduling destruction of SIP dialog’kntaydtnxawwiyky4yaadanied4lk4ys@139.110.215.10′ in 32000 ms (Method: OPTIONS)

[Sep  4 12:42:19]Really destroying SIP dialog ‘xidaktlblveesdlbtkbyyexelaiibtvx@139.110.215.10’Method: OPTIONS

[Sep  4 12:42:20]

[Sep  4 12:42:20] <--- SIP read fromUDP:10.215.110.139:5060 --->

[Sep  4 12:42:20] OPTIONS sip:10.240.147.26:5060SIP/2.0

[Sep  4 12:42:20] Via: SIP/2.0/UDP10.215.110.139:5060;branch=z9hG4bKxlaisbketikainbbedltysdla;Role=3;Hpt=8e78_16;TRC=ffffffff-ffffffff;pth=0;X-HwDim=4

[Sep  4 12:42:20] Call-ID:aecdkcavavdticeydtswaewesttbbad4@139.110.215.10

[Sep  4 12:42:20] From:;tag=yaekiyny

[Sep  4 12:42:20] To:

[Sep  4 12:42:20]CSeq: 1 OPTIONS

[Sep  4 12:42:20]Contact:;expires=65535

[Sep  4 12:42:20]Accept: application/sdp

[Sep  4 12:42:20]Max-Forwards: 70

[Sep  4 12:42:20]Content-Length: 0

[Sep  4 12:42:20]

[Sep  4 12:42:20] <------------->

[Sep  4 12:42:20] — (10 headers 0 lines) –

One thought on - SIP Trunk Problem: Message Option 200 (heartbeat)

  • OPTIONS is treated as if it were an INVITE, so it looks up the extension in the dialplan. The following shows what extension and context:

    [Sep 4 12:42:20] Looking for s in trunkinbound (domain 10.240.147.26)

    If you add an “s” extension to the “trunkinbound” context it should then respond 200 OK.

    —
    Joshua C. Colp Digium – A Sangoma Company | Senior Software Developer
    445 Jan Davis Drive NW – Huntsville, AL 35806 – US
    Check us out at: http://www.digium.com & http://www.asterisk.org

    —