Toggle sidebar Toggle sidebar

Not able to route DID assigned numbers to user extension

kkchee

Bronze Partner
Basic Certified
Joined
Jul 1, 2022
Messages
9
Reaction score
0
After upgraded to V20 system was not able to route the DID to the user extension. Everything routed to the default route in the SIP trunk.

1731467939613.png



1731467968571.png
 
Your DID couldnt be ok like this. check your logs what is happend.
 
@kkchee I see that you're using a PRI gateway in v20, and I've encountered a similar issue with PRI gateways where calls are routed to the default route from the trunk. To address this, try setting the default route to "End Call" and assigning the DIDs directly to the agents. This approach has helped me to resolve the same issue for my customer's 3CX. Let me know if this works for you!
 
AshishKushwaha said:
@kkchee I see that you're using a PRI gateway in v20, and I've encountered a similar issue with PRI gateways where calls are routed to the default route from the trunk. To address this, try setting the default route to "End Call" and assigning the DIDs directly to the agents. This approach has helped me to resolve the same issue for my customer's 3CX. Let me know if this works for you!
Click to expand...
Thanks @AshishKushwaha. I have followed your advice and still the same issue. It can't route to the users and all calls are ended.
 
bitn2 said:
Your DID couldnt be ok like this. check your logs what is happend.
Click to expand...
Thanks @bitn2 .
Here is what the logs captured:

Lsip{3778696/4060.1/UAS*[Connected&Neutral]} termination message:
InvTERM Recv Req BYE from 172.20.3.253:5060 tid=1d0891ea Call-ID=[email protected]:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK1d0891ea
Max-Forwards: 70
To: <sip:[email protected]>;tag=4c29f30b
From: "0123666498"<sip:[email protected]>;tag=as05debf24
Call-ID: [email protected]
CSeq: 104 BYE
Proxy-Authorization: Digest username="10000",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]:5060",nonce="414d535c1d450e7b37:c9227b0878f076a08ac412642483795a",response="4a17a137b650cbf2bcd9ab9425799d11"
User-Agent: Digium Gateway
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

11/13/2024 6:20:46.836 PM Lsip{3778696/4060.1/UAS*[Connected&Neutral]} sends: SendResp Send 200/BYE from 0.0.0.0:0 tid=1d0891ea Call-ID=[email protected]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK1d0891ea
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=4c29f30b
From: "0123666498"<sip:[email protected]>;tag=as05debf24
Call-ID: [email protected]
CSeq: 104 BYE
Content-Length: 0

11/13/2024 6:20:46.836 PM L:4060.1[Line:10000<<0123666498{5c49f265f157}] onReadyToSend: Send Send 200/BYE from 0.0.0.0:0 tid=1d0891ea Call-ID=[email protected]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK1d0891ea
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=4c29f30b
From: "0123666498"<sip:[email protected]>;tag=as05debf24
Call-ID: [email protected]
CSeq: 104 BYE
Content-Length: 0

11/13/2024 6:20:46.835 PM Checking for authentication of Auth Recv Req BYE from 172.20.3.253:5060 tid=1d0891ea Call-ID=[email protected]:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK1d0891ea
Max-Forwards: 70
To: <sip:[email protected]>;tag=4c29f30b
From: "0123666498" <sip:[email protected]>;tag=as05debf24
Call-ID: [email protected]
CSeq: 104 BYE
Proxy-Authorization: Digest username="10000",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]:5060",nonce="414d535c1d450e7b37:c9227b0878f076a08ac412642483795a",response="4a17a137b650cbf2bcd9ab9425799d11"
User-Agent: Digium Gateway
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

11/13/2024 6:20:43.710 PM Lsip{3778696/4060.1/UAS*[Connected&Neutral]}: confirmed:
InvIN Recv Req ACK from 172.20.3.253:5060 tid=4a006651 Call-ID=[email protected]:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK4a006651
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=4c29f30b
From: "0123666498" <sip:[email protected]>;tag=as05debf24
Call-ID: [email protected]
CSeq: 103 ACK
User-Agent: Digium Gateway
Content-Length: 0

11/13/2024 6:20:43.699 PM Lsip{3778696/4060.1/UAS*[Sent200OK&AnswerSent]} Updated contact: <sip:[email protected]:5060>
11/13/2024 6:20:43.699 PM Lsip{3778696/4060.1/UAS*[Sent200OK&AnswerSent]} Updating target <sip:[email protected]:0> with "" user = 8997
11/13/2024 6:20:43.698 PM Lsip{3778696/4060.1/UAS*[Sent200OK&AnswerSent]}: connected
InvIN Send 200/INVITE from 0.0.0.0:0 tid=7bdf3178 Call-ID=[email protected]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK7bdf3178
Require: timer
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=4c29f30b
From: "0123666498"<sip:[email protected]>;tag=as05debf24
Call-ID: [email protected]
CSeq: 103 INVITE
Session-Expires: 1800;refresher=uac
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 20.0.3.806 (806)
Content-Length: 280

I'm not sure if i missed out anything from the logs. Can you advise if anything amiss or misconfigured in 3CX? I'm really bummed out by this new v20.
 
You have a DID defined ending in 802, yet the invite coming in is ending in 801.

kkchee said:
I'm really bummed out by this new v20.
Click to expand...
The PBX is receiving a call from a DID that it is not configured to process. How is this the fault of Version 20 is beyond me.
 
  • Like
Reactions: bitn2
NicholasP_3CX said:
You have a DID defined ending in 802, yet the invite coming in is ending in 801.


The PBX is receiving a call from a DID that it is not configured to process. How is this the fault of Version 20 is beyond me.
Click to expand...
Thanks @NicholasP_3CX for your advice. I've mistakenly posted a log which captured for the configured 801 DID. I have defined DIDs for 802 & 801. It was my silly mistake posting the logs for 801 which differ from my screenshot configuration.
 
Define the DIDs as *3801 and *3802 and see if that makes a difference.
 
NicholasP_3CX said:
Define the DIDs as *3801 and *3802 and see if that makes a difference.
Click to expand...
I have tried to define the DID as recommended and it doesn't seems to make a difference.

Here are the logs capture:

11/13/2024 10:07:51.322 PM Lsip{3794279/4075.1/UAS*[Connected&Neutral]} termination message:
InvTERM Recv Req BYE from 172.20.3.253:5060 tid=07175f14 Call-ID=[email protected]:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK07175f14
Max-Forwards: 70
To: <sip:[email protected]>;tag=b21f840e
From: "0123666498"<sip:[email protected]>;tag=as1562021b
Call-ID: [email protected]
CSeq: 104 BYE
Proxy-Authorization: Digest username="10000",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]:5060",nonce="414d535c1d4543b097:c61361e999e15e9849c30d892bc08d75",response="4cb5ec7c95025e4c4ee31e7a224b4f47"
User-Agent: Digium Gateway
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

11/13/2024 10:07:51.322 PM Lsip{3794279/4075.1/UAS*[Connected&Neutral]} sends: SendResp Send 200/BYE from 0.0.0.0:0 tid=07175f14 Call-ID=[email protected]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK07175f14
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=b21f840e
From: "0123666498"<sip:[email protected]>;tag=as1562021b
Call-ID: [email protected]
CSeq: 104 BYE
Content-Length: 0

11/13/2024 10:07:51.321 PM L:4075.1[Line:10000<<0123666498{136d45653149}] onReadyToSend: Send Send 200/BYE from 0.0.0.0:0 tid=07175f14 Call-ID=[email protected]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK07175f14
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=b21f840e
From: "0123666498"<sip:[email protected]>;tag=as1562021b
Call-ID: [email protected]
CSeq: 104 BYE
Content-Length: 0

11/13/2024 10:07:51.321 PM Checking for authentication of Auth Recv Req BYE from 172.20.3.253:5060 tid=07175f14 Call-ID=[email protected]:
BYE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK07175f14
Max-Forwards: 70
To: <sip:[email protected]>;tag=b21f840e
From: "0123666498" <sip:[email protected]>;tag=as1562021b
Call-ID: [email protected]
CSeq: 104 BYE
Proxy-Authorization: Digest username="10000",realm="3CXPhoneSystem",algorithm=MD5,uri="sip:[email protected]:5060",nonce="414d535c1d4543b097:c61361e999e15e9849c30d892bc08d75",response="4cb5ec7c95025e4c4ee31e7a224b4f47"
User-Agent: Digium Gateway
X-Asterisk-HangupCause: Normal Clearing
X-Asterisk-HangupCauseCode: 16
Content-Length: 0

11/13/2024 10:07:45.260 PM Lsip{3794279/4075.1/UAS*[Connected&Neutral]}: confirmed:
InvIN Recv Req ACK from 172.20.3.253:5060 tid=55582816 Call-ID=[email protected]:
ACK sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK55582816
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=b21f840e
From: "0123666498" <sip:[email protected]>;tag=as1562021b
Call-ID: [email protected]
CSeq: 103 ACK
User-Agent: Digium Gateway
Content-Length: 0

11/13/2024 10:07:36.152 PM Lsip{3794279/4075.1/UAS*[Sent200OK&AnswerSent]} Updated contact: <sip:[email protected]:5060>
11/13/2024 10:07:29.932 PM Lsip{3794279/4075.1/UAS*[Sent200OK&AnswerSent]} Updating target <sip:[email protected]:0> with "" user = 8997
11/13/2024 10:07:45.060 PM Lsip{3794279/4075.1/UAS*[Sent200OK&AnswerSent]}: connected
InvIN Send 200/INVITE from 0.0.0.0:0 tid=741ff67f Call-ID=[email protected]:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.20.3.253:5060;branch=z9hG4bK741ff67f
Require: timer
Contact: <sip:[email protected]:5060>
To: <sip:[email protected]>;tag=b21f840e
From: "0123666498"<sip:[email protected]>;tag=as1562021b
Call-ID: [email protected]
CSeq: 103 INVITE
Session-Expires: 1800;refresher=uac
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Content-Type: application/sdp
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 20.0.3.806 (806)
Content-Length: 279

v=0
o=3cxPS 240065183744 45919240193 IN IP4 172.20.201.86
s=3cxPS Audio call
c=IN IP4 172.20.201.86
t=0 0
m=audio 8430 RTP/AVP 8 0 9 3 101
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:9 G722/8000
a=rtpmap:3 GSM/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

The DID defined as advised:

1731507281002.png
I was trying to define *3802* to see if that makes a different and it's the same.
 
Could you please check and capture the PCAP logs from both the PRI gateway and the 3CX side to verify if the DIDs are coming through correctly? Sometimes the PRI gateway replaces the dialed DID with the pilot DID because of the outbound and inbound rule configured on the PRI gateway, which could be causing calls to follow the default route.
 
You must log in or register to reply here.

Latest Posts

Forum statistics

Threads
111,956
Messages
589,927
Members
164,859
Latest member
MichaelRussell3
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom