Hey All!
We were having this problem where after a registration with the provider, we would receive one call then no more after that.
All other calls would get blocked and terminated.
There would be no logs of calls in 3CX and my mobile phone that i called from just came up 'Call Disconnected'.
We went through NAT issues, STUN issues, MODEM firmware issues, all thinking that it may be a issue where the first call would open and block ports and not be closed correctly.
In the end we found that the provider has in place a cool NAT workaround to aid in resolving issues with clients with NAT. (used in alot of providers)
3CX, as part of the registration packet, includes a 'rinstance' command that our provider was ignoring and thought it was a DNS command, therefore did not apply the NAT fixes to our domain.
We got the provider to start looking at this rinstance command and to act on itsinformation correctly.
After this got fixed we have had no drop outs, call issues, lack of audio... infact no issues at all!
So this just goes to show that it may not allways be your fault if there is something wrong!
The provider was Adam Internet in Australia. If there are any further issues with this provider please contact me.
I will now community test the provider in the comming week or so.
Jay
EDIT:: Rsync changed to rinstance
We were having this problem where after a registration with the provider, we would receive one call then no more after that.
All other calls would get blocked and terminated.
There would be no logs of calls in 3CX and my mobile phone that i called from just came up 'Call Disconnected'.
We went through NAT issues, STUN issues, MODEM firmware issues, all thinking that it may be a issue where the first call would open and block ports and not be closed correctly.
In the end we found that the provider has in place a cool NAT workaround to aid in resolving issues with clients with NAT. (used in alot of providers)
3CX, as part of the registration packet, includes a 'rinstance' command that our provider was ignoring and thought it was a DNS command, therefore did not apply the NAT fixes to our domain.
We got the provider to start looking at this rinstance command and to act on itsinformation correctly.
After this got fixed we have had no drop outs, call issues, lack of audio... infact no issues at all!
So this just goes to show that it may not allways be your fault if there is something wrong!
The provider was Adam Internet in Australia. If there are any further issues with this provider please contact me.
I will now community test the provider in the comming week or so.
Jay
EDIT:: Rsync changed to rinstance
Phone System 