3/16/2023 0 Comments Cisco jabber for windows dns srvWorkaround in my case is simple - change Device sec profile to unsecure. When your CSF is trying to use TLS, there is no match with that pattern, so registration was denied, because rule is looking for transport=TCP and REGISTER message was not forwarded to CUCM. So autogenerated Search Rule was responsible for pattern match. Tvcs: UTCTime=" 15:37:05,339" Module="arch" Level="DEBUG": Detail="Search rule '' did not match destination alias ' transport=tls lr'" When you look at the DEBUG messagess between REGISTER and its 404 response, you can see: Right above that message is response to SIP/2.0 404 Not found with that warning in the header: So some maybe useful troubleshooting info for others with same error.Ĭheck the EXP-C network log in DEBUG level. I used secured SIP device profile for Jabber CSF device (based on my very quick reading of Mobile-Remote-Access-via-Expressway-Deployment-Guide-X8-2.pdf) I missed, that TLS between EXP-C and CUCM is possible only in Mixed security mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |