![]() ![]() ![]() |
|
Systems like 3CX use hacks to avoid SIP ALG's working because they're a nightmare. I've never come across a system were a SIP ALG was ever required.
It's good that you like VoIP with a SonicWALL - you'd be the only person in the world who does!
sbiddle:
Systems like 3CX use hacks to avoid SIP ALG's working because they're a nightmare. I've never come across a system were a SIP ALG was ever required.
It's good that you like VoIP with a SonicWALL - you'd be the only person in the world who does!
Historically we use 3CX (v15.5), Sonicwall, and 2Talk for VoIP Gateway. This just worked on both UFB/Fiber. Admittedly Sonicwall was a bit of a learning curve, but once you get a working configuration it's obviously/easy setup. But now we have moved to Regus I'm now trying to go the basics by having Yealink phone connecting directly to 2talk without using my Sonicwall and 3CX PBX. Using 2talk auto provisioning tool, which does work surprisingly. I did try and put 50600 for the port number but the web interface for the Yealink phone saw complaining that the STUN entry was invalid (because it's blank).
chevrolux:
If you are using 2talk, then port 50600 is an alternate you can register on. May help if there is a router screwing with 5060 traffic.
The Yealink phone is registering okay. I just keep having a gut feeling the Regus is blocking 5060/VoIP/SIP/RTP traffic inbound.
What would be a is to have some kind of diagnostic tool to pin point the point of failure.
sbiddle:
Systems like 3CX use hacks to avoid SIP ALG's working because they're a nightmare. I've never come across a system were a SIP ALG was ever required.
It's good that you like VoIP with a SonicWALL - you'd be the only person in the world who does!
Were you also doing the firewall installation for these thousands of phones?
vulcannz:
sbiddle:
Systems like 3CX use hacks to avoid SIP ALG's working because they're a nightmare. I've never come across a system were a SIP ALG was ever required.
It's good that you like VoIP with a SonicWALL - you'd be the only person in the world who does!
Were you also doing the firewall installation for these thousands of phones?
In many cases, yes. I've deployed quite a significant number of multi-site fully managed PBX's with many featuring hundreds of extensions across sites. If you don't control everything end to end a deployment of this size often runs into issues that you have no control over so becomes a nightmare.
jimbob79:chevrolux:If you are using 2talk, then port 50600 is an alternate you can register on. May help if there is a router screwing with 5060 traffic.
The Yealink phone is registering okay. I just keep having a gut feeling the Regus is blocking 5060/VoIP/SIP/RTP traffic inbound.
What would be a is to have some kind of diagnostic tool to pin point the point of failure.
HELL YEAH! FIXED IT!!!!!
The issue was at 2Talk and annoyingly I wished somebody 2Talk tech. support team told me this rather than fobbing me off with generic answers about the firewall. I guess you get what you pay for.
So before we moved, we had a UFB connection with static IP address. So at some point, I had ticked the box which to saying "My phone was not behind NAT.." obviously. Only stumbled across this option in desperation. Now it's working.
jimbob79:
HELL YEAH! FIXED IT!!!!!
The issue was at 2Talk and annoyingly I wished somebody 2Talk tech. support team told me this rather than fobbing me off with generic answers about the firewall. I guess you get what you pay for.
So before we moved, we had a UFB connection with static IP address. So at some point, I had ticked the box which to saying "My phone was not behind NAT.." obviously. Only stumbled across this option in desperation. Now it's working.
I'm surprised your phone worked previously with that setting. That changes the NAT type in their Asterisk back end. Even with a public IP your phone was still behind a NAT firewall.
I'm surprised your phone worked previously with that setting. That changes the NAT type in their Asterisk back end. Even with a public IP your phone was still behind a NAT firewall.
The SonicWall was exposing/Port Forwarding our 3CX server to the public IP address, so no NATing was required.
Also, another note for other REGUS clients is that you have to register each PC/Device's mac address to be able to access to the outside world.
So it wasn't a 2talk issue then... it was a user issue. Like you say, you get what you pay for and "manage yourself" means "manage yourself".
|
![]() ![]() ![]() |