Identification DID in SIP packet

Discussion in '3CX Phone System - General' started by pehavel, May 31, 2017.

Tags:
Thread Status:
Not open for further replies.
  1. pehavel

    Joined:
    May 31, 2017
    Messages:
    6
    Likes Received:
    0
    Hello,

    I have problem with identification DID from SIP packet (Sip Trunks).

    Correct number for DID is show only in fields INVITE and x-DDI, but no one can be selected on setting "Look for the DID number in these fields".

    Log (selected DID number bold):
    • 05/31/2017 11:13:24 PM - [CM500002]: Call(C:21): Info on incoming INVITE from Line:10000<<494111222:
    • Invite-IN Recv Req INVITE from 222.222.222.222:5060 tid=a1b2c3 Call-ID=3b5ab1453d67XXX@217.11.11.11:
    • INVITE sip:494909108@40.50.60.70:5060;rinstance=sdfasdfasdfasdfad;nat=yes SIP/2.0
    • Via: SIP/2.0/UDP 222.222.222.222:5060;branch=12abc123abc
    • Via: SIP/2.0/UDP 200.200.200.200:5566;received=217.11.11.11;branch=12abc123abc123abc;rport=5566
    • Max-Forwards: 69
    • Record-Route: <sip:217.11.11.11;lr>
    • Contact: <sip:494111222@200.200.200.200:5566>
    • To: <sip:1033625080@217.11.11.11>
    • From: <sip:494111222@200.200.200.200:5566>;tag=as36a6ec68
    • Call-ID: 3b5ab1453d67XXX@217.11.11.11
    • CSeq: 102 INVITE
    • Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    • Content-Type: application/sdp
    • Date: Wed, 31 May 2017 21:13:24 GMT
    • Supported: replaces, timer
    • User-Agent: ha-loo.cz
    • x-DDI: 494909108
    • Content-Length: 359
    I need identificate DID from for example row x-DDI.
    How can I do it?
     
  2. craigreilly

    craigreilly Well-Known Member

    Joined:
    Feb 1, 2012
    Messages:
    2,947
    Likes Received:
    179
    Are you using an unsupported provider?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. pehavel

    Joined:
    May 31, 2017
    Messages:
    6
    Likes Received:
    0
    Yes, I using an unsupported provider. In Czech Republic is only one supported provider (small choice).
     
  4. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,349
    Likes Received:
    274
    Hello @pehavel

    Are you having source identification issues? What kind of issue are you facing exactly? From what i can see from the provided logs your provided is Authentication based and is using rInstance.
    When rInstance is present then there is no need to adjust the "Look for the DID number in these fields" in the Inbound parameters as that is used to let the PBX know to which trunk the incoming call belongs to and route it accordingly if rInstance is not present.
     
  5. pehavel

    Joined:
    May 31, 2017
    Messages:
    6
    Likes Received:
    0
    Hello

    I have problem with identification Called number (or Dial number) from the outside network. In VoIP provider "Ha-loo Centrála" I have several phone numbers in one profil and these numers has common one SIP Trunk registration in 3CX pbx. But pxb don't know, which number is dial.

    In rinstace field is string 37d573bfdba60bb2 and it is still same for any Called number. I can't use this string for indentification Called number.

    In sample SIP Caller number is bold (494909108). I need to route incoming calls according to this number.

    Thank you for help.
     
  6. YiannisH_3CX

    YiannisH_3CX Support Team
    Staff Member 3CX Support

    Joined:
    May 10, 2016
    Messages:
    4,349
    Likes Received:
    274
    You do not need to to use rInstance to identify the numbers, the PBX does that automatically. I believe your issue is with inbound rules not source identification. Try adding the DID's under the trunk with a * character in front of the number so no matter how the number arrives at the PBX it will match your DID's. For example if your DID is 494909108 then your DID should be *4909108. Then create your inbound rules using the new numbers.
     
  7. pehavel

    Joined:
    May 31, 2017
    Messages:
    6
    Likes Received:
    0
    Problem istn't in inbound rules.

    Now I solved problem: for right identification of Called number I must set in SIP Trunk → Inbound Parameters → "CalledNum" number that has been dialed (default: To->user) value Request Line URI : User Part.
    Now is route incoming calls right by inbound rules.

    In log is now right record: [Flow] Looking for inbound target: called=494909108; caller=<sip:494111222@:5060> (before change: [Flow] Looking for inbound target: called=1033625080; caller=<sip:494111222@:5060>)
     
Thread Status:
Not open for further replies.