Twinning Hunt Group calls no longer sends original caller id

[JimFed]

We upgraded our internal IP office to 11.0.4.3 and it appears that since we did that when twinned Hunt Group calls are sent to our Cell phones it does not send the original Caller ID
It had been working fine since March when we all started working from home. Nothing else has changed so we think it related to the upgade on phone system
Anyone else seen this. Normal twinned calls direct to extension does send the correct Caller ID. We were running 11.0.4.2 before we upgraded

 

[Ekster]

If you are using SIP Trunks, try setting the caller ID in the SIP tab of the hunt group.

“Some humans would do anything to see if it was possible to do it.
If you put a large switch in some cave somewhere, with a sign on it saying 'End-of-the-World Switch. PLEASE DO NOT TOUCH'.
The paint wouldn't even have time to dry.”

Terry Pratchet

 

[JimFed]

If we put our phone number in the huntgroup box it will send that number out on a twinned call and if we have nothing in there it sends us 1 503 as caller id 503 being our huntgroup ext.
We used to get the original calling party. That is what we are trying to fix

 

[JimFed]

FYI so some other poor sucker doesn't have to spend all the time we had to. We finally opened a ticket with Avaya. They came back and said the upgrade did change the way it works. Ticket is still open but they are probably going to come back and say it is by design

 

[icet500]

If sip trunk, switch the sip uri for twin/forward to caller. If PRI, check mark send original caller id.

 

[teletechman]

On 11.0.4 I was told that you need to make the forwarding tab of the SIP URI original caller for this to work.
Mike

 

[TouchToneTommy]

I make a new ARS that has entry for N; / Dial 3K1 / NSSi / {line group} and a new system shortcode 8N / Dial / N / {New ARS}

Configure forwarding and twinning numbers with 8+number instead of 9+number

On a SIP URI, under Local URI and Contract, Forwarding/Twinning, set to Original Caller