Solved Conference number will not work with DID

Status
Not open for further replies.

rjamesm2884

Free User
Basic Certified
Joined
Feb 23, 2019
Messages
174
Reaction score
16
We recently added a new DID and for some reason, it keeps diverting the call to the IVR. I have mapped everything on the conference side to go to the extension 700 and with the new DID.
If I call the 700 ext it connects me to the conference but if I call the DID number it will go to IVR. I restarted services and still the same problem. Any ideas?
 
Have you looked at the Activity log, for one of these calls, for any clues as to why the calls may be doing that?
 
Under inbound rules - you have the DID pointing to ext 700?
Screen Shot 2020-03-12 at 10.56.43 AM.png
 
Check the activity log to see how the DID is showing up.... I have * before the 10 digit number in the DID rules... *4805551212
 
I checked the activity log for some reason it diverts to 802 which is the IVR
 
03/12/2020 3:14:38 PM - [CM503002]: Call(C:1): Alerting Ivr:802 by contact <sip:[email protected]:5483/UDP>
03/12/2020 3:14:38 PM - [CM503025]: Call(C:1): Calling T:Ivr:802@[Dev:sip:[email protected]:5483;rinstance=c23dfde73200f34b] for L:1.1[Line:10001<<+1832XXXXXX]
03/12/2020 3:14:38 PM - [CM503027]: Call(C:1): From: Line:10001<<+18326602640 ("NAME,FIRST" <sip:[email protected]3cx.us:5060>) to T:Ivr:802@[Dev:sip:[email protected]:5483;rinstance=c23dfde73200f34b]
03/12/2020 3:14:38 PM - [CM503004]: Call(C:1): Route 1: from L:1.1[Line:10001<<+1832XXXXXX] to T:Ivr:802@[Dev:sip:[email protected]:5483;rinstance=c23dfde73200f34b]
03/12/2020 3:14:38 PM - [Flow] Call(C:1): has built target endpoint: Ivr:802 for call from L:1.1[Line:10001<<+1832XXXXXXX]
03/12/2020 3:14:38 PM - [Flow] Target endpoint for 802 is Ivr:802
 
03/12/2020 3:14:38 PM - [CM503002]: Call(C:1): Alerting Ivr:802 by contact <sip:[email protected]:5483/UDP>
03/12/2020 3:14:38 PM - [CM503025]: Call(C:1): Calling T:Ivr:802@[Dev:sip:[email protected]:5483;rinstance=c23dfde73200f34b] for L:1.1[Line:10001<<+1832XXXXXX]
03/12/2020 3:14:38 PM - [CM503027]: Call(C:1): From: Line:10001<<+18326602640 ("NAME,FIRST" <sip:[email protected]3cx.us:5060>) to T:Ivr:802@[Dev:sip:[email protected]:5483;rinstance=c23dfde73200f34b]
03/12/2020 3:14:38 PM - [CM503004]: Call(C:1): Route 1: from L:1.1[Line:10001<<+1832XXXXXX] to T:Ivr:802@[Dev:sip:[email protected]:5483;rinstance=c23dfde73200f34b]
03/12/2020 3:14:38 PM - [Flow] Call(C:1): has built target endpoint: Ivr:802 for call from L:1.1[Line:10001<<+1832XXXXXXX]
03/12/2020 3:14:38 PM - [Flow] Target endpoint for 802 is Ivr:802
I don't understand why this is behaving this way. I already rebooted the server still same issues.
 
And the number used in your DID rules matches exactly, the incoming DID number? If it doesn't, or no DID information available, then the call will follow the default route.
 
Try using the same rule and sending that DID to a "regular"extension, see if that works.
 
Try using the same rule and sending that DID to a "regular"extension, see if that works.
Just did. It still goes to the IVR.
 
Then the incoming DID is not following the rule because it cannot match the number. Do other DIDs work correctly? Have you used wildcards?
 
There is only two DID the main IVR DID and a Conference Call DID. No wild cards used.
 
Do you use any other DID rules that work? You know for certain that you have DID service (number dialled being sent along with caller ID).? If you don't specifically subscribe to this service, then you may not have it.
 
Do you use any other DID rules that work? You know for certain that you have DID service (number dialled being sent along with caller ID).? If you don't specifically subscribe to this service, then you may not have it.
No like I said only two DID rules IVR and Conference Calls. The IVR works if I dial 700 internally I can get to the conference line. If I dial the DID for the conference calls the system diverts it to the IVR.
 
Ok SIPTRUNK.com was able to find the issue. It was a setting in the Sip Trunk INBOUND PARAMETERS "CalledNum" number that has been dialed (default: To->user) ---> REQUEST LINE URI: USER PART.

Problem solved. Thanks, everyone who replied and was able to help in any way. Very much appreciated!
 
  • Like
Reactions: YiannisH_3CX
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,939
Messages
589,844
Members
164,826
Latest member
Ravex comms