SIP trunk between Cisco and Avaya

[Casey Arnold]

We currently have a SIP trunk configured between CUCM ver 11 and Avaya ver 5.  The calls are routing correctly, however, when a call comes across from the Avaya system, we believe that Avaya is prepending the 5 digit extension with a +.  But when it reaches a Cisco phone it is showing up as 91xxxxx.    Does anyone know why Cisco is prepending the extensions with a 91?  We need to convert our Avaya users to use Unity for VM and we can get the calls to Unity, but because the caller ID is incorrect, we only get as far as the Unity welcome message.

Any idea how we can get rid of this 91 prepending our 5 digit extensions?

Thanks in advance for your assistance.

Casey

[Jaime Valencia]

CUCM won't add a 91 without it being configured to do so, you need to look at where you're doing that to remove it, or adjust your configuration so it does not affect those calls.

[Casey Arnold]

Jamie,

I understand that, I was hoping that someone might point me in the right direction as to where to look, but we did find it in System Parameters.

Thanks,

Casey

[Chris Deren · Accepted solution]

review the trunk/gateway calling party transformation, review transformation patterns and system parameters to see if any of these perform the prefixing.

[Casey Arnold]

Chris, You were correct. We found it in the System Parameters.  :)

Thanks,

Casey