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 | le...@uoguelph.ca<mailto:le...@uoguelph.ca> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] From: Ryan Huff <ryanh...@outlook.com> Sent: Friday, November 2, 2018 1:58 PM To: Lelio Fulgenzi <le...@uoguelph.ca> Cc: voyp list, cisco-voip (cisco-voip@puck.nether.net) <cisco-voip@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 <le...@uoguelph.ca<mailto:le...@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 coy...@acme.webex.com<mailto:coy...@acme.webex.com> from Jabber and am connected, the connected party information at the top of Jabber remains coy...@acme.webex.com<mailto:coy...@acme.webex.com>, however, when I dial the same from production, it changes to coyote@<ipaddr.of.cucm.sub<mailto:coyote@%3cipaddr.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 | le...@uoguelph.ca<mailto:le...@uoguelph.ca> www.uoguelph.ca/ccs<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.uoguelph.ca%2Fccs&data=02%7C01%7C%7C562fab46bf0d42e667d308d640ec54b0%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636767781103757335&sdata=6DmHhUndTWjK11HZJQi3yidinLIF%2Fo7f2WcH4U713WE%3D&reserved=0> | @UofGCCS on Instagram, Twitter and Facebook <image001.png> _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@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@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
