Turns out use FQDN wasn’t checked on the SIP profile being used by Jabber on the production cluster. Not sure why that presents itself with changing the information only when the call is connected, not while in progress though.
But at least it’s resolved. Hopefully that change doesn’t cause any behaviour changes we can’t live with or resolve. -sent from mobile device- 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<x-apple-data-detectors://1/0> 519-824-4120 Ext. 56354<tel:519-824-4120;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] On Nov 2, 2018, at 1:55 PM, 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<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook <image001.png> _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net> https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
