EX90 Registered to Regional CUCM :: Not able to dial out of history to external endpoints

[Brandon Nuner]

EX90 Registered to Regional CUCM :: Not able to dial out of history to external endpoints

Lab deployment;

Cisco VCSe - 7.2.2

Cisco VCSc - 7.2.2

Cisco CUCM (SME Cluster) - 9.1.1

Cisco CUCM (Region_B Cluster) - 9.1.1

Endpoints;

Movi - 4.6 - Registered to Cisco's service @jabber.com

EX90 - 6.2 - Registered to Cisco CUCM (Region_B Cluster)

Call flow 1 - Movi calls EX90 = SUCCESS

Jabber.com Movi >> SIP >> Cisco VCSe >> SIP >> Cisco VCSc >> SIP >> Cisco CUCM (SME Cluster) >> SIP >> Cisco CUCM (Region_B Cluster) >> SIP >> Cisco EX90

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 nunerb123@jabber.com.. my EX90 only sees nunerb123 in call history.. not nunerb123@jabber.com.  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 nunerb123@jabber.com. 

Just to be clear... I am able to dial nunerb123@jabber.com directly from the EX90 if I input the string myself.. I'm just not able to dial from the History of my EX90.

Thank you!

[Paulo Souza]

Hi Brandon,

Example; Say my Movi alias is nunerb123@jabber.com.. my EX90 only sees nunerb123 in call history.. not nunerb123@jabber.com.  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 nunerb123@jabber.com. 
Just to be clear... I am able to dial nunerb123@jabber.com directly from the EX90 if I input the string myself.. I'm just not able to dial from the History of my EX90.

Tell something, when you dial from Jabber to your EX90, is there any SIP/H323 interworking working on your VCS's? Could you please take the search history of both VCSs and check whether there is interworking going on? Can you check the source alias received by each VCS (C and E) to see if it is correct?

Regards

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[Brandon Nuner]

Hi Paulo,

Interworking is turned on but this call senario is not being interworked.  Also the source alias is correctly passed to/from the VCS's.  I can verify this by registering my EX90 to the VCSc and performing the same test.

I didn't mention this in the original post but I suspect 1 or both of the CUCM clusters are at fault.

thanks

[Paulo Souza]

Hi Brandom,

It seems CUCM is not keeping the original source SIP URI, but it is replacing the URI by removing the domain portion.

In the SIP Trunk configuration of CUCM, can you check if the option "use full qualified domain name" is enable? Also, is there any translation in CUCM for this call?

Regards

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[Brandon Nuner]

There are no translations in the call flow.  The option for "use full qualified domain name" is Checked on all SIP Profiles that are assigned to SIP Trunks in the call flow and also assigned in the SIP Profile assigned to the endpoint.

[Paulo Souza]

Hi Brandom,

I really believe that CallManager 9.1 should be able to work fine with SIP URI, not just to accept calls using URI from endpoints registered to it, but also to manipulate the source URI correctly.

Just in case, have you configured CallManager and VCS by following this guide

http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/Cisco_VCS_Cisco_Unified_Communications_Manager_Deployment_Guide_CUCM_8_9_and_X7-2.pdf

? Can you double check?

Regards

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[Brandon Nuner]

Paulo,

Thank you for the suggestion however it does not apply.  We will be receiving calls from many different domains and I need to be able to just accept the domain that's being presented.  What happens when someone calls from another domain such as Cisco.com?  The solution has to be flexible enough to work with all domains.

Also... just noticed something very odd.

• While I'm in the call from Movi to EX90 and I attempt to add the connected party to my favorites the display name is saved as nunerb123 and the sip Uri is saved as nunerb123@jabber.com.. all correct!!
• However.. when I hang up the call and go to History.. the source alias is nunerb123.. not nunerb123@jabber.com

[Brandon Nuner]

Does anyone know what SIP header information is used for the Call History on the EX90?

[Paulo Souza]

Hi Brandom,

I suggested the guide only to check the parameters applied to trunk, such as SIP normalization script, SIP Profile parameters and so on. Because those settings may influence.

If you register EX90 to VCS and the source alias of jabber is correct, so it is probably a problem related to how the CallManager manipulates the source URI, not a problem in EX90 itself, I think.

I have a CUCM 9 here to test. I will make some attempts and I will post the results as soon as I get.

Regards

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[Brandon Nuner]

I must had misinterpreted this, "but also to manipulate the source URI correctly."

In any case, I did follow that document very closely.  Not to say I couldn't had skipped over something.

Thank you for being willing to spin up your lab to test.  I'm also going to register the EX90 to the SME Cluster (1 step closer the the VCS) to see if that makes a difference at all.

[Paulo Souza]

Hi Brandom,

Meanwhile, you can do following test:

Register EX90 to VCS

- Make a call from Jabber

- Take the logs of the call directly on the EX90. You can use tcpdump to collect the SIP messages.

Register EX90 to CUCM

- Make a call from Jabber

- Take the logs of the call directly on the EX90. You can use tcpdump to collect the SIP messages.

Compare both SIP headers. Check whether there is difference related to display name and source URI. So you can come to conclusion whether callmanager is putting wrong information to EX90 or EX90 is not manipulating correctly the SIP headers received from CUCM.

=)

I will test as well.

Paulo Souza

Please rate replies and mark question as "answered" if applicable.

[Brandon Nuner]

If we are looking at just the From: Header information in both call examles you have listed above the From: Header information is the same throughout the call.

Please let me know if you find the same or if I should be looking at a different header.

From: "nunerb123" <>nunerb123@jabber.com>;tag=109355~47ab162b-176d-4e90-baf0-b2428590ffb2-38420524

     SIP Display info: "nunerb123"

     SIP from address: sip:nunerb123@jabber.com

     SIP from address User Part: nunerb123

     SIP from address Host Part: jabber.com

     SIP from tag: 109355~47ab162b-176d-4e90-baf0-b2428590ffb2-38420524

[Brandon Nuner]

Forgot to mention.

The same issue occurs on the SME Cluster.

[Brandon Nuner]

Just downgraded the EX90 to 5.1.8 based on another discussion I just found;

https://supportforums.cisco.com/thread/2228844

Just downgraded unit.. No changes to the CUCM programming... History is working correctly.

I'm going to open a TAC case and follow up.

[Paulo Souza]

Hi Brandon,

I just tested your problem in my remote lab. I got the same behavior, EX90 receives the correct SIP information from CUCM, including all the source headers. So I agree with you that may be something related to EX90's strange behavior.

Could you try to redial from EX90 and then capture SIP messages on the endpoint? Just to check if EX90 is really sending the incorrect destination URI to CUCM.

Unfortunately, I cannot make that test because this is a remote lab and I don't have anybody there to test for me using the history. =/

Regards

Paulo Souza

Please rate replies and mark question as "answered" if applicable.