No Audio on Internall Call

[Edward Shin]

Hello,

We have a cellular router with a speaker phone attached.
It is correctly registered with an extension and internal calls successfully connect and I can see the line go green.
However there is no audio being sent or received.
I attached a Grandstream phone to it and it is getting the same issue.
I can see traffic on port 5060 but no traffic on ports 9000-10999.
All the rules are correctly made but it just seems like no data is being sent over ports 9000-10999.
I can't see any traffic on our firewall using those ports.

 

[eddv123]

Please describe your network and issue more clearly.

You say the issue is no audio on internal calls. The router and ports in this case would not really get involved (unless it was a remote site using RPS STUN phones - as the audio would traverse back to the PBX).

Please confirm the audio path and network topology (VLAN's, dual NIC's, routed network etc): https://www.3cx.com/blog/docs/network-configurations-supported-3cx-phone-system/

Most importantly where the phones and PBX reside.

 

[Edward Shin]

It is a remote site not using a STUN server. We have many of these units deployed all around and they all work with the current configuration, however with this new unit is using a new provider. It doesn't look like any audio is being sent, cannot see any audio traffic on our firewall for the 9000-10999 port range. The network topology is speakerphone, connected to a cellular router on our own MPLS network, connected to the PBX at our office on a VLAN.

 

[leejor]

What make/model device is this cellular router? Who's network is it on? Was it supplied by the provider? IPV4 or IPV6, that might make a difference. Other remote extensions to the same PBX are working as expected?
Does a registration of the extension, when looking at the 3CX Activity Log, look to be correct? Public IP and local device port, even without STUN? You say this is a router, and they have been deployed elsewhere with success, is there any port forwarding , in the device, that was required?

 

[Edward Shin]

Router - Microhard Dragon IoT
This is our own Rogers MPLS
We have many units on Bell's network but this is our first Rogers MPLS unit
This is all in regards to IPv4
All units using a Bell SIM work fine, we have created the corresponding rules and NATing for Rogers
The Registration on 3cx and the speaker both seem to be correct and the extension itself registers and connects when called out to it.
It is a 10.100 IP, private to our MPLS network.
There is port forwarding required just to access the speaker web GUI along with other things. These all seem to be working correctly. I don't believe port forwarding is required for audio.

 

[leejor]

Is this the first install using Rogers? Are you using them simply as transport, or is there more involved. Is it possible to swap out the SIM for one from Bell (if the router is compatible). If that worked , then it may be some issue with the provider. Have you involved Rogers in helping to troubleshoot?

 

[Edward Shin]

Yes this is the first install using Rogers.
They provided us with our own APN using their infrastructure.
If we swap out the Rogers with a Bell SIM card, the unit will work (with the corresponding rule and config changes and etc...)
I just don't get why we don't see any traffic on the audio ports (9000-10999) when the call is made and connected. There is just no traffic at all except for ports 5060 (SIP), 53 (DNS), 83 (web GUI of speaker)

 

[Marari]

We have many units on Bell's network but this is our first Rogers MPLS unit
This is all in regards to IPv4

There was an issue with Rogers customers and the iOS app over the summer.

Rogers upgraded their network to default to IPV6 and, if memory serves correctly, there is no automatic fallback (anymore) to IPV4. The issue was resolved with the iOS app but it took a while to get there. Some people had limited success with talking to Rogers support and asking them to blacklist to blacklist the IMEI of the phones on IPV6 forcing it to IPV4, but I'm not 100% sure that will fix your problem, if its appropriate to your problem, or if they will even do that anymore.

Bell / Bell MTS did not have the issue at all.

 

[leejor]

I was wondering if IPV6 had anything to do with your issue, especially after the problems with EE in the UK, as they migrate their mobile network from IPV4.

You might want to contact Rogers regarding this.