- Joined
- Jul 29, 2017
- Messages
- 135
- Reaction score
- 18
As my provider told me, I had to disable SecureSIP because the certificate could not be used to make a connection to the sips server.
(Provider: 3CX is aware of this problem, but cannot solve it)
So I have disabled SecureSIP, and all seems to work fine, until today.:
The PBX has automatically enabled the SecureSIP feature. Therefore the trunk failed to register.
Im wondering, why this is happening, when I manually disabled SecureSIP.
08.02.2019 04:50:00 - Secure SIP (IPv6) is available at ***
08.02.2019 04:50:00 - Secure SIP (IPv4) is available at ***
08.02.2019 04:50:00 - Adding secure SIP transport (IPv4) for ***:5061
08.02.2019 04:50:00 - [CM506005]: Public IP=**** is used for WAN communications through local interface with IP=**
08.02.2019 04:50:00 - UDP transport is joined to SIP multicast group on interface **
08.02.2019 04:50:00 - Folder for SSL certificates : /var/lib/3cxpbx/Instance1/Bin/Cert
08.02.2019 04:50:00 - ** Initializing SIP stack **
08.02.2019 04:50:00 - Local IP addresses detected: [**,****]
08.02.2019 04:50:00 - [CM501006]: Default Local IP address: **
08.02.2019 04:50:00 - Default best-route IP is determined as **
08.02.2019 04:50:00 - [CM501002]: Version: 15.5.15502.6
08.02.2019 04:50:00 - [CM501001]: Start 3CX PhoneSystem Call Manager
08.02.2019 04:50:00 - [CM501007]: * Started Calls Controller thread *
08.02.2019 04:50:00 - Startup completed for pbx:5485/DBProvider
08.02.2019 04:50:00 - [EC200001]: Configuration server is connected:
application
bx:5485/DBProvider
local:127.0.0.1:47256
remote:127.0.0.1:5485
08.02.2019 04:50:00 - Application connected
bx:5485/DBProvider
08.02.2019 04:50:00 - Start management threads for pbx:5485/DBProvider
(Provider: 3CX is aware of this problem, but cannot solve it)
So I have disabled SecureSIP, and all seems to work fine, until today.:
The PBX has automatically enabled the SecureSIP feature. Therefore the trunk failed to register.
Im wondering, why this is happening, when I manually disabled SecureSIP.
08.02.2019 04:50:00 - Secure SIP (IPv6) is available at ***
08.02.2019 04:50:00 - Secure SIP (IPv4) is available at ***
08.02.2019 04:50:00 - Adding secure SIP transport (IPv4) for ***:5061
08.02.2019 04:50:00 - [CM506005]: Public IP=**** is used for WAN communications through local interface with IP=**
08.02.2019 04:50:00 - UDP transport is joined to SIP multicast group on interface **
08.02.2019 04:50:00 - Folder for SSL certificates : /var/lib/3cxpbx/Instance1/Bin/Cert
08.02.2019 04:50:00 - ** Initializing SIP stack **
08.02.2019 04:50:00 - Local IP addresses detected: [**,****]
08.02.2019 04:50:00 - [CM501006]: Default Local IP address: **
08.02.2019 04:50:00 - Default best-route IP is determined as **
08.02.2019 04:50:00 - [CM501002]: Version: 15.5.15502.6
08.02.2019 04:50:00 - [CM501001]: Start 3CX PhoneSystem Call Manager
08.02.2019 04:50:00 - [CM501007]: * Started Calls Controller thread *
08.02.2019 04:50:00 - Startup completed for pbx:5485/DBProvider
08.02.2019 04:50:00 - [EC200001]: Configuration server is connected:
application
local:127.0.0.1:47256
remote:127.0.0.1:5485
08.02.2019 04:50:00 - Application connected
08.02.2019 04:50:00 - Start management threads for pbx:5485/DBProvider