I know these. I give you a solution for your problem.
with default settings, when you are on http. after registration over WS, this happens:
Scheduling destruction of SIP dialog ‘[email protected]:5061’ in 32000 ms (Method: NOTIFY)
Reliably Transmitting (no NAT) to 192.168.1.119:51938:
NOTIFY sip:[email protected];transport=wss SIP/2.0
Via: SIP/2.0/WS 192.168.1.71:5061;branch=z9hG4bK285ccc8d
Max-Forwards: 70
From: “Unknown” sip:[email protected]:5061;tag=as340c7c42
To: sip:[email protected];transport=wss
Contact: sip:[email protected]:5061;transport=WS
Call-ID: [email protected]:5061
CSeq: 102 NOTIFY
User-Agent: FPBX-13.0.131(13.9.1)
Event: message-summary
Content-Type: application/simple-message-summary
Content-Length: 105
Messages-Waiting: no
Message-Account: sip:*[email protected]:5061;transport=WS
Voice-Message: 0/0 (0/0)
Scheduling destruction of SIP dialog ‘fg7mkh7mb0nnhdbi77q0dv’ in 32000 ms (Method: REGISTER)
<— SIP read from UDP:192.168.1.171:5065 —>
jaK
<------------->
[2016-06-20 08:52:36] NOTICE[11153]: chan_sip.c:29921 sip_poke_noanswer: Peer ‘99302’ is now UNREACHABLE! Last qualify: 0
it uses “WSS”. i think this makes issue.
Hi Everybody,
since I have open this Case, which was originally as below:
after updating our System (10.13.66-11) with the latest Status Patches,
WebRTC Phones can logon, can make call’s but show as unregistered in CLI
and therefore can’t be called.
I have tried re configuring the Firewall, stopped the Firewall etc. but its not working.
Everything was working perfectly before the update.
I want to update this case and let everybody know, that after installing an Let’s encrypt Certificate and reinstalling the UCP Node Server Module at last, all looks good for me.
I’m on the latest WebRTC Module (13.0.27) as for all other Modules as well and my UCP logon works with https.
Phone and XMPP Module are “green”.
At least from my side, I could close this case as solved.
Cheers,
NUB
1 Like