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!

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

Internal Call Routing across WAN & Out Main Site...

Status
Not open for further replies.
demanding

demanding

IS-IT--Management
Jan 7, 2008
631
US
Here's my challenge:

We have multiple LSPs in different states. Each location dials 111222 to reach the Help Desk which is outsourced in the main location's city. We want the Help Desk to see the DID of the caller. If they call a local number in each location (that actually routes to 111222), it shows their phone number. But, if they just dial 111222, it shows the main number for the main location so the Help Desk does not know who is calling and they always have to ask ... which upsets the callers. So, I have tried many things and have not gotten far. Just so you know, we also have 2 phone systems in the main location (an ECS and a legacy switch not converted yet). If someone on the ECS/main calls someone on the legacy/main, it is routed in the UDP table as:

UNIFORM DIAL PLAN TABLE

Matching Pattern Len Del Insert Digits Net Conv Node Num

11 6 2 111 aar n


This sends all calls to the other PBX - no problem. But I want to be able to keep 111222 in the ECS switch and have it go out of those local trunks (we have local trunks in each system) as it will show the caller ID. Seems like it should be simple but I'm missing something...any thoughts?

 
Sort by date Sort by votes
I bet your carrier is not allowing you to show the remote sites CLI on your "Main location" trunks.

You need to either get an agreement from your carrier to allow CLI passthrough or modify teh CLI to present a different CLI for each remote site (but onbe that is valid from teh mian site)

so 12345 is from site 1
and 123456 is from site 2


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
 
Upvote 0 Downvote
That's not the issue. The problem is how to get the correct UDP and/or vectoring setup so someone can call x111222 (like they are calling other 6 digits #s) and have it go out the trunks in the ECS system and not route over to the Legacy system and go out (these systems are in the same location/same carrier). Right now the UDP has what I noted above. I need to know how I should set up one specific ext. to stay local in the ECS system, have users call that number and it go out the trunks on that system.
 
Upvote 0 Downvote
You should be able to use:
uniform-dialplan
aar digit-conversion
aar analysis 1 location x (define local route)
puplic-unknown-numbering (define callerID

You can use location x of each media-gateway or port-network to
to define calls routing locally. You will only be able to send calling number out on isdn.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting
 
Upvote 0 Downvote
I figured it out finally. I was getting hung up on a couple things even though I had all of that in place. Thanks!
 
Upvote 0 Downvote
Way to go Sandy. Good job. This is the same as setting up dialing 911 using local facilities.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting
 
Upvote 0 Downvote
Ok - sending out all 10 digits. However, it appears we may need to send only 6 digits...I changed the public unknown table from 10 to 6 and it drops the first digit so it is only sending 5. What am I missing? I have tried several variations but 5 is as close as I can get.
 
Upvote 0 Downvote
Here's my public table:

Notice 17 and 18 are going across trunk 62 - I removed the CPN prefix and change the length to 6 - but it strips the first digit in the 6-digit extension and if you notice entry "20" and then there is "21" out of view that not all ext start with a "1"...

NUMBERING - PUBLIC/UNKNOWN FORMAT
Total
Ext Ext Trk CPN CPN
Len Code Grp(s) Prefix Len
6 8 590 6
6 17 61 757687 10
6 17 62 6
6 17 170 757687 10
6 18 1 949622 10
6 18 61 949622 10
6 18 62 6
6 19 61 858509 10
6 19 62 858509 10
6 19 190 858509 10
6 20 61 312759 10
6 20 62 312759 10
 
Upvote 0 Downvote
Code: 
station is 171234, DID is 2224171234 - send CLI 2224171234 over TG 62
station is 123456, DID is 2224123456 - send CLI 123456     over TG 99
station is 171234, DID is 2224171234 - send CLI 171234     over TG 99
station is 172222, DID is 2224172222 - send CLI 2224174000 over TG 62
station is 17xxxx, DID is 222417xxxx - send CLI 222417xxxx over TG 62

Ext Len 6 for total Length 10 Prefix inserts 4 digits


change public-unknown-numbering 1                               Page   1 of   2
                      NUMBERING - PUBLIC/UNKNOWN FORMAT
                                           Total
Ext Ext           Trk       CPN             CPN
Len Code          Grp(s)    Prefix          Len
                                                     Total Administered: 5
 6  1             99                        6
 6  17            99                        6
 6  17            62        2224            10
 6  171234        62        2224            10
 6  172222        62        2224174000      10

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

37 years Bell, AT&T, Lucent, Avaya
Tier 3 for 27 years and counting
 
Upvote 0 Downvote
Sorry - this is going right over my head. Thanks for the information.
 
Upvote 0 Downvote
Back on this topic! I have the ECS systems worked out...but now I have a location on CM3.1.4 with an LSP - the LSP location dials the 11-1222 number and it goes out of the main location's trunks to a local # - but it is showing the main location's main #. The main location can call the 11-1222 number and when the receiving ends gets the call, they see the individual's DID. So why doesn't the LSP caller show that? I have messed around with the Public table and nothing changes. Still shows the main location main number. So, if I can't get that to work, how can I set up a vector for the LSP location and route the call to a toll-free number but still having that site call the 11-1222 number?
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

M
  • Locked
  • Question
Call from internal trunk sac/cf override
Replies
0
Views
135
milske
M
Gus1972
  • Locked
  • Question
Blast Conference (Internal)
Replies
1
Views
234
bignose21
bignose21
SouthernKnight
  • Question
Inbound EC500 not converting to Internal Extension
Replies
8
Views
330
SouthernKnight
SouthernKnight
M
  • Locked
  • Question
Internal Trunk override sac/cf of station
Replies
0
Views
151
milske
M
met1016
  • Locked
  • Question
vipers across LD networks
Replies
5
Views
900
JefferP
JefferP

Part and Inventory Search

Sponsor

Back
Top