SIP Trunk getting unregistered after making changes in Inbound rules.

[indranath]

I noticed that my SIP trunk is getting unregistered after making any changes to the Inbound rules at DID route.

 

[leejor]

What changes did you actually make? Does it work correctly if you change it back to the previous configuration?

What does the 3CX Activity log show, for an incoming call, after you made the changes? Have you compared to a "before" log?

Is the provider now receiving a condition that causes them to drop the call and that affects re-registration?

 

[craigreilly]

So you make change to an inbound rule, and the trunk unregisters or reregisters?
What specific change is occurring to the inbound rule?
Generally these are set and forget.

 

[Cytranic]

I came here to post about this same issue. If I change just the name on an INBOUND DID rule, all my calls drop. Just a name change. The Calls drop, the trunk becomes unregistered, and I have to click refresh registration to get the trunk back up. I can reproduce every time.

 

[YiannisH_3CX]

Hello,

When a change is made to the trunk settings or inbound rule the trunk de-registers and immediately re-registers to apply the new settings. Most providers do not drop calls when this happens, however some do. This behaviour is by design and cannot be changed currently.

 

[ucme4now]

To be more specific, Registration is the authentication method between endpoints. Making any change is a potential change to the authentication between the end points even if it is just a name change for the SIP trunk. This forces the the PBX to register with the SIP Provider end point to valid credentials. The SIP Provider will drop the call because your PBX is no longer a valid end point in their system during this process. It is no different when you register a phone, you put in the wrong password and it no longer shows up in the PBX as a valid end point. It is a safety mechanism meant to protect you and the the SIP Provider. The bottom line is everything is real-time, schedule an outage when making change or suffer the consequences in real time.

 

[indranath]

What changes did you actually make? Does it work correctly if you change it back to the previous configuration?

What does the 3CX Activity log show, for an incoming call, after you made the changes? Have you compared to a "before" log?

Is the provider now receiving a condition that causes them to drop the call and that affects re-registration?

If i change the name of the rule or the route calls to option like changing Extension. Then the trunk getting unregistered and all calls getting disconnect.

 

[indranath]

Hello,

When a change is made to the trunk settings or inbound rule the trunk de-registers and immediately re-registers to apply the new settings. Most providers do not drop calls when this happens, however some do. This behaviour is by design and cannot be changed currently.

If i change the name of the rule or the route calls to option like changing Extension. Then the trunk getting unregistered and all calls getting disconnect.

 

[BrenttG]

We have seen the same, changing an inbound rule drops the trunk, but only for about 5 seconds, and yes all active calls do drop, we simply made it policy to check the active calls list before hitting save on a change.

 

[craigreilly]

@YiannisH_3CX perhaps 3cx should say "You have active calls. These calls could be disconnected. Press 'OK' to continue or 'Cancel' to wait."

 

[BrenttG]

Or at least a warning that says, Any active calls may drop, use caution.