Call flow 2- EX90 attempts to dial Movi from history = FAILS
Call flow 3 - EX90 attempts to dial Movi by entering sip alias manually = Success
Discription of issue;
In attempt to follow Cisco's recommended deployment model of registering Cisco video endpoints to CUCM I've run across a problem. I have all the dialing working so long as you are entering the name/number and hitting dial. I'm now working on making sure all endpoints are able to dial out of their history. My issue is as follows. When the Movi client that is external to my SIP domain dials my EX90 registered to the CUCM Region_B Cluster I see the host information in my history but not the domain. Example; Say my Movi alias is email@example.com.. my EX90 only sees nunerb123 in call history.. not firstname.lastname@example.org. What ends up happening is that when I attempt to dial from history to the previous call EX90 dials nunerb123@IPADDRESSSOFCUCM which of course fails because it needs to route to email@example.com.
Just to be clear... I am able to dial firstname.lastname@example.org directly from the EX90 if I input the string myself.. I'm just not able to dial from the History of my EX90.
Yes, go ahead and open a TAC case. To speed up the process, you can open a TAC from this discussion, so TAC team will start your case first checking all the troubleshooting steps we have done until now, so you can save time and avoid re-test.
Please rate replies and mark question as "answered" if applicable.
Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".
Go to >> CUCM Administration >> System >> Enterprise Parameters Configuration >> Set your >> "Organization Top Level Domain". I believe that alone with fix the issue. If not, set as well, "Cluster Fully Qualified Domain Name". Please post if this works for you.
Thanks for your reply. I already had the customer's domain set in the Enterprise Params top domain and cluster domain name. The fix was setting the endpoints to use the 'Standard SIP Profile For TelePresence Conferencing' which has the checkbox ticked for '
Cisco Finesse Not Ready - Call Overlap status is very a very common issue seen on Finesse desktop. Agents miss two calls and they are put in Not Ready - Call Overlap status. This is very likely related to CVP server and it's unreachabl...
Lab 1: Cisco Meeting Server Standalone CertificatesLab 2: Cisco Meeting Server Cluster Certificates with Multi-SANLab 3: Multiple Certificates with Multiple CA ServersLab 4: Cisco Meeting Server Cluster Certificates Advanced ScenarioLab 5: Streamer Servic...
Certificates are the first step to deploy Cisco Meeting Server, preparing certificate are very important to enable different services. As a VOIP administrator, mastering the concept of certificates is unavoidable
Using multiple CA servers, instead of a si...
I just finished to write a comprehensive certificates preparation for Cisco Meeting Server Clustering. Through 60 pages I explained in detail, how to create certificates for database cluster, callbridge cluster, certificate chain for webbridge3, certifica...