upgrade broke remote extension registration..ALLOWSOURCEASOUTBOUND

Status
Not open for further replies.

gp3cx

Joined
Jun 1, 2017
Messages
10
Reaction score
0
just upgraded to current debian version. ALLOWSOURCEASOUTBOUND is now broken and does not use the "source IP : port" to communicate with remote extensions. it uses correct ip but wrong port. it uses the port specified in Contact header. all my remote extensions do not register any longer.
 
Hello @gp3cx

Please give us some more information so we can better understand the issue. What PBX version are you running? The exact build number can be found on Dashboard under the information column.
Also what is your current Debian version?

Can you provide a log that shows the issue you are facing?
 
when a remote extension 555 tries to register the following shows in the log:
01/19/2018 1:51:28 PM - Dev(1510806627):[sip:[email protected]:5060 / 555]: Outbound is set to source: <sip:[email protected]:8918>
then when 3cx responds OK to the registration request its supposed to send it to 174.204.6.180:8918....but...it erroneously sends it to 174.204.6.180:5060. the phone never gets it and registration fails. this is a bug

Build 15.5.6354.2
debian 9.2.1
 
Last edited:
What phones are you using and how are these phones provisioned? If you are using STUN what is the port configured for the specific phone? Does the firewall checker pass and is there SIP ALG configured on the firewall of the remote site?
 
i have a generic ip phone i have used for years with 3cx. it uses rport. firewall checker 100%. the only thing that changed was i did an update from the dashboard,
 
Last edited:
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,881
Messages
589,534
Members
164,738
Latest member
User0