PRI routing in tandum

[CarGoSki]

Hello all.

I have a 406v2 with a dual pri card and a single pri card. I do realize that I can only have two d-chans in operation while the third can be configured as a t-1.

Currently this 406 uses two pri's. One for service from the central office and one plugged into a point to point t-1 connected to another 406v2. The third will be used eventually to connect to a third site as a T-1.

I route 100 dids to the point to point t-1 from the PRI. Works well. I can dial the site directly using a short code 38N; 38N Works well. I can also use the P2P T1 on the other site to serve up dial tone from the PRI. Works well.

The problem is: On the remote site(the site with P2PT1 only)

Being able to allow the remote site to dial the main site using the dial plan and allowing the use of external outgoing calls over the P2PT1.

On the remote site I can use this incoming route to allow external call processing over the P2PT1:
Incoming Number = *
Destination = 9.

This will route all calls from the P2PT1 to the 9 short code on the main site. Works great.

However, all calls from the P2PT1 are treated as an external call and attempt to dial out. Not so good for trying to reach a main site user from the remote site.

So I can have it one way or the other. I have thought of separating the channels into two different groups, one for external calls and one for user to user calls but it is not dynamic at all.

I did try the wildcard xxxx in the incoming number field and # in the destination field but this did not seem to work at all. I did try 39xx in the incoming number field and a period in the destination field. That did not work either.

I suppose that I could zen for awhile and perhaps it will come to me. In the intrim.....any ideas?

 

[CiCiNL]

So, if I understand you correctly. You have to sites connected using a Tie line PRI Q-sig interface and you want to use break-out on the main site so the sub-site kan dial out using the main sites PRI-trunk?
Default short code '?' is routed over that tie line to the main site?
You have setup an outgoing access code on the main site? If you do so, and you have setup '?' in the sub-site, you do not programm 9 as outgoing access on the sub-site. So only 9 on the main site.
The dial plan on the subsite is 38xx and on the main site 39xx? I think you should consider changing the first digit on one of the sites just to make sure.

 

[redphone]

You will need to create an incoming route for each extension just like you would for DID numbers from the phone company. Wild characters are not allowed in incoming route patterns. Use the MSN tool to save time.

 

[CarGoSki]

I worked it out. I will outline it later for any interested in using the setup.

 

[CarGoSki]

So here is how I route two way traffic between two IPOffices via a point to point T-1. I used Monitor to see what was being sent and received in the ISDN traces.

I first used route
Incoming Number: *
Destination: .
Line Number: Main site PRI

But since I needed to define the sent number as two different number( Main site and Remote) I needed to route to a SC to insert the correct caller id before sending the call.

[SC]MainSite

[8]N;
NsiMainNumberRemoteSite

In essence using the [9] shortcodes to handle the Main site outgoing calls and the [8] to handle the remote site. I quickly found a problem with the incoming route where the dial code was present during forwarded calls.

Not good. Back to the lab to do some more remote site SC work. What resulted is this.

[SC]Remote Site
LineGroup 0 is point to point T-1

39xx; 39N; DialExt; 0
38xx; 38N; Dial; 0
[9]1N; 81N; 0; Dial; Account Code On
[9]011; 8011; 0; Dial; Account Code On
[9]OneRouteForEachLocalTollFreeAreaCode; AreaCodeNsMainSiteDID; Dial; Local Loop Start Trunks; Account Code Off
[9]OneRouteForEachLocalTollFreeACMainSite;AreaCodeN; Dial; 0
[9]911; 911; Dial; LocalLoopStartTrunks


[SC]Main Site
LineGroup 1 is point to point T-1
LineGroup 0 is Central Office PRI
[9]N; NsiMainSiteDID; 0; Dial
[8]N; NsiRemoteSiteMainDIDNumber; 0; Dial
38xx; 38xx; 0; DialExt
39xx; 39xx; 1; Dial

[IR]Main Site
LineGroup 1 is point to point T-1
LineGroup 0 is Central Office PRI

Line 1; ICNum; -8xxxxxxxxxx; Destination 8#
I built a route for 10, 11, 12, 13, 14 and 15 numbers.

Since I can trap for a number in incoming routes but do not want to create a route for every known number I simply inserted an 8 into the dial string at the remote site. Of course I need to remove the eight and can do that in the incoming route of the main site.

ICNum; -8xxxxxxxxxx; Destination; 8# does the work of trapping for a leading 8 [-8], saving the next 10 digits[xxxxxxxxxx] and routing all numbers in the x variable[#] to short code 8 [8]. SC [8] then routes the 10 digit number over the Main site PRI.

The only thing that I can say is to be careful when using * you may receive things in the dial string that you did not intend.

Of course if I intend to have the same range of numbers available to boths site then I would need to put some seperation on the line groups. I would leave line group zero for default shorts codes and move the Main site PRI and Remote Site trunks to linegroup 5. I would then move the P2PT1 to linegroup 10. I suppose that would make a cleaner build.

I am positive that this method can be implemented for FOIP where you can trap by incoming number and route to the appropriate destination.