On the UCM end, the logging looks tends to look like: If you get the WAN IP of the customer, you can see timeouts and similar as Jabber sends nothing to the Expressway, it just discontinues the conversation. It goes through the unregister process internally, and then starts over to no avail. In the log, we can see the via line showing the client's IP and a port of 0, which Jabber notes is a bad message and discards it. The Expressway is also okay with this, and replies with the proxy auth challenge (407). Jabber is actually okay with this and sends it off to the Expressway. ĭigging through the Jabber log on my end, for my MRA customers, what I could see is that whatever mechanism grabs the socket details for the SIP connection is not able to determine the local port. I went through this with a customer before I was pointed to this thread by.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |