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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

LCR on IPO Network using SCN 2

Status
Not open for further replies.

jpopa

Programmer
Mar 3, 2005
59
US
This weeks fun question:

I have two IPO's, a 406 and a 401. The 406 has a PRI for all outgoing calls. On the 401 side, I have 4 copper trunks, and the link to the 406. How do I program the system to reroute outgoing calls from the 401 to the 406? Any thoughts? I am guessing with a shortcode, but all my attempts have failed.
 
What type of link are you using?

I have a site where I have done this, but there is one risk which I hope you're covering by using those analog trunks. You need to make sure there is a facility onsite to dial emergency. Therefore you route external calls over your link, and 911 over your trunks.

If your link is VoIP, then create a VoIP line and give it a unique Line Group ID number.

Create a shortcode as follows:

SC: 9n
TN: n
FT: Dial
ID: (your VoIP Line Group ID)

If you use a dial out code at the remote end, you must put it in the Telephone Number field. So if there is a 9 code at the other end, the shortcode would be as follows:

SC: 9n
TN: 9n
FT: Dial
ID: (your VoIP Line Group ID)

Also create a shortcode as follows for 911 / 999:

SC: 911 (or 999)
TN: 911 (or 999)
FT: DialEmergency (or just Dial will work)
ID: 0 (your analog trunk group ID)

Obviously this relies on your VoIP link being setup correctly. Do you need assitance setting it up, or is the link working?


 
The link is working(finally). Should I delete all the other [9]N; etc? It seems those pick my call up before the 9N does.
 
Well, I am having issues with everything except IC over the VoIP link so here's what I've got.

Systems are both 3.0.59. Voicemail is 1.46. I know it should be 3.0, but the customer runs it on a server and they can't really touch it at the moment.

Site A - Local VM, Local PRI

Site B - Local Copper Trunks

From site B, I cannot access voicemail. It has the right IP, and I was able to access it earlier. Is this possibly due to the 1.46 version?

On site B, we have 4 coppers. These 4 coppers ring the local receptionist during the day. At night, the receptionist needs a method to get the call transfered across the network to the recep huntgroup at site A. I can't seem to get a Night Service set up to the HG across the network. Seems like this is reasonable considering they are on different systems. But then I tried having the lines ring her phone directly, and then she would ForwardUnconditional to a site A extension. It seems to go, but it never rings anyone's phone in Site A, but it says it's Connected in Call Status.
 
Fixed the VM. Had to set it to line(funny how searching helps:p)
 
mytelecoms:

I set things up as you suggested, but it still isn't working. Any other thoughts?
 
If you want to reach hunt groups across the SCN, you must program them as short codes. The IP Office does not automatically recognize hunt groups across the SCN.
 
And I did that, but I am still having issues.
 
How are your IP trunks configured? I'd try routing the calls directly to an extension at the other site to verify connectivity. Then route directly to a hunt group, to verify the short code. Then worry about the Night Service destination (in number form) and time profile.
 
Make sure all lineIDs, Linenumbers, users, groups numbers and names (long and short names may not be equal ) are unique. Make sure "voicenetworking" is enabled on your VoIP trunks in the VoIP section.

You MUST use en-bloc dialling over VoIP trunks for trunk breakout, if not it will fail.( [9]N; = en-bloc; 9N = overlap )

For break out on VoIp line to alog/ISDN trunk you should have shortcodes on the VoIP line at the site you want to access the alog/ISDN line.
Lets say all external numbers are starting with a "0", then have a shortcode in your VoIP line like this:
SC = 0N ( assume the other end sends the complete number en-bloc )
TN = N
Function = dial
LineID = the alog/ISDN line group for external access

Beside this keep in mind that since 3.0 LCR will apply to all calls send to lines, except SCN directory numbers as these are considered as internal numbers.
 
Thanks intrigrant, that helped a whole bit. Seems everything is working just great.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top