IPO SIP Incoming Call Route, no match 2

[sroderick]

I have SIP trunks to nexVortex configured, but it does not seem to use my Incoming Call Route. The incoming call does correctly match the trunk. Unless I populate the "Local URI" field, or the SIP Name for a User with the inbound number it won't complete the call. I want the "Local URI" field to be "Use Internal Data" so that each user can have their own Outbound CID, but I want the main number to go to the main hunt group. Outbound seems to be working fine, it's just the inbound call not matching any call routes. This is the message I see:

1976942mS Sip: 18.1037.1 -1 SIPTrunk Endpoint(f52986a8) Present Call, no match (1541*******) from URI in To header or (1541*******) from request URI

The number is obscured, but both are identical and match the number in my inbound call route. Line Group ID matches the trunk number and Incoming Number matches 1541*******.

Any thoughts?

Steve

 

[sroderick]

Okay, someone pointed me to a post that said to put * in the first three fields of the SIP URI. That seemed to do it. Hopefully this will be helpful to someone else now!

 

[Bas1234]

If you pressed HELP on the SIP URI then the first 6 lines showed you.

· IP Office 5.0+: If the wildcard * is used in the SIP trunk's Local URI, Contact and Display fields, that SIP trunk will accept any incoming SIP call. The incoming call routing is still performed by the system incoming call routes based on matching the values received with the call or the URI's incoming group setting. Outgoing calls using the trunk will need to use another URI set against the trunk.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________