- Joined
- Jan 9, 2014
- Messages
- 5,076
- Reaction score
- 1,096
Yesterday night I applyied on all pbx the latest .655 hotfix release as i got registration problems on 4 PBXs previously.
Trunk provider is a supported one: OpenIp -----> Trunks set from 3cx template
Since this morning I got on 2 PBXs same problem running like that:
Pbxs are on premise Windows 10 Pro V2004
Pbx send a gone on trunk and try a registration one second after
Registration seem to succeed , trunk is green connected on PBX but no call traffic is possible both ways.
Refresh button works and give a new timestamps.
On provider side they see 3CX registration request coming but this is connected to a 0.0.0.0. public IP so PBX is unreachable and calls goes to degraded route.
another problem seem to be with register timeout value is not followed by PBX, Value is set in trunk to 300s but provider see registration request coming a lot of time before middle time of 150s.(30s or 40s)
Do you encounter same behavior as me ?
Trunk provider is a supported one: OpenIp -----> Trunks set from 3cx template
Since this morning I got on 2 PBXs same problem running like that:
Pbxs are on premise Windows 10 Pro V2004
Pbx send a gone on trunk and try a registration one second after
Registration seem to succeed , trunk is green connected on PBX but no call traffic is possible both ways.
Refresh button works and give a new timestamps.
On provider side they see 3CX registration request coming but this is connected to a 0.0.0.0. public IP so PBX is unreachable and calls goes to degraded route.
another problem seem to be with register timeout value is not followed by PBX, Value is set in trunk to 300s but provider see registration request coming a lot of time before middle time of 150s.(30s or 40s)
Do you encounter same behavior as me ?
Last edited:
