Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

SIP Trunk Inbound Calls Failing

Discussion in '3CX Phone System - General' started by eQDoBBs, Jun 6, 2015.

Thread Status:
Not open for further replies.
  1. eQDoBBs

    Joined:
    Aug 14, 2012
    Messages:
    38
    Likes Received:
    3
    Hi

    We have just changed over to a SIP trunk provided by TalkTalk in the UK. The setup for this, is the following:

    EFM Circuit connects to RAD Router
    This connects to Adtran NetVanta 6310 (10.10.10.10 - (not real IP))
    This in turn connects to the 3CX server with direct cable connection (10.10.10.11)

    We were told by TalkTalk that when creating the SIP Trunk in 3CX we should not enter any authentication details. Adding the trunk in 3CX successfully connects and shows as registered. Updating the outbound call settings, allows outbound calls to be made successfully.

    However inbound calls are not working. The logs on 3CX are showing that the call is being routed to it, but the error is confusing as it refers to authentication issues. I am unsure where the registration issue is as the trunk is configured to 'Do Not Require' in the Advanced settings page, so no inbound or outbound registration should occur.

    Any help is much appreciated.

    ## Error Log Start ##

    06-Jun-2015 09:57:40.229 [CM102001]: Authentication failed for AuthFail Recv Req INVITE from 10.10.10.10:5060 tid=-dc93-35da0e3-6ea1278 Call-ID=49ed3e8-7f000001-13c4-dc93-ebeb0281-dc93@10.10.10.10:
    INVITE sip:5848@10.10.10.11:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bK-dc93-35da0e3-6ea1278
    Max-Forwards: 70
    Contact: <sip:01234567890@10.10.10.10:5060;transport=UDP>
    To: <sip:5848@10.10.10.11:5060>
    From: <sip:01234567890@10.10.10.10:5060;transport=UDP>;tag=49aa1e8-7f000001-13c4-dc93-9baa1256-dc93
    Call-ID: 49ed3e8-7f000001-13c4-dc93-ebeb0281-dc93@10.10.10.10
    CSeq: 2 INVITE
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
    Content-Type: application/sdp
    Proxy-Authorization: Digest username="",realm="3CXPhoneSystem",nonce="414d535c0b83470459:f0afb26395441b6321aa10b51f3938f0",uri="sip:5848@10.10.10.11:5060",response="12b6f69c20e0bafd337562b6b807026d",algorithm=MD5
    Supported: 100rel, replaces
    User-Agent: ADTRAN_Netvanta_6310/R10.9.4.E
    Content-Length: 177

    v=0
    o=Sonus_UAC 12114 14296 IN IP4 10.10.10.10
    s=SIP Media Capabilities
    c=IN IP4 10.10.10.10
    t=0 0
    m=audio 10002 RTP/AVP 8
    a=sendrecv
    a=ptime:20
    a=rtpmap:8 PCMA/8000
    ; Reason: Credentials don't match, check that authorization-ID and password match the ones in extension settings
    06-Jun-2015 09:57:40.229 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    Invite-UNK Recv Req INVITE from 10.10.10.10:5060 tid=-dc93-35da0e3-6ea1278 Call-ID=49ed3e8-7f000001-13c4-dc93-ebeb0281-dc93@10.10.10.10:
    INVITE sip:5848@10.10.10.11:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bK-dc93-35da0e3-6ea1278
    Max-Forwards: 70
    Contact: <sip:01234567890@10.10.10.10:5060;transport=UDP>
    To: <sip:5848@10.10.10.11:5060>
    From: <sip:01234567890@10.10.10.10:5060;transport=UDP>;tag=49aa1e8-7f000001-13c4-dc93-9baa1256-dc93
    Call-ID: 49ed3e8-7f000001-13c4-dc93-ebeb0281-dc93@10.10.10.10
    CSeq: 2 INVITE
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
    Content-Type: application/sdp
    Proxy-Authorization: Digest username="",realm="3CXPhoneSystem",nonce="414d535c0b83470459:f0afb26395441b6321aa10b51f3938f0",uri="sip:5848@10.10.10.11:5060",response="12b6f69c20e0bafd337562b6b807026d",algorithm=MD5
    Supported: 100rel, replaces
    User-Agent: ADTRAN_Netvanta_6310/R10.9.4.E
    Content-Length: 177

    v=0
    o=Sonus_UAC 12114 14296 IN IP4 10.10.10.10
    s=SIP Media Capabilities
    c=IN IP4 10.10.10.10
    t=0 0
    m=audio 10002 RTP/AVP 8
    a=sendrecv
    a=ptime:20
    a=rtpmap:8 PCMA/8000
    06-Jun-2015 09:57:40.229 [CM302002]: Authentication failed due to unidentified source of: SipReq: INVITE 5848@10.10.10.11:5060 tid=-dc93-35da0e3-6ea1278 cseq=INVITE contact=01234567890@10.10.10.10:5060 / 2 from(wire)
    06-Jun-2015 09:57:40.173 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:
    Invite-UNK Recv Req INVITE from 10.10.10.10:5060 tid=-dc93-35da0ac-1519bd3 Call-ID=49ed3e8-7f000001-13c4-dc93-ebeb0281-dc93@10.10.10.10:
    INVITE sip:5848@10.10.10.11:5060 SIP/2.0
    Via: SIP/2.0/UDP 10.10.10.10:5060;branch=z9hG4bK-dc93-35da0ac-1519bd3
    Max-Forwards: 70
    Contact: <sip:01234567890@10.10.10.10:5060;transport=UDP>
    To: <sip:5848@10.10.10.11:5060>
    From: <sip:01234567890@10.10.10.10:5060;transport=UDP>;tag=49aa1e8-7f000001-13c4-dc93-9baa1256-dc93
    Call-ID: 49ed3e8-7f000001-13c4-dc93-ebeb0281-dc93@10.10.10.10
    CSeq: 1 INVITE
    Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, PRACK, REFER, REGISTER
    Content-Type: application/sdp
    Supported: 100rel, replaces
    User-Agent: ADTRAN_Netvanta_6310/R10.9.4.E
    Content-Length: 177

    v=0
    o=Sonus_UAC 12114 14296 IN IP4 10.10.10.10
    s=SIP Media Capabilities
    c=IN IP4 10.10.10.10
    t=0 0
    m=audio 10002 RTP/AVP 8
    a=sendrecv
    a=ptime:20
    a=rtpmap:8 PCMA/8000

    ## end ##

    many thanks
     
  2. ian.watts

    ian.watts Active Member

    Joined:
    Apr 8, 2011
    Messages:
    532
    Likes Received:
    1
    Seems the root problem is with inbound call identification.
    3CX correctly will rejects inbound invites it cannot identify.

    You may need to add a From: Host Part to your Source ID section, dropping in your 10.10.10.10 bit.
    Likewise, requiring registration for either direction tends to get in the way with an IP-based "auth" setup (ugh.. so inflexible..), may want to require none.

    I'd start with those two. Typically I need to line up my DIDs with the format the provider sends in calls. Example: Flowroute sends BTN calls as 1aaannnnnnn but the DIDs themselves as +1bbbmmmmmmm.. was confusing the first time I was looking at why I saw calls coming in but the routing logic blocking or misrouting those incoming calls.. made it part of SOP to make a few test calls to verify the rules are functional.. varies with provider.
     
  3. eQDoBBs

    Joined:
    Aug 14, 2012
    Messages:
    38
    Likes Received:
    3
    Hi Ian,

    Many thanks for your reply. Your advice led me to the solution, which was to create a From: Host Part and enter a Custom IP with the Adtran IP as the value.

    thanks again

    Mark
     
    vwadher likes this.
  4. vwadher

    Joined:
    Mar 11, 2007
    Messages:
    17
    Likes Received:
    0
    Hello Mark, Can you please send me a screenshot of what you did? We are having the same issue on our AudioCodes. thank you!
     
Thread Status:
Not open for further replies.