[cisco-voip] connected party information while calling webex

Bill Talley btalley at gmail.com
Fri Nov 2 17:25:44 EDT 2018


What is your cluster fully qualified domain name set to under Enterprise Parameters in CUCM?

Sent from an iOS device with very tiny touchscreen input keys.  Please excude my typtos.

> On Nov 2, 2018, at 2:15 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> 
>  
> Yeah – that caught my eye as well while I was comparing. I think you are referring to:
>  
> Calling and Connected Party Info Format
>  
> Options are:
>  
> Deliver DN only in connected party
> Deliver URI only in connected party, if available
> Deliver URI and DN in connected party, if available
>  
> Both are set to the last one, Deliver URI and DN in connected party, if available.
>  
>  
>  
> ---
> Lelio Fulgenzi, B.A. | Senior Analyst
> Computing and Communications Services | University of Guelph
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>  
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>  
> <image001.png>
>  
> From: NateCCIE <nateccie at gmail.com> 
> Sent: Friday, November 2, 2018 2:52 PM
> To: Lelio Fulgenzi <lelio at uoguelph.ca>
> Cc: Ryan Huff <ryanhuff at outlook.com>; voyp list, cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] connected party information while calling webex
>  
> There is a setting on the sip trunks to deliver dn or uri or both. I bet there is a difference between your two clusters on that setting. I may not win the bet, but that is where I’d check first. 
> 
> Sent from my iPhone
> 
> On Nov 2, 2018, at 12:20 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> 
>  
> Gotcha. All using FQDN as far as I can tell. Very odd. I don’t think I’ve made changes to jabberconfig.xml either.
>  
> ---
> Lelio Fulgenzi, B.A. | Senior Analyst
> Computing and Communications Services | University of Guelph
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>  
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>  
> <image001.png>
>  
> From: Ryan Huff <ryanhuff at outlook.com> 
> Sent: Friday, November 2, 2018 2:18 PM
> To: Lelio Fulgenzi <lelio at uoguelph.ca>
> Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] connected party information while calling webex
>  
> I meant UC, Siri assumed I meant UDS. How about the CM server references, all FQDN as well?
> 
> Sent from my iPhone
> 
> On Nov 2, 2018, at 14:15, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> 
> What is this UDS thoust speak of?
>  
> But seriously, referenced where?
>  
> I checked my UC Services, all of those are FQDN. I checked my Service Profile, and that just has a “Use UDS for Contact Resolution” option that I’ve checked off in both systems.
>  
> What would UDS have to do with replacing @acme.webex.com with @<ip.addr.cucm.sub> though? Curious. I was leaning towards connected party information setup.
>  
>  
>  
> ---
> Lelio Fulgenzi, B.A. | Senior Analyst
> Computing and Communications Services | University of Guelph
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>  
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>  
> <image001.png>
>  
> From: Ryan Huff <ryanhuff at outlook.com> 
> Sent: Friday, November 2, 2018 1:58 PM
> To: Lelio Fulgenzi <lelio at uoguelph.ca>
> Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
> Subject: Re: [cisco-voip] connected party information while calling webex
>  
> UDS services referenced by FQDN or IP?
> 
> Sent from my iPhone
> 
> On Nov 2, 2018, at 13:55, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> 
>  
> I’ve migrated my development cluster configuration to my production cluster configuration and have compared them as best as possible, but I seem to be missing connected party information when calling webex from Jabber.
>  
> On the development cluster, when I dial coyote at acme.webex.com from Jabber and am connected, the connected party information at the top of Jabber remains coyote at acme.webex.com, however, when I dial the same from production, it changes to coyote@<ipaddr.of.cucm.sub>
>  
> I’ve reviewed the SIP trunk and dependencies as much as I could and they all seem the same. I did some comparison of enterprise parameters and ccm service parameters and they too look the same.
>  
> I can’t imagine anything expresway or within webex site config would cause this.
>  
> Thoughts? Pointers?
>  
> ---
> Lelio Fulgenzi, B.A. | Senior Analyst
> Computing and Communications Services | University of Guelph
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
> 519-824-4120 Ext. 56354 | lelio at uoguelph.ca
>  
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>  
> <image001.png>
>  
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C562fab46bf0d42e667d308d640ec54b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636767781103601084&sdata=YJE317AfF9SoJ6%2BkPwj2UzimeauGWR91KiD295rmcDg%3D&reserved=0
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181102/f06afa37/attachment.html>


More information about the cisco-voip mailing list