Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outgoing Caller ID with PRI

Status
Not open for further replies.

tipandring70

Technical User
Oct 27, 2005
128
US
500 8.0 (43) This worked when I started the day, I was cleaning out errors when I deleted a ARS Table. They told me no one could call out so I switched the short code to a table that gives out the main number. I had save a copy of the config to the desktop before I started so I had a copy of the table that I removed. I copied it into the 500 and switch the short code back to go to it. But no matter what ext. I call from all I get is the main number.
Is there a way of forcing out so the call will show the user's DID?
 
User short code can be used to send out CLID
by using Nsixxxxxxxxxx with xxxxxxxxxx as the DID #
 
I was hoping not to have to do that, there is over 500 users.
This was working before I took the table out.
 
If all your ext # match the last part of the DID, you can use ARS with Nsi111222E with 111222 as the area code and prefix .
 
This will allow you to see if the CLI is being sent out.
[URL unfurl="true"]http://www.ipofficehelp.com/HOWTO_ConfigureMonitorComprehensive.aspx#PRITroubleshoot[/url]

If you have an Incoming Call Route created for the user, and it is a valid telephone number that can be sent outbound, then that will be sent on the outbound call without the need for a special short code in the ARS table.

That is:
Incoming Call Route (ICR)
3035551212 Destination 7771

When 7771 makes an outbound call it will send 3035551212. However if you have say, just 1212 in your ICR you will send 1212 as the caller ID which many carriers will reject and replace with the billing telephone number (BTN). You can always use the full TN in the ICR even if you are only receiving say 4 digits.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Thanks everyone,
kholladay, so you are saying that without Any Nsi the outgoing caller ID can get its info from the incoming call route. This seems to be true, is this a default thing? on Friday I was also working on something else. The system I'm working on has 2 sites Site A and site B. Site A has the PRI and voicemail, site B is connected by IP trucks. Ever since the the upgrade Site B has not been getting the called ID on the top line of the 5610 sets has not been displayed. So Avaya told me to put a short code on the ip trunks at site B
Code ?
feature dial
telephone number .SS

So this is the only thing I changed

It did not help, but I left it in, maybe that is wrong?
 
Yes that is default, so long as there is a matching ICR the extension will send this information outbound.

Any Avaya tech that told you to create a short code for sending calls between sites in an SCN is an idiot and should be ignored. Caller ID is passed along with the rest of the call information when an SCN is active. Tell them to stop being lazy and find the real problem and stop trying to take the easy way out.

By default, with no extra programming an inbound call to site A, hitting an AA and then dialing an extension at site B should pass caller ID information for the original call. That is unless you've done something extremely odd.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Thanks for the info kholladay,
I'll see what is happening in the morning.
 
OK now the outgoing caller ID is working. but still since the upgrade the incoming caller ID is still not working.
When a call comes into Site A (main site where PRI and VMPro are) and goes to staton that is logged in at site A I get number and name.
When I login down at Site B (connected by ip trunks) and I get an outside call I get the number of the caller next to whatever Apperance button the call is on (no Name) but on the top of the display (where I get the number and name of a calling station) all I get is "bR"
I have tried the short code (? Dial .SS) at both ends and even tried it with .ss instead of .SS .
Also, when I picked up the call the top row of the display showed my number twice.
but in the phone logs it gives both number and name.
 
I cannot stress this enough. DO NOT build a short code to pass calls between locations in an SCN. This is completely and absolutely incorrect programming.

Kyle Holladay / IPOfficeHelp.com
ACSS/ACIS/APSS Avaya SME Communications
APDS Avaya Data
MCP/MCTS Exchange 2007/2010
Adtran ATSA, Aruba ACMA

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top