Incoming Call Issue after New SSL Replacement

Status
Not open for further replies.

rsavalas

Free User
Joined
Sep 21, 2021
Messages
1
Reaction score
0
Hi,

Have a v16 3CX with most all of client are 3cx apps. We've replaced the SSL certificate due to its expiration with the new one, no issue with the console, dashboard etc., but all extension are not able to receive the incoming call even from internal, but successfully made outbound call to fxo gw/pstn.

Tried to upgrade to v18, run smoothly, but the same issue with incoming calls are there.
There's a call log in receiver phone, said it was misscalled, and also on Call Log, the call was not answered.

Here below is the log files during the call:


15:26:55.588|7fb075611700| Warn|RTPReceiver.cpp(172): 5:RTPReceiver[0]:RTP receiver was not added for [email protected]:5482(C:12.1). has no assigned socket
15:26:55.588|7fb075611700| Warn|RTPReceiver.cpp(172): 5:RTPReceiver[0]:RTCP receiver was not added for [email protected]:5482(C:12.1). has no assigned socket
15:26:55.588|7fb06ceef700| Info|MSEndPoint.cpp(2685): 11:[MS211000] C:12.1: 10.241.85.157:10004 offers telephone-event. In-Band DTMF tone detection is turned off for this call segment
15:26:55.588|7fb06ceef700| Info|MSEndPoint.cpp(3014): 10:[MS210000] C:12.1:Offer received. RTP connection: 10.241.85.157:10004(10005)
15:26:55.589|7fb06ceef700| Info|MSEndPoint.cpp(2253): 10: C:12.2 SDP_PASSTHROUGH
15:26:55.589|7fb06ceef700| Info|MSEndPoint.cpp(2398): 10:[MS210004] C:12.2:Offer provided. Connection(proxy mode): 127.0.0.1:7028(7029)
15:27:15.609|7fb06ceef700| Info|MSEndPoint.cpp(2253): 10: C:12.3 SDP_PASSTHROUGH
15:27:15.609|7fb06ceef700| Info|MSEndPoint.cpp(2398): 10:[MS210004] C:12.3:Offer provided. Connection(proxy mode): 127.0.0.1:7030(7031)
15:27:15.709|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:VRTP receiver for [email protected]:5482(C:12.2) has no assigned socket
15:27:15.709|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:VRTCP receiver for [email protected]:5482(C:12.2) has no assigned socket
15:27:15.709|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:T38 receiver for [email protected]:5482(C:12.2) has no assigned socket
15:27:15.709|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:T38_ receiver for [email protected]:5482(C:12.2) has no assigned socket
15:27:15.710|7fb06ceef700| Info|MSEndPoint.cpp(2685): 11:[MS211000] C:12.3: 127.0.0.1:12028 offers telephone-event. In-Band DTMF tone detection is turned off for this call segment
15:27:15.710|7fb06ceef700| Info|MSEndPoint.cpp(3019): 10:[MS210001] C:12.3:Answer received. RTP connection[unsecure]: 127.0.0.1:12028(12029)
15:27:15.710|7fb06ceef700| Info|MSEndPoint.cpp(2253): 10: C:12.1 SDP_PASSTHROUGH
15:27:15.710|7fb06ceef700| Info|MSEndPoint.cpp(2403): 10:[MS210005] C:12.1:Answer provided. Connection(proxy mode):127.1.2.3:46(47)
15:27:18.022|7fb075611700| Warn|RTPReceiver.cpp(193): 5:RTPReceiver[0]:RTP receiver for [email protected]:5482(C:12.1) has no assigned socket
15:27:18.022|7fb075611700| Warn|RTPReceiver.cpp(193): 5:RTPReceiver[0]:RTCP receiver for [email protected]:5482(C:12.1) has no assigned socket
15:27:18.022|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:VRTP receiver for [email protected]:5482(C:12.3) has no assigned socket
15:27:18.022|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:VRTCP receiver for [email protected]:5482(C:12.3) has no assigned socket
15:27:18.022|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:T38 receiver for [email protected]:5482(C:12.3) has no assigned socket


15:27:18.022|7fb06e6f2700| Warn|RTPReceiver.cpp(452): 5:MediaProxy:T38_ receiver for [email protected]:5482(C:12.3) has no assigned socket
 
Status
Not open for further replies.

Forum statistics

Threads
111,977
Messages
590,096
Members
164,906
Latest member
Nari