SIP Trunk/Incoming Call Route/Incoming CLI 1

[Kajue]

I'm wondering if anyone else can test this issue.

I have a 500V2A in Essential with SIP Trunks at R11.1. It was installed as 11.1 237 and I upgraded last night to see if this issue would be resolved to R11.1 FP1. My issue is that I cannot get the system to route based on Incoming CLI. I can see that the incoming caller id is correct in system status. The call comes in and routes to the ICR with just the incoming number and no incoming cli field. If I add an incoming cli field to that entry it won't match the call to an ICR at all.

I have the same SIP trunk provider on several other systems and have this working on at least 3 other systems at 11.0.4.0.0b74 and 11.0.4.1.0b11.

 

[derfloh]

Is the SIP URI configured to Auto for incoming?

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[Kajue]

This customer I had put the prefix in the SIP Line so that I didn't have to mess with wildcard short codes to dial out from voicemail or call history. So the system was trying to match 9+the incoming caller id. Removed the prefix from the line and everything matches perfectly.

Since 2004 working as a local Vendor.
-Avaya IP Office, NEC, Nortel, Samsung, AllWorx-