R8.1 breaks outbound Caller ID on SIP when using P-Asserted-Identity (PAI) 1

[DavidCT]

It's back... had the exact problem when going from 7.0.27 to 8.0.18 -- no outbound caller ID. Here's the old thread:

http://www.tek-tips.com/viewthread.cfm?qid=1677116

Upgraded from 8.0.44 to 8.1.43, and the problem is back. Ran a SysMon trace on a few calls and can see there is no P-Asserted-Identity (PAI) string being sent at all in the Invite. Downgraded back to 8.0.44 and the correct outbound caller ID works fine and the P-Asserted-Identity string is back in the Invite.

Anyone else using PAI for outbound caller ID dare to test?

Avaya acknowledged a fix in Tech Bulletin 143, Page 5 on the 8.0.42 release.

 

[amriddle01]

Sounds about right from the Avaya QA folks

 

[hairlessupportmonkey]

No one had the issue in the Beta trials as far as Im aware....

ACSS - SME
General Geek

 

[andynetcon]

Thanks for the heads up, David. Disappointing to hear that this continues to be an issue.

 

[jamie77]

I logged an issue with CLI in 8.1 Beta. It defaulted to P-Asserted when we use the FROM field. Our SIP ITSP was sending the wrong CLI in the P-Asserted field (send a random 020 number sometimes). Though I can say it worked either way duting trial

Jamie Green

Football is not a matter of life and death-It is far more important!!!!

 

[crashtest1000]

Just spent a day on this thanks for the heads up do you know if ther is a PB or fix?

 

[tlpeter]

If it this problem then upgrade to 8.1.52

IPOFFICE-31745 PAI field missing on outgoing SIP call

BAZINGA!

I'm not insane, my mother had me tested!