Solved 3CX Engin, DID not forwarding to correct extension.

Status
Not open for further replies.

adsl

Bronze Partner
Basic Certified
Joined
May 16, 2012
Messages
5
Reaction score
1
I have inbound and outbound calls working ok with 3CX v15.x.
I have been using FreePBX in the past and use context=from-pstn-toheader to differentiate DID inbound numbers for Engin.
ie
0299995400 in dial to ext 100 (primary number and username)
0299995401 in dial to ext 101
0299995402 in dial to ext 102 etc.

On 3CX if I ring an inbound number such as 9999 9001 or 9999 9002 will end up on ext 100
Has anybody got 3CX inbound DID routing working and can you share your settings.

Here is a log of a phone call. IP and numbers changed to protect identity.
This is being picked up in the log.
Code:
P-Called-Party-ID: <sip:[email protected]>

The number being called is 0299995402 but it is not being diverted to the correct extension (in this case it should divert to ext 102).

so what do I have to change in 3CX to make the call divert to the correct extension.



p.s I have tried using 6129995402, 029995402 and  *9995402 as the inbound DID rule.



03/10/2019 1:37:34 AM – Leg L:10.2[Ivr:800] is terminated: Cause: BYE from local

03/10/2019 1:37:34 AM – [CM503008]: Call(C:10): Call is terminated

03/10/2019 1:37:34 AM – Leg L:10.1[Line:10000<<0424999999] is terminated: Cause: BYE from 203.161.164.69:5060

03/10/2019 1:37:30 AM – Currently active calls – 1: [10]

03/10/2019 1:37:29 AM – [CM503007]: Call(C:10): Ivr:800 has joined, contact <sip:[email protected]:5483>

03/10/2019 1:37:29 AM – [CM503007]: Call(C:10): Line:10000<<0424999999 has joined, contact <sip:[email protected]:5060>

03/10/2019 1:37:29 AM – L:10.2[Ivr:800] has joined to L:10.1[Line:10000<<0424999999]

03/10/2019 1:37:29 AM – [CM505001]: Endpoint Ivr:800: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:[email protected]:5060]

03/10/2019 1:37:29 AM – [CM503002]: Call(C:10): Alerting Ivr:800 by contact <sip:[email protected]:5483>

03/10/2019 1:37:29 AM – [CM503025]: Call(C:10): Calling T:Ivr:800@[Dev:sip:[email protected]:5483;rinstance=8f726c80a9a597db] for L:10.1[Line:10000<<0424999999]

03/10/2019 1:37:28 AM – [CM503027]: Call(C:10): From: Line:10000<<0424999999 ("0424999999" <sip:[email protected]:5060>) to T:Ivr:800@[Dev:sip:[email protected]:5483;rinstance=8f726c80a9a597db]

03/10/2019 1:37:28 AM – [CM503004]: Call(C:10): Route 1: from L:10.1[Line:10000<<0424999999] to T:Ivr:800@[Dev:sip:[email protected]:5483;rinstance=8f726c80a9a597db]

03/10/2019 1:37:28 AM – [Flow] Call(C:10): has built target endpoint: Ivr:800 for call from L:10.1[Line:10000<<0424999999]

03/10/2019 1:37:28 AM – [Flow] Target endpoint for 800 is Ivr:800

03/10/2019 1:37:28 AM – [CM503010]: Call(C:10): Making route(s) from Line:10000<<0424999999 to <sip:[email protected]:5060>

03/10/2019 1:37:28 AM – [CM505003]: Provider:[Engin] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]

03/10/2019 1:37:28 AM – [CM500002]: Call(C:10): Info on incoming INVITE from Line:10000<<0424999999:

Invite-IN Recv Req INVITE from 203.161.164.69:5060 tid=1pb1ut105gs3sn0n4h80.1 Call-ID=SDscfte01-ff28ed945c7500e0131704bb0fbc75eb-jm6gpa0010:

INVITE sip:[email protected]:5060;rinstance=777def88c837fbb9 SIP/2.0

Via: SIP/2.0/UDP 203.161.164.69:5060;branch=z9hG4bK1pb1ut105gs3sn0n4h80.1

Max-Forwards: 29

Contact: <sip:[email protected]:5060;transport=udp>

To: ". A COMPANY NAME"<sip:[email protected];rinstance=777def88c837fbb9>

From: <sip:[email protected];user=phone>;tag=SDscfte01-9228144-1552142248956-

Call-ID: SDscfte01-ff28ed945c7500e0131704bb0fbc75eb-jm6gpa0010

CSeq: 829527551 INVITE

Session-Expires: 1800;refresher=uas

Min-SE: 90

Accept: application/media_control+xml, application/sdp, multipart/mixed

Allow: ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, PRACK, REFER, NOTIFY, UPDATE

Content-Type: application/sdp

Supported: 100rel, timer

P-Called-Party-ID: <sip:[email protected]>

Recv-Info: x-broadworks-client-session-info

Content-Length: 367

v=0

o=BroadWorks 2560826635 1 IN IP4 203.161.164.69

s=-

c=IN IP4 203.161.164.69

t=0 0

m=audio 23658 RTP/AVP 8 18 0 101

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729/8000

a=fmtp:18 annexb=no

a=rtpmap:0 PCMU/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=silenceSupp:eek:ff – - – -

a=ptime:20

a=maxptime:30

a=sqn: 0

a=cdsc:1 image udptl t38

a=sendrecv

03/10/2019 1:37:28 AM – [CM503001]: Call(C:10): Incoming call from Line:10000<<0424999999 to <sip:[email protected]:5060>

03/10/2019 1:37:28 AM – Line limit check: Current # of calls for line Lc:10000(@Engin[<sip:[email protected]:5060>]) is 1; limit is 10

03/10/2019 1:37:28 AM – Timezone offset: 660 min.
 
That is the main after hours IVR for 0299995400 all 10 of the inbound numbers only go to the IVR instead of the extension assigned to the DID.
 
I figured it out:
In the SIP Trunk inbound Parameters
"CalledNum" number that has been dialed (default: To->user) needs to equal P-Called-PartyID : User Part

9767
 
  • Like
Reactions: YiannisH_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,916
Messages
589,719
Members
164,785
Latest member
Texas Clay -