No outbound calling or internal calling after update

[smpltech]

Running 3cx on debian in the cloud to 8 remote Yealink T46S, phones behind pfsense firewall, everything has been fine, until a phone all of sudden lost registration. 3cx was a couple updates behind, and so I upgraded to 16.0.1078 last night. Now this morning not even extension to extension calling works, no outbound calls work. I can use my soft phone from another location to call another extension at the main location and it works, they receive inbound calls from the sip trunk fine.

I ran a packet capture at the firewall of the remote phones, and what sticks out is Status: 407 Proxy Authentication Required

1 0.000000 10.0.0.81 my.cloud.pbx.ip SIP 1133 Request: INFO sip:[email protected]:5060 |
2 0.087848 my.cloud.pbx.ip 10.0.0.81 SIP 374 Status: 200 OK |
6 0.779166 10.0.0.81 my.cloud.pbx.ip UDP 60 5065 → 5060 Len=4
8 1.191216 10.0.0.81 my.cloud.pbx.ip SIP 1208 Request: INFO sip:[email protected]:5060 |
9 1.194374 10.0.0.81 my.cloud.pbx.ip STUN 86 Binding Request
10 1.195355 10.0.0.81 my.cloud.pbx.ip STUN 86 Binding Request
11 1.234480 my.cloud.pbx.ip 10.0.0.81 SIP 373 Status: 200 OK |
12 1.234486 my.cloud.pbx.ip 10.0.0.81 STUN 130 Binding Success Response MAPPED-ADDRESS: my.remote.office.ip:11231 XOR-MAPPED-ADDRESS: my.remote.office.ip:11231
13 1.235385 my.cloud.pbx.ip 10.0.0.81 STUN 130 Binding Success Response MAPPED-ADDRESS: my.remote.office.ip:28613 XOR-MAPPED-ADDRESS: my.remote.office.ip:28613
14 1.254149 10.0.0.81 my.cloud.pbx.ip SIP/SDP 994 Request: INVITE sip:[email protected]:5060 |
15 1.341693 my.cloud.pbx.ip 10.0.0.81 SIP 480 Status: 407 Proxy Authentication Required |
16 1.343834 10.0.0.81 my.cloud.pbx.ip SIP 344 Request: ACK sip:[email protected]:5060 |
17 1.349569 10.0.0.81 my.cloud.pbx.ip SIP/SDP 1213 Request: INVITE sip:[email protected]:5060 |
18 1.467456 my.cloud.pbx.ip 10.0.0.81 SIP 308 Status: 100 Trying |
19 1.467473 my.cloud.pbx.ip 10.0.0.81 SIP 388 Status: 603 Decline |
20 1.472729 10.0.0.81 my.cloud.pbx.ip SIP 333 Request: ACK sip:[email protected]:5060 |
21 1.485096 10.0.0.81 my.cloud.pbx.ip SIP 1362 Request: INFO sip:[email protected]:5060 |
22 1.571367 my.cloud.pbx.ip 10.0.0.81 SIP 374 Status: 200 OK |

My phones have all been working for months, I have them all set to offsite STUN mode, and Disallow off LAN IPs is unchecked on each phone, all show green for registration.

 

[smpltech]

ok, so deployed SBC on a windows machine, set phones to provision to sbc LAN ip, still cant call out.

 

[Naveen | Cal4care]

a bit disappointing, entire office is down, cant even buy support. attempting to purchase support shopping cart appears to not like the state of california- View attachment 21107

Please try the following steps,

1. Fill in the address and select something from the google drop down!

2. After you select something (valid) from google then you can make some adjustments to the order details.

 

[Naveen | Cal4care]

ok, so deployed SBC on a windows machine, set phones to provision to sbc LAN ip, still cant call out.

Please note that the 407 Proxy authentication is normal and the PBX will use it to authenticate an endpoint.
The "407 Proxy Authentication Required" SIP message is sent from the PBX to the phone, to obtain authentication from the user.

In the SBC network, 3CX clients working?

Can you restart the SBC service then try?

 

[JohnS_3CX]

@smpltech since you mentioned in another post that you were using custom templates, the first thing we always suggest is to reset your devices, delete them from the extensions, and provision them again from scratch using our guides https://www.3cx.com/sip-phones/

A small change in the template can sometimes have effects that you will discover much later, so best be on the safe side during troubleshooting.

The SBC should have solved any issues related to STUN, so here's what you should do

1. Ensure SBC is on the same LAN and subnet as the phones!
2. Check in your trunks and confirm the SBC is registered and connected
3. Create two new extensions, do not change any settings - keep defaults!
4. Delete two phones from your other extensions to free them up
5. Factory reset those two phones and when they come online they will appear as "new" under "Phones" page
6. Select a phone and assign it to the brand new extension (same for the other phone)

Finally, make calls between those two new extensions, and also make external calls. If these two work then you have confirmed your network and phones are healthy. Now you know what to do with the rest of the phones at least

 

[Jojo37]

Hi,

I add the same problem that appeared suddenly.
After checking my parameters, I found out that the protocol send by the template wasn't correctly selected : it forced UDP when I was using TLS.
I just had to comment the line account.1.sip_server.1.transport_type = 0 to let my phone use the correct protocol.