Outbound caller ID showing * 2

[raist3001]

I've been going over this config for 2 days now trying to figure out why outbound caller ID is showing a *

My ARS tables are set as
ON; 0NSi(Telephone Number)"@(Registration IP)"
1N; 1NSi(Telephone Number)"@(Registration IP)"
XN; NSi(Telephone Number)"@(Registration IP)"
XXXXXXXXXN NSi(Telephone Number)"@(Registration IP)"


User is using 9N pointing to the proper ARS Route ID

SIP URI on SIP Line has the following entries for Local URI, Contact, Display Name, PAI

Entry 1 *
Entry 2 registration server
Entry 3 Use internal Data

Not sure what I am missing.

 

[amriddle01]

Errrr Entry 1 in the URI you should have a separate URI for inbound that uses the * entries

 

[raist3001]

Am I deleting Entry 1 then?

I should add this is a religious school. They have the rectory and school with different DID's.
I have 2 ARS tables set up to use the different DID's.
The users Short Codes are using 9N pointing to the proper ARS table.

 

[amriddle01]

I'm not going to tell you how to do it as all providers have different requirements. But I typically have all set to use internal data for the outbound URI if I want users to send their DDI, if all users send the main number all three are "Credential user name". Then a separate URI on a different outgoing group with *** entries so calls go through ICR

 

[raist3001]

Thanks, I was a bit confused as the * entries were required by the provider.
They are telling me that my from header is sending the *@ip_Address. So the PBX is sending the telephone number (From Header) as a *.

 

[amriddle01]

It will, the provider is talking nonsense. You only use *s as wildcards for routing incoming calls through ICR, they have no place in the local URI field of an outbound URI usually. As an example Mitel 5000 systems don't ever use the * entry as they are configured in a totally different way, so it can't possibly be a requirement of the provider

 

[raist3001]

My provider is insisting the * URI entry needs to stay.
I deleted this entry along with the registration server URI entry
Now when the client calls I see their extension number.
I edited the SIP tab on each user and then edited the SIP NAME to show the correct number per extension.
I tested this and the proper number is now being displayed.
I also called our distributor for tech support who also told me I needed the * URI entry.
Go figure.

 

[Pepp77]

The * URI entry can be used for outgoing calls if you want to use the s feature in the ARS.

For example a URI of *** to be used for incoming can also be used for outgoing if your ARS is

N;
Dial
Ns08001234567

I am not sure if this only became doable in 9.1.

We use this with Gamma SIP trunks all the time now.

| ACSS SME |

 

[intrigrant]

Take note on the advice of Pepp77, he is 100% right on how to set it up.

 

[amriddle01]

The s never used to work for SIP, indeed I'm fairly certain is doesn't work with our preferred SIP trunk. Gamma are a bit easier to do what you want with outgoing CLIs than most, you can pretty much send anything you want

 

[Pepp77]

Also works fine on Voiceflex and Intelepeer.

| ACSS SME |

 

[raist3001]

S does not work with our SIP provider
In any event, it is working now based on what I outlined above.

Thanks for all the help

 

[intrigrant]

I use the .sCLI on SIP since the feature was released and it works with all SIP providers here locally