06-01-2018 04:08 AM - edited 03-18-2019 02:09 PM
Hello,
I have some stanadlone endpoints on the internet SX10/20.
When they are calling into Skype via EXP-E -> EXP-C -> CUCM -> CMS they all apear with the same H323 ID and CMS will drop the call because of this bug : CSCve27489
So I changed the H323 ID on the configuration page of the endpoint, saved and rebooted but I still get the following in the setup :
2018-06-01T10:43:21.075+00:00 a8 appl[1709]: 254.57 H323Packet sourceAddress 2018-06-01T10:43:21.075+00:00 a8 appl[1709]: 254.57 H323Packet { 2018-06-01T10:43:21.075+00:00 a8 appl[1709]: 254.57 H323Packet h323-ID : "h323:xx:xx:xx:xx"
The h323 id should be showing the new value, or am I wrong on this point ?
Thanks for taking a look,
Regards,
Mat
06-01-2018 08:29 AM - edited 06-01-2018 08:32 AM
You described these endpoints as standalone - that means they aren't registered to a Gatekeeper or SIP Proxy, correct? The H.323 ID and E.164 fields are not used unless you are registering to an H.323 Gatekeeper. You are still seeing the IP address as the ID because in your scenario that's what it is.
06-02-2018 01:43 AM - edited 06-02-2018 01:50 AM
Yes, there standalone, TAC reccomended to change these values even though I did mention the endpoints were standalone.
So after a bit more analysis I can see that the reason 1st call is disconnected when the second call coming from a standalone endpoint to a skype meeting is because CUCM is sending identical SIP URI "FROM" for two seperate calls which results in the first call getting disconnected (CSCve27489). I am checking CCM traces to see which App/Process on CUCM is responible for this as I was not involved with the deployment.
"When second external standalone endpoint calls to skype meeting, 1st standalone endpoint already connected gets disconnected from the same skype meeting."
Regards,
Mat
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: