07-14-2015 01:17 AM - edited 03-17-2019 03:38 AM
Hi everyone!
We have a new sip trunk directly connected from provider into CUCM 10.5. without cube or anything else.
Everything is working fine, all numbers go out with E164 numbering. But there is one problem:
When we use call forward, the PAI number is the original calling number, but it should be the B party number (the forwarding phone).
How can we make CUCM use the B party number in the PAI field? The FROM field includes the orignal number, so that is fine.
Tobias
07-14-2015 01:51 AM
You could look at using a LUA normalization script on the SIP trunk to manipulate the signalling.
Or have you tried just disabling asserted-identity on the trunk completely? i.e. does your SP require it?
Aaron
07-14-2015 02:03 AM
It is required so we need to make it work.
So there is no simple function in CUCM to change that behaviour what CUCM uses in which field?
07-14-2015 02:11 AM
Did you try changing the calling party selection to 'First Redirect number - external' to see if it makes any difference?
07-14-2015 03:00 AM
That changes the FROM field, not the PAI field.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide