Anyone heard a status update on when Calling Party Name will be fixed for H323? We are using T.38 for faxing which doesn't work with XMedius in MGCP.
CallManager doesnt use the Facility I field in an ISDN message for caller ID. They use the Display I field. TAC suggests getting the telco to change it but the telco will tell you they cannot. I opened a TAC case on this in 2001 and had a ddts. The router gets the caller name fine and you can see this if you do a debug voice ccapi inout, but Call Manager doesnt process it in the Display I field. Call manager does not support the Caller Name coming in on the Facility I field:
Facility i = 0x9F8B0100A10F02015706072A8648CE1500040A0100
Progress Ind i = 0x8283 - Origination address is non-ISDN
Calling Party Number i = 0x2183, '7046463196'
Called Party Number i = 0x80, '2543'
0x9F8B0100A10F02015706072A8648CE1500040A0100 when converted to ascii is Jim, Cook.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.