Dial out through main site from remote site

[headtrip55]

Hello.
I currently have an IP Office 406v2 running 3.2(55).
It uses a PRI for inbound and outbound calls. I am putting another IP Office 406v2 running 3.2(55) at our second location that is connected to our main location via a wireless bridge. They will both be on the same network without any kind of VPN or anything. I am using SCN and I am able to dial by extension between the two IP Offices and the centralized voicemail is working. I have setup the IP Lines on both systems as line 31 and put 31 in both systems incoming and outgoing group ID for line 31.

What I need to do is have all outbound calls from the remote IP Office use the PRI on the main IP Office to get an outside line. What do I need to do to accomplish this?

I have been trying to search this forum for answers but everything I have tried doesnt seem to work.

Thanks a lot,
Jason

 

[amriddle01]

The Line ID for the IP line must be different in both systems for a start.

ACS - IP Office Implement

 

[amriddle01]

Then on the Remote site alter the shortcode for your external calls ( usually ? . dial) from 0 to the Line ID of the IP line.

ACS - IP Office Implement

 

[headtrip55]

The line number of the IP line has to be different at each site or the incoming and outgoing ID's of the lines have to be different?

 

[amriddle01]

Both, for ease in the remote system call the IP link Line number 2, Incoming ID 2 and Outgoing ID 2 it works ok like that but two systems cant have the same Line Numbers

ACS - IP Office Implement

 

[intrigrant]

On the site with only the IP Line you send all external dialled digits to IP Line 31.
Once the call arrives on the main site the number will be evaluated through the system shortcodes here and if it match the shortcode for external calls it will follow these rules.
There is a tech tip for this.
By the way, each IP Line within a SCN must have a unique number for route optimalisation ( anti tromboning ).

 

[kholladay]

Funny I have never used anything other than 0 for PRI and 100, 101, 102 etc for IP trunks and never had an issue. So with two sites I would use 100 for the IP trunk at both sites and if I had 3 I would use 101 for the trunk between the main and the 3rd.

Where are you reading this?

To answer the original question all you need to do is change the ARS table to add a 9 in front of the Telephone numbers and then change the line from 0 to 31.

N; N Dial 0
becomes
N; 9N Dial 31

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"If it worked the way it should you wouldn't need me

 

[intrigrant]

No, each Trunk within a SCN must have unique line ID's, so if you have a trunk with incoming/outgoing ID 100 at one site you do not use that number on another site.

 

[kholladay]

But again where are you reading this? I don't see this anywhere and I am not getting confirmation on that from Avaya.

The only mention of “unique” anywhere is
“Line Number: Default = 0, Range = 1 to 249. Enter the line number that you wish. Note that this must be unique.”

But this references the Line number as being unique to that IP Office and not to the SCN.


Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"If it worked the way it should you wouldn't need me

 

[intrigrant]

You are right in not finding docs about this line numbering but i have learned from practice that anti-tromboning only can be guaranteed using unique line IDs.
The docs say this:

Small Community Networking

IP Office systems linked by IP trunks can enable voice networking to form a Small Community Networking (SCN). Within an SCN the separate IP Office systems 'learn' each other's extension numbers and user names. This allows extension calls between systems and support for a range of internal call features, see Supported SCN Features.

IP Office Small Community Networking is supported for a maximum of 500 extensions across up to 16 IP Office systems.

To set up a small community network, the following are required:

• A working IP trunk between the IP Office systems that has been tested for correct voice and data traffic routing.

• On IP Office 500 systems, IP trunks require the entry of IP500 Voice Networking licenses. For IP Office 4.0, IP Trunks are not supported on systems running in Standard Edition mode. For IP Office 4.1+ IP trunks are supported in Standard Edition mode

• VCM modules are required in all systems.

• The extension and group numbering on each system must be unique.

• The extension and group names on each system must be unique.

• We also recommend that all names and numbers (groups, line, services, etc) on the separate IP Office systems are kept unique. This will reduce potential maintenance confusion.

• All systems should use the same set of Telephony timers, especially the Default No Answer Time.

 

[kholladay]

Ok I am good with that. So it is not a functional requirement but rather a comfort issue, i.e. to keep the administrator from becoming confused. I have started using the unique octet in the IP addressing scheme or the extension leading digit(s) lately and have found that makes my life a bit easier.

Thank you for finding it for me. That was going to drive me crazy.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"If it worked the way it should you wouldn't need me

 

[headtrip55]

I am still having problems getting this to work.

Here is my setup:

Main Location with PRI that I want to dial out of:
IP Line Number 31
Incoming Group ID - 31
Outgoing Group ID - 31
I currently use 9 to dial outside and that shortcode looks like this:
Code - [9]N;
Feature - Secondary Dial Tone
Telephone Number - N
Line Group ID - 0
That is how the sortcode was setup by Avaya when the system was installed and it works for us dialing out.
However I tried to duplicate that shortcode with an 8 to dial out and it just goes to a dial tone and doesnt seem to ring the number I dialed. I dont know why this is.

Remote Location:
IP Line Number 32
Incoming Group ID - 32
Outgoing Group ID - 32
Shortcode:
Code - 9N;
Feature - Dial
Telephone Number - .
Line Group ID - 31

I have a VoIP 5610 phone hooked up to the remote location and when I try to dial 9 and then a number it gives me a busy tone and says disconnected on the phone.

Do I have to put any shortcodes on the IP Line of the main location or anything?

Any help is appreciated.

Thanks a lot

 

[headtrip55]

OK. Nevermind. I got it working. Stupid mistake on my part.

When I changed the Line Numbers on the remote system to make them unique I didnt change the shortcode to use that line number.

I just changed the shortcode on the remote ip office to point to line 32 instead of 31 and it works now.

Thanks for the help.

 

[kholladay]

Main Location
Code: 9
Feature: Secondary Dial Tone
Number: .

Code: [9]N;
Feature: Dial
Number: N
Line: 0 (assuming this is your T1 or analog group)

Remote Location
Code: 9
Feature: Secondary Dial Tone
Number: .

Code: [9]N;
Feature: Dial
Number: 9N (yea that extra 9 needs to be there)
Line: 32

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"If it worked the way it should you wouldn't need me