Results 1 to 2 of 2

Thread: [SIP] Invalid SDP from terminator

  1. #1

    Default [SIP] Invalid SDP from terminator

    I'm moving our Epygy M32x (running firmware version 5.3.75) to a different location on a different subnet. Outgoing calls works as they should be, however external incoming calls are disconected as soon as the user tries to pickup the call. I have not changed anything other than the Epygi's WAN IP. I'm tearing my hair out trying to fix this!

    Some relevant info:
    • Handsets are SNOM 320 running version 8.4.35 (latest supported version by epygi)
    • Calls between handset works fine.
    • calls that get routed back out (i.e to mobiles if user is not at desk) works fine
    • [Internal] Calls to / from other Epygi unit works fine


    ITSP provided the below info on the cause of call disconect (what they can see from their end):

    Code:
    From the SIP logs file, I can see that call is being disconnected because of the Invalid SDP. Please find the following details for both 200 OK and 237 BYE.
    
        SIP/2.0 200 OK
        Via: SIP/2.0/UDP 203.176.185.26;branch=z9hG4bKdfb5.1f9e13f327ce4fb974c73d43de786060.0
        Via: SIP/2.0/UDP 175.45.127.201:5062;received=175.45.127.201;rport=5062;branch=z9hG4bK-571767192-3843100834-2361413535-749475168
        Record-Route: <sip:#ITSP sip server#:5060;transport=udp;lr>
        Record-Route: <sip:203.176.185.26;lr>
        Contact: "Anonymous"<sip:#ITSP sip server#:5061>
        To: <sip:#called number#@203.176.185.26;user=phone>;tag=ns6g2j4awxhtvkoc.i
        From: <sip:#caller number#@175.45.127.201:5062;user=phone>;tag=1022064792-3843100834-2361413535-749475168
        Call-ID: 9878eb5aa21011e59f4fc08c6015ac2c@175.45.127.201
        CSeq: 1 INVITE
        Content-Type: application/sdp
        Server: Sippy
        H323-credit-time: 21600
        Content-Length: 230
        
        v=0
        o=Sippy 496830480 1 IN IP4 #ITSP sip server#
        s=-
        t=0 0
        m=audio 0 RTP/AVP 8 0 18 101
        a=rtpmap:8 PCMA/8000
        a=rtpmap:0 PCMU/8000
        a=rtpmap:18 G729/8000
        a=fmtp:18 annexb=no
        a=rtpmap:101 telephone-event/8000
        a=fmtp:101 0-16
    
    BYE sip:#ITSP sip server#:5061 SIP/2.0
        Via: SIP/2.0/UDP 203.176.185.26;branch=z9hG4bKafb5.037f2688149301190c0a629a7e5a4de9.0
        Via: SIP/2.0/UDP 175.45.127.201:5062;received=175.45.127.201;rport=5062;branch=z9hG4bK-2524621977-3843100834-2361413535-749475168
        Max-Forwards: 69
        Route: <sip:#ITSP sip server#:5060;transport=udp;lr>
        To: <sip:#called number#@203.176.185.26;user=phone>;tag=ns6g2j4awxhtvkoc.i
        From: <sip:#caller number#@175.45.127.201:5062;user=phone>;tag=1022064792-3843100834-2361413535-749475168
        Call-ID: 9878eb5aa21011e59f4fc08c6015ac2c@175.45.127.201
        CSeq: 2 BYE
        User-Agent: TS-v4.5.1-18fW
        Reason: MVTSLocal;cause=85;text="[SIP] Invalid SDP from terminator", Q.850;cause=16;text="Normal call clearing"
        Content-Length: 0"
    The codec preference on the snom are: pcma, pcmu then 729.

    Incoming calls from two separate ITSP are haveing the same issue (one of the is more helpful with the log).

    I've searched everywhere and can't find where this SDO issue might be set / unset. I'm tearing my hair out.

    How do I fix up this "[SIP] Invalid SDP from terminator"?? Please help, Thank You.

  2. #2

    Default

    Did they tell exactly what is wrong in the SDP ???
    If not, let them tell.

    Looking at the SDP of SIP OK message, I do not see some important parameter:
    c=IN IP4 c=IN IP4 192.168.0.1
    Where IP address must be your public IP.

    Have you deleted it from the attached log just to hide your Ip or is it really missing???

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Invalid Extension for All SIP calls
    By islamhasan in forum Problem Report
    Replies: 1
    Last Post: 06-18-2012, 10:45 AM
  2. SIP Tunnel versus sip in routing rule
    By lambsons in forum Tips and Tricks
    Replies: 1
    Last Post: 08-31-2010, 04:58 AM
  3. the uploaded image is invalid
    By nitrox in forum Troubleshooting and Problems
    Replies: 1
    Last Post: 08-06-2009, 09:10 AM
  4. Default Auto Attendent Invalid Extension
    By brennja in forum Troubleshooting and Problems
    Replies: 5
    Last Post: 06-25-2008, 12:08 PM
  5. French Language pack invalid
    By dponzone in forum Troubleshooting and Problems
    Replies: 9
    Last Post: 03-07-2008, 01:14 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •