Avaya IP 500v2 on 9.1 with PRI (Twinning caller ID issue when calling internally ext to ext)

[JRTrevino]

Hello,

The standard outbound dialing for this site is 9N, using ARS 51, which sends the client's main telephone number.

I setup a separate outbound dialing code of 8N, routing to another ARS table. This ARS table has short code NSSi. When calling from an external number to a DID that is pointed at a twinned extension, the caller ID shows the originating calling party's caller ID just fine.

The issue is when ext 249 calls 265 (265 is twinned to their cell using 8N), the outbound caller Id shows unknown.

Any thought of how to resolve this?

FYI, I've tried toggling the System-->Twinning Tab option "Send original calling party information for Mobile Twinning" from on to off, with no resolution. With this setting on or off, external calls that ring a DID pointing to an ext that is twinned works fine. It's just the internal ext to ext I can't figure out.

Thanks in advance for any input...

 

[intrigrant]

Did you try without the "i", i.e. NSS instead of NSSi?

 

[JRTrevino]

No. I'll do that, and report back. Thanks.

 

[intrigrant]

We have it going without the "i" and then internal and external numbers are shown.

 

[JRTrevino]

No dice. With the i gone, and with the send original caller number setting checked or unchecked, still says unknown.

 

[amriddle01]

An internal call would attempt to display the extn as caller ID, if the provider doesn't like it perhaps they are changing it to Unknown

 

[derfloh]

You need (from 9.0.3 on) ICRs to link internal users against the DID to send die twinned or forwarded calls. Yyyyyyyxxx -> # doesn't work.

NSS(i) alone will only send the originating number what is the internal extension number only. Your provider will not accept that number and will withhold the number.

 

[JRTrevino]

So- the user I tested with has a DID in the ICR. Still showed unknown.

 

[amriddle01]

Just trace it with monitor and you'll have your answer