Routing call problems to general extension

Status
Not open for further replies.

dcorazon

Silver Partner
Advanced Certified
Joined
Mar 12, 2020
Messages
26
Reaction score
4
Hello everyone,

I have a weird problem on 3 3cx servers (3 different clients) (with the same trunk operator)
For context, I am on self-hosted servers with a cloud provider. Iam using operator OVH as SIP trunk. On my 3 3cx servers I added the SIP trunk with a main number routing to the extension 000 (operator). I then have classic DIDs from the 3 operators. The main trunk number is not used, the same for the operator extension

The problem I encounter is that certain calls on an DID assigned for example to the extension 3008 arrive I don't know by what magic on the operator extension and given that the operator is not an extension used the calls are redirected to the operator extension's messaging system. What is surprising is that on the extension 3008, on its different statuses no redirection is made to the operator extension or other (same messaging level we do not have the announcement which suggests contacting the operator and when I look in the logs the calls do not go to the extension 3008 but go directly to the extension 0000 then to the VMail of 0000 as if the caller had dialed the main number of the trunk for example).

And I have this problem on each of the 3CX servers where I have OVH as operator.

Attached is a screenshot of today's Call logs, we see that the same number tried to reach her several times and later succeeded after several tries.

Still in the call logs we see that several calls were routed to operator extension 0000 while at no level (except at the trunk level with the main number) is there routing to the operator extension, and this is really random.
 

Attachments

  • Capture d'écran 2023-12-21 121124.png
    Capture d'écran 2023-12-21 121124.png
    76.8 KB · Views: 9
  • Capture d'écran 2023-12-21 120257.png
    Capture d'écran 2023-12-21 120257.png
    46.2 KB · Views: 9
I have just made a capture log and the calls which pose problems I have in destination "Anonymous" <sip:[email protected]>, except that a few minutes later the same number when he calls back manages to reach the extension so the question is to know if it comes from a configuration of my 3CX or if it is at the level of my SIP provider OVH.
Below is the packet capture. we see that in the SIP header at the new "To" field there is no number entered.
PS: i replaced the real numbers by XXXX

12/27/2023 10:13:41 AM - Call from "+339XXXX7007" <sip:[email protected];user=phone>;tag=24352-ZG-e27cde70-08bf34904 to "Anonymous"<sip:[email protected]>;tag=2b84c24a
12/27/2023 10:13:41 AM - Added leg L:C:126.1[No endpoint yet]
12/27/2023 10:13:41 AM - IncomingCall: C:126 from <sip:[email protected]:0/UDP> to <sip:[email protected]:5060/udp>
12/27/2023 10:13:41 AM - No inbound caller ID reformat rule for DN:10002 is defined, or it is disabled (<Rules />)
12/27/2023 10:13:41 AM - CallerNameAddr: "+339XXXX7007"<sip:09XXXX7007;nf=e>
12/27/2023 10:13:41 AM - [Flow] Looking for inbound target: called=anonymous; caller="+339XXXX7007" <sip:09XXXX7007@:0>
12/27/2023 10:13:41 AM - [CM503012]: Inbound specific hours w/o holidays rule (unnamed) for 10002 forwards to DN:0000
12/27/2023 10:13:41 AM - Dev(52655323):[sip:[email protected]:5060 / 0033XXXX70054]: PBX contact is public IP: <sip:[email protected]:5060/UDP>
12/27/2023 10:13:41 AM - Blacklist check: number '09XXXX7007', list: ''; result = false
12/27/2023 10:13:41 AM - Line limit check: Current # of calls for line Lc:10002(@ovh[<sip:[email protected]:5060/UDP>]) is 1; limit is 10
12/27/2023 10:13:41 AM - [CM503001]: Call(C:126): Incoming call from Line:10002<<09XXXX7007 to <sip:[email protected]:5060>


Content-Length: 319
Reason: sip;cause=404
User-Agent: Cirpack/v4.76 (gw_sip)
Content-Type: application/sdp
Allow: REFER, INVITE, NOTIFY, ACK, UPDATE, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, CANCEL, BYE, PRACK
CSeq: 1805940174 INVITE
Call-ID: [email protected]
From: "+339XXXX7007" <sip:[email protected];user=phone>;tag=24352-ZG-e27cde70-08bf34904
To: "Anonymous" <sip:[email protected]>
Contact: <sip:10.7.1.65:5060>
Record-Route: <sip:91.XXX.XXX.23:5060;lr>;session=538877
Max-Forwards: 29
Via: SIP/2.0/UDP 91.XXX.XXX.23:5060;branch=z9hG4bK-EFGU-5e4e7905-346f7834
INVITE sip:[email protected]:5060;transport=udp;rinstance=86cbacd07993e407 SIP/2.0
Invite-IN Recv Req INVITE from 91.XXX.XXX.23:5060 tid=-EFGU-5e4e7905-346f7834 Call-ID=[email protected]:
12/27/2023 10:13:41 AM - [CM500002]: Call(C:126): Info on incoming INVITE from Line:10002<<09XXXX7007:
12/27/2023 10:13:41 AM - Inbound DID: ''; Phonebook Name: ''
12/27/2023 10:13:41 AM - [CM505003]: Provider:[OVH] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
12/27/2023 10:13:41 AM - Remote SDP is set for leg L:126.1[Line:10002<<09XXXX7007]
12/27/2023 10:13:41 AM - [CM503010]: Call(C:126): Making route(s) from Line:10002<<09XXXX7007 to <sip:[email protected]:5060/UDP>
12/27/2023 10:13:41 AM - [Flow] Building target endpoint to 0000 from "+339XXXX7007" <sip:[email protected]:5060>
12/27/2023 10:13:41 AM - [Flow] Target endpoint for 0000 is Extn:0000
12/27/2023 10:13:41 AM - [Flow] Call(C:126): has built target endpoint: Extn:0000 for call from L:126.1[Line:10002<<09XXXX7007]
12/27/2023 10:13:41 AM - [Flow] Endpoint Extn:0000 has no forwarding rule on reason 'All calls'
12/27/2023 10:13:41 AM - [CM503017]: Call(C:126): Target is not registered: Extn:0000
12/27/2023 10:13:41 AM - [CM503016]: Call(C:126): Attempt to reach <sip:[email protected]:5060> from Line:10002<<09XXXX7007 has failed. Reason: Not Registered
12/27/2023 10:13:41 AM - Leg L:126.1[Line:10002<<09XXXX7007]: Refreshing OutCID from endpoint Extn:0000 = []
12/27/2023 10:13:41 AM - RerouteReq
12/27/2023 10:13:41 AM - L:126.1[Line:10002<<09XXXX7007] failed to reach Extn:0000, reason Not Registered
 
Do you have some Holiday setup?
12/27/2023 10:13:41 AM - [CM503012]: Inbound specific hours w/o holidays rule (unnamed) for 10002 forwards to DN:0000
 
I don't have Holiday setup neither on the global parameters nor on the DID rules (I've just checked all DID Rules, i've manually named all inbound rules for future use). And the only setting in wich i have 0000 configured is on trunk setting for the main trunck number wich is unused.
 

Attachments

  • 1703684773668.png
    1703684773668.png
    72 KB · Views: 2
  • 2Capture.PNG
    2Capture.PNG
    33.9 KB · Views: 2
Last edited:
Thanks for te help
I've checked the post and no. And the weird thing is that it's happen radomly.
And on the log file the first line containing the number is this (already sent it in previous post).
12/27/2023 10:13:41 AM - Call from "+339XXXX7007" <sip:[email protected];user=phone>;tag=24352-ZG-e27cde70-08bf34904 to "Anonymous"<sip:[email protected]>;tag=2b84c24a

down to the lines i sent is the logs for others calls
 
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet