Prefering E.164 Alias over H.323 ID Caller ID on C series codec

STEFAN CHRISTEN · ‎01-30-2012

Hi

We have a setup with VCS and local registered C40 codecs. For ISDN connectivity we use a LifeSize Networker as a H.320 gateway. The Networker registers the gateway prefix with its H.323 ID on VCS and has a DDI range that is routed to the C40 codecs. On incoming ISDN calls to one of the C40 codecs only the H.323 ID of the Networker shows up on the screen of the C40 and only the H.323 ID is available in the call history but not the E.164 alias of the caller. Is there a way to prefer the E.164 alias (if available) over the H.323 ID on the C40 for the Caller ID on incoming calls?

There is a xconfig for MXP codecs (xConfiguration IdReport H323: <H323Id/E164Alias/IPAddress>) but unfortunately it doesn't work for C series codecs.

Any help is appreciated

Many thanks in advance

Regards

Stefan

Garvan Long · ‎01-30-2012

Even if you do get the E.164 reported, wont this be the E.164 of the Networker which is not much use any way as i suspect you want the calling number or the remote system ?

Is there a CLI ( Calling Line identifier setting on the Networker for inbound ISDN calls

STEFAN CHRISTEN · ‎01-30-2012

Hi Garvan

Thanks for the reply

The E.164 Alias is the one from the external caller. It's properly delivered to the C40 codec but unfortunately just doesn't show up on the display.

Unfortunately you cannot configure very much on the Networker and it needs to have a H.323 ID configured otherwise it will register with LifeSize as H.323 ID.

Regards

Stefan

crisalex · ‎01-31-2012

Hi Stefan,

Unfortunatelly you are correct, and by designed the xConfiguration IdReport was taken out from the C / EX series. This option is not present any more on this device.

We have tried to raise this as bug but this was not considerd a bug , as it's by design like this, so I would recomend to go for a feature request in this case and based on the business impact that this functionality has it over your business the developer will consider implementing this feature on the next sw releases.

Kind regards

Cristian