Solved Flowroute Sip Trunk Registration randomly failing after 18.0.7 Upgrade

[Stephen Osborn]

Had to reinstall 3cx completely to upgrade from 18.0.4 to 18.0.7 after the reinstall our SIP trunk fails to register multiple times throughout the day then reregisters itself a few minutes later with the following errors:

I have tried deleting and remaking SIP trunk but the registration's are still failing every so often and causing calls to drop.

I see some updated documentation on making sure your trunk is either registered with main number in 11 number format or e164

Trunk L:10000(Flowroute Innovative) has changed status to registered.
SIP Server ID: 4100 03/01/2023 6:12:33 PM

Call or Registration to Flowroute Innovative has failed. sip:[email protected] replied: 400 Bad Request; from IP:34.226.36.34:5060
SIP Server ID: 12294 03/01/2023 6:08:36 PM

Trunk L:10000(Flowroute Innovative) has changed status to unregistered. This means that no more calls will pass via this trunk. Please check your network connection and the voip provider or other SIP PBX
SIP Server ID: 4100 03/01/2023 6:08:36 PM

Trunk L:10000(Flowroute - Innovative) has changed status to unregistered. This means that no more calls will pass via this trunk. Please check your network connection and the voip provider or other SIP PBX
SIP Server ID: 4100 03/01/2023 1:00:35 PM

This is our Trunks current settings we are east coast based so we use us-east flowroute gateway

 

[SweetAction]

I notice you have 2 flowroute trunks setup that are register based (and using the same proxy). While maybe not the issue, this is an issue. More info: https://support.flowroute.com/157679-3CX-rinstance-configuration

I'd fixed that first and then see if the issue continues.

 

[Stephen Osborn]

I notice you have 2 flowroute trunks setup that are register based (and using the same proxy). While maybe not the issue, this is an issue. More info: https://support.flowroute.com/157679-3CX-rinstance-configuration

I'd fixed that first and then see if the issue continues.

I saw that when logging into one of the two of our Flowroute accounts. Each of the Sip Trunks are registered to different Flowroute accounts with unique authentication details which I believe should make it fine since they are not on the same account like the documentation reads about upcoming changes.

The weird thing is the trunks don't seem to fail registration when you manually refresh but later like 30mins to an hour later when renewing registration possibly?

 

[SweetAction]

Ah, in that case I would reach out to Flowroute and ask them what they see. A 400 error is usually a server side error and they may have some information for you.

 

[Stephen Osborn]

Flowroute doesn't seem to know what would be causing the registrations to fail seems to happen usually an hour after a manual sip trunk registration. I reverified us-east flowroute ip range where indeed whitelisted in firewall (34.226.36.32/28). 3CX Firewall test hasn't failed all green.

Only error verbose logs is showing is: 03/03/2023 12:50:36 PM - [CM504005]: Registration failed for: Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]); Cause: Cause: 408 Request Timeout/REGISTER from local

pfsense set to conservative for firewall optimization option.

03/03/2023 12:50:41 PM - No inbound caller ID reformat rule for DN:10001 is defined, or it is disabled (<Rules />)

03/03/2023 12:50:41 PM - Source is identified as trunk Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>])

03/03/2023 12:50:41 PM - Source is identified as trunk Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>])

03/03/2023 12:50:38 PM - DN:10001 is registered

03/03/2023 12:50:38 PM - Registered line: Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>])

03/03/2023 12:50:38 PM - Line Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]) has been registered at server with rinstance '2b89d4543b7dfafe'

03/03/2023 12:50:38 PM - Updated registration times for DN:10001

03/03/2023 12:50:38 PM - [CM504004]: Registration succeeded for: Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>])

03/03/2023 12:50:38 PM - Successful registration of Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]), contact <sip:[email protected]:5060;rinst=2b89d4543b7dfafe>

03/03/2023 12:50:36 PM - Sent registration forLc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]) :ClientReg Send Req REGISTER from 0.0.0.0:0 tid=10fc9a5427a9dd63 Call-ID=oUMQs8kSfx2q9Cu67CmwfA..: REGISTER sip:us-east-va.sip.flowroute.com SIP/2.0 Via: SIP/2.0/ ;branch=z9hG4bK-524287-1---10fc9a5427a9dd63;rport Max-Forwards: 70 Contact: <sip:[email protected]:5060;rinstance=2b89d4543b7dfafe> To: <sip:[email protected]> From: <sip:[email protected]>;tag=668acd4e Call-ID: oUMQs8kSfx2q9Cu67CmwfA.. CSeq: 1 REGISTER Expires: 120 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE Supported: replaces, timer Content-Length: 0

03/03/2023 12:50:36 PM - Updated registration times for DN:10001

03/03/2023 12:50:36 PM - [CM504003]: Sent registration request for Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>])

03/03/2023 12:50:36 PM - Registering Line Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>])

03/03/2023 12:50:36 PM - Unregister: ADS for 10001 is not found

03/03/2023 12:50:36 PM - Unregistering Line 10001

03/03/2023 12:50:36 PM - Destroyed ADS for Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]); contact <sip:[email protected]:5060;rinst=84e5149f851360ed>

03/03/2023 12:50:36 PM - Removing ADS of Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]): contact <sip:[email protected]:5060;rinst=84e5149f851360ed>

03/03/2023 12:50:36 PM - DN:10001 is unregistered

03/03/2023 12:50:36 PM - Unregistered line: Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>])

03/03/2023 12:50:36 PM - DN:10001 is unregistered

03/03/2023 12:50:36 PM - Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]) trying to register at another destination: 34.226.36.33:5060/UDP fk=0 tgt=

03/03/2023 12:50:36 PM - Line 10001: Request for registration in 10 ms

03/03/2023 12:50:36 PM - Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]) graylisted target 34.226.36.32:5060/UDP fk=0 tgt=ep-us-east-va-01.flowroute.com for 86400 sec.

03/03/2023 12:50:36 PM - Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]): failed to reach destination 34.226.36.32:5060/UDP fk=0 tgt=

03/03/2023 12:50:36 PM - Updated registration times for DN:10001

03/03/2023 12:50:36 PM - [CM504005]: Registration failed for: Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]); Cause: Cause: 408 Request Timeout/REGISTER from local

 

[Stephen Osborn]

Another failed request

03/03/2023 1:31:45 PM - [CM504007]: Next attempt to register Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]) is scheduled in 5 minute

03/03/2023 1:31:45 PM - [CM504005]: Registration failed for: Lc:10001(@flowroute Doctor[<sip:[email protected]:0/UDP>]); Cause: Cause: 400 Bad Request/REGISTER from 34.226.36.33:5060

 

[SweetAction]

My next step would be a packet capture to see what's going on.

On your switch, mirror the port 3CX is using to another machine running wireshark or similar, wait for the issue to happen, examine the capture and see what the registration attempt is doing compared to a sucessful one.

 

[Stephen Osborn]

For some reason had to remake firewall nat rules in pfsense post update even though 3cx was passing firewall test post update.

Everything looks to be resolved.