SIP Trunk Group- From vs P-Asserted-Identity

[picklemogg]

Hey Gang- Hoping someone might have some info on this... We have Avaya SM/CM 6.2 integrated with Genesys Contact Center. When transfering calls from Genesys to Avaya we want Avaya to send 10 digit ANI (vs an internal extension) to the Avaya phone when the call connects to the end user. So.... right now in the SIP Invite from Genesys to Avaya we pass 10 digit ANI in the "From" header (let's say 111-222-3333) and 7 digit internal extension (let's say 1234567) as the "P-Asserted-Identity". In the Avaya SIP trunk group config there is a parameter "Identity for Calling Party Display" and the option for this can be set to "From" or "P-Asserted-Identity". In my example above if set to "From" it should pass 111-222-3333 as calling party to phone and if it set to "P-Asserted-Identity" it should pass 1234567 as calling party to phone. In our test environment we changed the "Identity for Calling Party Display" option to "From" and it works like a charm- passes 111-222-3333 as calling party. However in our production environment we attempted this same change- set the "Identity for Calling Party Display" option to "From" and we are still seeing 1234567 as calling party instead of 10 digit ANI 111-222-3333. We did confirm in Genesys logs that 111-222-3333 is being passed in the "From" header, but it seems like Avaya is still using the 7 digit extension 1234567 being passed in "P-Asserted-Identity" even though we changed the SIP trunk to use "From".

Does anyone have any thoughts around this? Is there possibly another configuration option that also needs to be adjusted? I'm much more up to speed on the Genesys side of our integration than Avaya, but hopefully my explanation here makes sense.

Any thoughts please let me know. I really appreciate it!

Thanks,
-TJ