Using "Incoming CLI" routes with SIP trunks 1

[wyohick]

Have IP 500 R8.1 I have SIP trunks. Having a problem with routing incoming calls using "Incoming CLI". Have tried just the 10 digits ie...405xxxxxxx digits, 1405xxxxxxx and 1405xxxxxxx@4.xxx.xxx.xxx.(provider's ip address). I'm trying to block some weirdo's numbers but I'm using my cell number to test and I can't even route it to an auto attendant using the "Incoming CLI". Do I need to add these numbers somewhere else in SIP progamming? Any takers? Thanks.

 

[tlpeter]

Open monitor and see what is it receiving.
The number you see in manager should be used.
When there is no exact match then it will use the normal incoming route.

BAZINGA!

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

 

[wyohick]

Thanks for responding. I did check out monitor. That's where I decided to use the 1405xxxxxxx@4.xxx.xxx.xxx but it just follows my default route still.

 

[tlpeter]

I think you should use the number and a prefix in front.
There is a part with dialed and dialing number and not the part you posted.


BAZINGA!

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

 

[wyohick]

Sorry. I'm not using x's I just don't want to show my cell number or my SIP providers IP address. So for example; If my cell is 405-555-1212 and my SIP prvider's IP address is 555.555.555.555 then I'm programming 14055551212@555.555.555.555 in the Incoming CLI because that is what monitor is showing. Right now I'm trying to make it go to an auto attendant to test. Eventually I want to go to a short code that drops the call. Like a "call clear".
Did I misunderstand your last post?

 

[tlpeter]

Yes you did
You need to add 4055551212 and probably a leading 9.
So if you want to dial 405-555-1212 then add the prefix.
So you have the incoming call route and then you need to copy that and add the CLI including prefix.
If you leave this prefix out then there is no best match and it will follow the best match which is the other incoming call route.
The 405-555-1212@555.555.555.555 is not what you see on a phone.
What you see on a phone is what you need to enter in the CLI field.


BAZINGA!

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

 

[intrigrant]

You must add the CLI as you see it presented on your phone and not as it shows in Monitor in a SIP trace.
In Monitor you can see what is presented to the phone, look for Display 1234xxxxx>Ext103 or something like that.

 

[wyohick]

If I'm NOT using a Prefix setting under lines then I shouldn't need it in the route too right? And I'll go check my trace again. Thanks.

 

[amriddle01]

You need the *** URI to get it to Incoming call route



"No problem monkey socks

 

[Billx1]

I ran a test here using Callcentric.

Monitor Trace:
811903mS SIP Call Rx: 17
INVITE sip:17772345678.168.1.26:5060;transport=udp SIP/2.0
v: SIP/2.0/UDP 204.11.192.162:5080;branch=z9hG4bK-3d447fffeb4d2625be57a3f2f89e5609
f: "Jim Jones" <sip:17772401234@callcentric.com>;tag=15675 <<<<<<<<<<<<---------------- Note: f=from (AKA CLI)
t: <sip:17772345678@callcentric.com>

I created 2 Incoming Call Routes, one with just 17772345678 and another with 17772345678 plus 17772341234 as the "Incoming CLI"

I set each route to a different destination.

I called 17772345678 from 17772401234 and it routed to the destination I set for its "Incoming CLI" (17772401234)
and the LCD on the phone showed 17772401234

I called 17772345678 from a different number and it routed to the NON-CLI destination.

Based on my limited, Callcentric tests, I would say to use the number that appears in the LCD of the phone.

PS. Make sure both routes are using the same Line Group ID number.

 

[amriddle01]

Hello....my post ^^^^^^^



"No problem monkey socks

 

[intrigrant]

@amriddle : Good advise must be ignored as we know better.... although that seems to be the opinion of the most here, I have noticed that before.
Makes me often reluctant to reply on "basic" questions