No MWI notification with TLS
Hi, can somebody confirm this effect? - FreeSWITCH version: 1.5.13b on FreeBSD - CA, agent.pem and cafile.pem were created by gentls_cert and the internal profile was configured to enable TLS with only SSL23 cipher (according to https://wiki.freeswitch.org/wiki/SIP_TLS) - a user has at least one waiting voice mail - my UAC is CSipSimple_m0-18/r2423 a connection via UDP shows the following flow (UAC - UAS): ---> REGISTER <--- 401 Unauthorized ---> REGISTER with credentials <--- 200 OK ---> SUBSCRIBE <--- 202 Accepted <--- NOTIFY with payload "Messages-Waiting: yes" and "Voice-Message: 2/0" ---> 200 OK Here CSIPSimple correctly indicates waiting messages. However, if i connect the same user via TLS (SSL23), i get only this flow: ---> REGISTER <--- 401 Unauthorized ---> REGISTER with credentials <--- 200 OK ---> SUBSCRIBE <--- 202 Accepted And that's all, no NOTIFY is sent from FS and CSIPSimple shows no MWI-Message. Is there possibly more to configure to work the same way with TLS? Thanks for any help and hints Torsten
Without logs or sip traces its hard to tell, Also without the exact git rev its even harder to tell. /b On Sat, Jun 28, 2014 at 11:05 AM, Torsten Hantzsche <thantzsche@petitenet.de
wrote:
Hi,
can somebody confirm this effect?
- FreeSWITCH version: 1.5.13b on FreeBSD - CA, agent.pem and cafile.pem were created by gentls_cert and the internal profile was configured to enable TLS with only SSL23 cipher (according to https://wiki.freeswitch.org/wiki/SIP_TLS) - a user has at least one waiting voice mail - my UAC is CSipSimple_m0-18/r2423
a connection via UDP shows the following flow (UAC - UAS):
---> REGISTER <--- 401 Unauthorized ---> REGISTER with credentials <--- 200 OK ---> SUBSCRIBE <--- 202 Accepted <--- NOTIFY with payload "Messages-Waiting: yes" and "Voice-Message: 2/0" ---> 200 OK
Here CSIPSimple correctly indicates waiting messages.
However, if i connect the same user via TLS (SSL23), i get only this flow:
---> REGISTER <--- 401 Unauthorized ---> REGISTER with credentials <--- 200 OK ---> SUBSCRIBE <--- 202 Accepted
And that's all, no NOTIFY is sent from FS and CSIPSimple shows no MWI-Message.
Is there possibly more to configure to work the same way with TLS?
Thanks for any help and hints Torsten
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Sun, 29 Jun 2014, Brian West wrote:
Without logs or sip traces its hard to tell, Also without the exact git rev its even harder to tell. /b
Sorry, forgot to mention that: i tried it with commit 7406be6. Meanwhile, after some hour-long trial & error i solved it by adding <variable name="sip-force-contact" value="NDLB-tls-connectile-dysfunction"/> to the user directory to circumvent the problem with the different portnumbers in the lines "contact:" and "via:". Now FS sends the MWI-NOTIFY with TLS too. Sorry for the noise and thanks, Torsten
You shouldn't need this, Sounds like you have an broken implementation possibly, Please file a JIRA, That should just work due to using TCP for the connection. Please include the logs, sip traces and details in a JIRA. We recently removed RPORT from TCP and TLS as it shouldn't be there per the spec and could be related to that change, I would like to understand it better. -- Brian West brian@freeswitch.org Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED) On Jun 30, 2014, at 12:37 PM, Torsten Hantzsche <thantzsche@petitenet.de> wrote:
Now FS sends the MWI-NOTIFY with TLS too.
Sorry for the noise and thanks, Torsten
On Wed, 2 Jul 2014, Brian West wrote:
You shouldn't need this, Sounds like you have an broken implementation possibly, Please file a JIRA, That should just work due to using TCP for the connection.
Please include the logs, sip traces and details in a JIRA. We recently removed RPORT from TCP and TLS as it shouldn't be there per the spec and could be related to that change, I would like to understand it better.
Brian, i filed a Jira for that: FS-6643 Torsten
participants (3)
-
Brian West
-
Brian West
-
Torsten Hantzsche