Toggle sidebar Toggle sidebar

All inbound calls go to voicemail

Status
Not open for further replies.

ajnewtexas

Forum User
Joined
Jul 21, 2016
Messages
37
Reaction score
1
Windows install. Latest 16 3cx.

I've had a weird issue in the last 48 hours. No changes I can point to.

All inbound calls go to voicemail or don't connect. Restarted Routers, modem, Windows host, ect. Double checked to make sure all exts were set to Available.

Outbound has no issues.

Any place to start trying to fix this? Working with my ISP and SIPTRUNK to insure inbound 506o traffic is unencumbered.

Thank you!
 
voicemail are from 3cx extensionst or from sip provider ?

what is your common call flow?
 
3cx...I can play/listen to them without issue.
 
can you share screen copy of inbound rule?
 
  • 3CX Version, Enterprise Annual 16.0.504
  • Server OS Windows 10 Pro
  • Is the 3CX Server Hosted and where? Windows 10 Pro box in office
  • IP Phone Make/Model/Firmware : Yealinks T48G/T46S on latest 35.83.0.130 / and Windows Softphone/ IOS Softphones
  • Provisioning Method: Local
  • Trunk Provider or Gateway Make/Model :SIPTrunk
  • Has the Firewall Checker passed: YES
  • Are custom Phone Templates being used: NO
All services running
 
What does the 3CX Activity Log look like, for an incoming call, to an extension, that shows status as registered?
 
Seeing this when calls come in:

04/08/2020 4:21:46 PM - NAT/ALG check:L:2.1[Line:10000<<3607552760] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 205.251.137.154;branch=z9hG4bK1983.e65ccf9dd31da837b222aa54d3c53c5b.1 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK08B539fd3823dbe2f6e
04/08/2020 4:21:43 PM - NAT/ALG check:L:1.1[Line:10000<<3607552760] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 63.247.69.226;branch=z9hG4bKc432.cc6203f0dc19fb7a2243e2d316c86379.1 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK00B6e381c79b2d7360f
 
Some more logs from a call that bounced around:

04/08/2020 7:48:25 PM - [CM503021]: Call(C:3): ACK is not received from sip:[email protected]
04/08/2020 7:47:53 PM - [CM503003]: Call(C:3): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 192.168.40.13:5060
04/08/2020 7:47:36 PM - Call to T:RingAll:800@[Dev:sip:[email protected]:5060] from L:4.1[Line:10000<<8552238053] failed, cause: Cause: 486 Busy Here/INVITE from 192.168.40.20:5060
04/08/2020 7:47:36 PM - [CM503003]: Call(C:4): Call to <sip:[email protected]:0> has failed; Cause: 486 Busy Here/INVITE from 192.168.40.20:5060
04/08/2020 7:47:35 PM - NAT/ALG check:L:4.1[Line:10000<<8552238053] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 205.251.137.154;branch=z9hG4bKd9ba.c62e5f5cb2a75c92a7eb180b2607fed5.1 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK04B96ade32998d77133
04/08/2020 7:47:32 PM - Call to T:RingAll:800@[Dev:sip:[email protected]:5060,Dev:sip:[email protected]:5060] from L:3.1[Line:10000<<8552238053] failed, cause: Cause: 486 Busy Here/INVITE from 192.168.40.20:5060
04/08/2020 7:47:32 PM - [CM503003]: Call(C:3): Call to <sip:[email protected]:0> has failed; Cause: 486 Busy Here/INVITE from 192.168.40.20:5060
04/08/2020 7:47:32 PM - NAT/ALG check:L:3.1[Line:10000<<8552238053] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 63.247.69.226;branch=z9hG4bK4ad8.ef68c9925469f65ddbf8eeaec1b44f6c.0 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK08Bb0e273c484edf1be
 
Screen Shot 2020-04-08 at 8.50.39 PM.pngHere's an image for it in the call log
 
Seeing these failed after restarting services:
04/08/2020 8:42:52 PM - UDP transport is joined to SIP multicast group on interface 127.0.0.1
04/08/2020 8:42:52 PM - Failed to join UDP transport to SIP multicast group on interface 169.254.54.195. Err code 10049
04/08/2020 8:42:52 PM - Failed to join UDP transport to SIP multicast group on interface 169.254.5.78. Err code 10049
04/08/2020 8:42:52 PM - Failed to join UDP transport to SIP multicast group on interface 169.254.241.175. Err code 10049
04/08/2020 8:42:52 PM - Failed to join UDP transport to SIP multicast group on interface 169.254.130.38. Err code 10049
04/08/2020 8:42:52 PM - UDP transport is joined to SIP multicast group on interface 192.168.40.73
04/08/2020 8:42:51 PM - License loaded sucessfully. License level: 3
04/08/2020 8:42:51 PM - Folder for SSL certificates : C:\ProgramData\3CX\Instance1\Bin\Cert
04/08/2020 8:42:51 PM - ** Initializing SIP stack **
04/08/2020 8:42:51 PM - Local IP addresses detected: [169.254.130.38,169.254.241.175,169.254.5.78,169.254.54.195,192.168.40.73]



These 169 addresses aren't on my network. Could these be the inbound failure/ loop?
 
Inbound rule:
Screen Shot 2020-04-08 at 9.12.50 PM.png
 
If you hear the 3CX Voicemail box, the calls are not failing.

Check your routing and ensure your are not in "out of office hours" or forced out of office mode.

Change your inbound rule to go to an extension that you know can receive calls, and is in the available Status currently. See the extension's Available status forwarding rules if in doubt of routing, and force it into Available using the status button in your management console's Extensions section. You should be able to receive the calls normally at this point
 
do you have multiple NICs in your PBX server?
I think the 169 address is the multicast address in this case.
But can also if it is on a real NIC be a self assigned IP address if the interfaces is requesting it via DHCP and couldn't get one.
 
and you run the PBX on Windows 10 PRO? that is not really a server platform. But then I don' know if that is supported or not - not a windows guy for this.

P.S. just checked it is actually supported. I am surprised.
 
JohnS_3CX said:
If you hear the 3CX Voicemail box, the calls are not failing.

Check your routing and ensure your are not in "out of office hours" or forced out of office mode.

Change your inbound rule to go to an extension that you know can receive calls, and is in the available Status currently. See the extension's Available status forwarding rules if in doubt of routing, and force it into Available using the status button in your management console's Extensions section. You should be able to receive the calls normally at this point
Click to expand...

Same issue when assigned to a single ext and not a Ring Group...What info can I get you to fix this?

From Activity Log:
04/09/2020 9:32:23 AM - [CM503003]: Call(C:9): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 192.168.40.19:5060
04/09/2020 9:32:23 AM - [CM503003]: Call(C:9): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.40.167:54502
04/09/2020 9:32:06 AM - NAT/ALG check:L:10.1[Line:10000<<3258649365] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 205.251.137.154;branch=z9hG4bK09f5.883e9d0146ddbe8fe68bdc8cbb6a9d80.1 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK0cB999a2ab6993e2f41
04/09/2020 9:32:03 AM - NAT/ALG check:L:9.1[Line:10000<<3258649365] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 63.247.69.226;branch=z9hG4bKe4f1.5fe24eb0406ad3330ba573e46f218f74.0 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK00B9776937a0ab5b0a9
 
AlexanderReichert said:
do you have multiple NICs in your PBX server?
I think the 169 address is the multicast address in this case.
But can also if it is on a real NIC be a self assigned IP address if the interfaces is requesting it via DHCP and couldn't get one.
Click to expand...
Only the single NIC on the Windows 10 Pro box
 
One more line added to the The incoming call. The Inbound rule is set to ring ext 103. Call is coming in from 3258649365

04/09/2020 9:32:55 AM - [CM503021]: Call(C:9): ACK is not received from sip:[email protected]
04/09/2020 9:32:23 AM - [CM503003]: Call(C:9): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Cancelled/INVITE from 192.168.40.19:5060
04/09/2020 9:32:23 AM - [CM503003]: Call(C:9): Call to <sip:[email protected]:0> has failed; Cause: 487 Request Terminated/INVITE from 192.168.40.167:54502
04/09/2020 9:32:06 AM - NAT/ALG check:L:10.1[Line:10000<<3258649365] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 205.251.137.154;branch=z9hG4bK09f5.883e9d0146ddbe8fe68bdc8cbb6a9d80.1 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK0cB999a2ab6993e2f41
04/09/2020 9:32:03 AM - NAT/ALG check:L:9.1[Line:10000<<3258649365] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 63.247.69.226;branch=z9hG4bKe4f1.5fe24eb0406ad3330ba573e46f218f74.0 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK00B9776937a0ab5b0a9
 
Tried direct inbound to another ext...same issue...bounced to voicemail:

04/09/2020 10:58:50 AM - [CM503021]: Call(C:1): ACK is not received from sip:[email protected]
04/09/2020 10:58:41 AM - [CM503003]: Call(C:1): Call to <sip:[email protected]:0> has failed; Cause: 603 Decline/INVITE from 192.168.40.21:5060
04/09/2020 10:58:01 AM - NAT/ALG check:L:2.1[Line:10000<<3258649365] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 205.251.137.154;branch=z9hG4bKfc04.4ddb9aabab9ddf67715fc69dd876a9f8.0 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK00Baeb474e296c27298
04/09/2020 10:57:58 AM - NAT/ALG check:L:1.1[Line:10000<<3258649365] REQUEST 'INVITE' - some of SIP/SDP headers may contain inconsistent information or modified by intermediate hop SIP proxy detected: Via:SIP/2.0/UDP 63.247.69.226;branch=z9hG4bKfb57.649c8c78a9300b9a5d8df91384b41cc5.0 Via:SIP/2.0/UDP 67.231.5.110:5060;branch=z9hG4bK08B7f8dce3c68855500
 
All calls seem to also be being duplicated?
This was the same internal call.
1586454045050.png
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,031
Messages
590,388
Members
164,983
Latest member
Reed Fred
3CX Logo Footer Copyright © Sitemap Privacy
Top Bottom