Probably has to do with the special character. Here was the only bug I found related- https://tools.cisco.com/bugsearch/bug/CSCuo91983
Might be caused by the same root issue but might need a new bug opened. On Thu, Jan 8, 2015 at 11:12 AM, Leslie Meade <leslie.me...@lvs1.com> wrote: > CallerID from the PSTN to H323 is correct. Sip trunk to CUCM is correct. > CUCM to 8841 shows correct. But is it not displaying on the screen. > > > > Same call to another model is fine. > > > > I suspect the issue lies with the “±” in front of the Displayname ? > > > > 16301690.001 |10:27:08.571 |AppInfo |localizeCgpn: StationSIPCdfc on > device SEP6CFA89720901 , CSS = ,useDevicePoolCgpnCss =1 > AlternateCgpn(global)=705264XXXX cgpn=705264XXXX > > 16301690.002 |10:27:08.571 |AppInfo |SIPStationCdfc: CcSetupReq - > unicodeConnectedUnicodeDisplayName='' asciiConnectedDisplayName='±TRUE > NORTH TRAN' > > 16301690.003 |10:27:08.571 |AppInfo |SIPStationCdfc: CcSetupReq - > unicodeCallingPartyName='' asciiCallingPartyName='±TRUE NORTH TRAN' > callingParty='705264XXXX' > > > > Has anyone seen something like this before ? > > > > Leslie > > > > > > _______________________________________________ > cisco-voip mailing list > 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
