Making outbound calls using a PRI from another IPO in a SCN environment

[kjk165]

Hi there,

I am having a issue getting a remote location to dial outbound calls. They can receive calls and make internal calls with in the SCN. I have checked my ARS tables on both ends, Short codes, and SIP Line configuration. Here is what I have:

Main IPO:

ARS- Listed as 50:Main
secondary dial tone: System
Code:
N; Nsi317#######(This would be a phone #) Dial 3K1 Line Group:0

Line: Line 18
Telephone #: Line to (Main IPO)
Incoming Group Id: 601
Outgoing Group ID: 601
VOIP tab:
Gateway IP address: 10.10.10.240 (goes to remote location)
Compression Mode: G.711Ulaw.64k
Supplementary Services; IP Office SCN

Short Code: 9N Dial N Line group id: 50:Main


Remote Location:
ARS:
50:Main
Secondary dial tone: system
Code:
N; Nsi317####### (again, remote locations main #) dial3K1 Line group Id:733

Line:
Line# 17
Telephone Number: (link to Main IPO)
Incoming Group ID: 733
Outgoing Group ID: 733
VOIP tab:
Gateway IP address: 10.10.10.15 (Main IPO)
Compression Mode: G.711Ulaw.64
Supplementary Services: IP Office SCN

Short Code:
9N Dial N Line Group ID: 50:Main

System Status shows the 2 IPO's seeing each other on the SCN. Again, no problem dialing internal #'s or receiving incoming phone calls from the outside. The remote location just cannot call outbound calls. Is there something that I am missing? They system is running on 5.0 (15). So I am getting no help from Avaya or our supplier on this because it's not 7.0 or higher. Any help or thoughts would be appreciated.

 

[Pepp77]

On the remote site your dialling out shortcode needs to send the digits across the SCN line so that the main site receives N and then sends that to its ARS.

So on the remote site you would have something like

N;
Dial
N
733

| ACSS SME |

 

[intrigrant]

At the remote IP Office site, create the following system short code:
Code: 9N;
Telephone Number: 9NsaaaxxxE (aaa = area code, xxx = exchange, E = extension number of the IP Office user – these components can be used to set the outgoing CLI, for example – 9Ns420123E will pass 420123200 as the CLI for extension 200)
Feature: Dial
Line Group ID: 733

At the central IP Office, create a Short Code on the VoIP trunk:
Code: 9N
Telephone Number: NSS
Feature: Dial
Line Group ID: 0 ( Outgoing Line ID of the PRI trunk )


A simple mind delivers great solutions

 

[sizbut]

If you're trying to send the remote locations number as the outgoing CLI for calls on the main sites lines, the line provider may be rejecting the calls. They just see a CLI that isn't valid for return calls to same location for which they are providing a line. Really need to run monitor to see where the calls fail.

Try just working on getting calls going out without any CLI manipulation. When that works move on.

 

[kjk165]

Thanks,

I was able to get it to work finally.

It also helps to change the analog trunk line group ID from 0 to 1 because the PRI is also listed as Line group 0 on the Main IPO. Once I changed that, I was able to call out externally. The analog trunk was conflicting with the PRI, even with the analog trunk being put OOS (out of service), you still need to change the line group id #.

again thank you for all the responses.

 

[intrigrant]

that is mandatory programming on a scn, however most engineers don't bother to change the linegroup 0.

A simple mind delivers great solutions