Daniel Hello,
Pasted below, 200 OK and Following ACK(Recorded at the client side via
wireshark configured with private key)
BR,
Arik
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/TLS
Daniel, Thank you!
You are right about this.
I configured PJSIP not to check whether the contact contains SIPS.
This solved the problem on one of my setups where I have one NIC that has a
public IP.
However on the original setup, the kamailio has one public IP and one private
IP. In that
Hello,
can you paste here the 200OK for INVITE sent out by kamailio and the ACK
received by kamailio?
Cheers,
Daniel
On 11.06.18 09:51, Arik Halperin wrote:
> Daniel, Thank you!
>
> You are right about this.
>
> I configured PJSIP not to check whether the contact contains SIPS.
>
> This
Hello,
Kamailio is not involved in the issue reported here. Practically, pjsip
expects sips: scheme in the contact URI, which was set by FreeSwitch in
200ok. Maybe there is an option that you have to turn on for FreeSwitch
to use sips: scheme.
Otherwise, you can try to replace sip with sips in
Hello,
I’m using TLS
After receiving 200OK from kamailio:
r2voip.clear2voipdialer I/(NativeSdk_2_0) 1528174138320 PJSIP: (NativeSdk_2_0)
1528174138320 PJSIP:2018-05 07:48:58.319 pjsua_core.c RX 2203 bytes Response
msg 200/INVITE/cseq=8107 (rdata0x7a2c56fb38) from TLS 70.36.25.65:443:
