First foray into SCN 1

[Textron68]

I will be setting up an IP Office SCN to replace an existing Merlin system which is operating in tandem across a T1. It is more than 3500 feet from end to end. IT has not approved VoIP on the network for IP endpoints, so IP phones are not an option at this time. So, traditional Digital and Analog phones will be used. We can however use VoIP for our connection between the units, the local network is fiber between the communications closets. The site currently has 3 T1 circuits (PRI for outside service, T1 for intra-corporate and T1 tie-line between the two units). We want to eliminate the T1 tie-line and just have the PRI outside and the intra-corporate (which will be PRI when upgraded). Use SCN for the tie between the two units. I understand the majority of the SCN, but when it comes to the trunking… Side (a) will have all the trunking, Side (b) will only have phones and no trunks. ‘Breakout’ is not supported on the analog phones (both (a) and (b) will have analog and digital). Users will dial ‘9’ for outside local/long-distance or ‘8’ for intra-corporate. For Side (a) easy enough (been there done that), Side (b) what do I need to do to setup the ARS to go across the SCN to Side (a) and make the call using the standard dial codes? Or are the trunks seen and available at Site (b)? Also, on the Incoming route, is there anything I need to do at Side (a) to send the calls to Side (b) across the SCN, other than put in the extension?
Any other ‘gotcha’ incidents? I understand the dial-plan interaction and Naming conventions for use with Voicemail Pro.
We will be initially rolling out with 4.2.11 to maintain consistency with all the other units in our system. I am waiting to hear about the reliability of the R6 once it is rolled out later this month.

 

[intrigrant]

If you are not confident in the setup then call for assistance onsite or get a training regarding SCN.
Reading your post i would say you are familiar with SCN:

Side (a) will have all the trunking, Side (b) will only have phones and no trunks.

you need a ip trunk on bothe sites, program shortcodes on the site without PSTN asif you do have PSTN lines but now send the calls to the IP Trunk.
On the site with the PSTN trunks you need to program shortcodes in the IP trunk.
Example:
Site B ( no PSTN )
IP Trunk with incoming and outgoing ID set to 99
SC = 9N;
TN = 9N
Action = Dial
Linegroup ID = 99

Site A
PSTN lines with incoming and outgoing ID set to 0
IP Trunk with incoming and outgoing line ID set to 90
Shortcodes in IP Line with ID 90
SC = 9N
TN = N
Action = Dial
Linegroup ID = 0

For user to user dialling you do not need any shortcode, that is part of the SCN deal, for huntgoups you do need shortcodes unless you make them distributed groups.

For the incoming call route yust enter the extension number were the call has to go to, doesn't matter on which site that user is.
Usually if a user has a incoming call route setup with a DDI numer then that number is used as CLI for that user.

That does not work over SCN, you have to do the following:
Site B ( no PSTN )
IP Trunk with incoming and outgoing ID set to 99
SC = 9N;
TN = 9NsDDI were DDI is depending on what you receive from the provider, here we get the full national number excluding the leading zero, so DDI number = 0101234567, the TN part of the shortcode = s101234567. the last three digits corresponds with the extension numbers so i would make one SC with .s101234E in the TN part, the E adds the extensionnumber of the caller dialling the number.
Action = Dial
Linegroup ID = 99

Site A
PSTN lines with incoming and outgoing ID set to 0
IP Trunk with incoming and outgoing line ID set to 90
Shortcodes in IP Line with ID 90
SC = 9N
TN = N.SS this forwards the received CLI to the PSTN
Action = Dial
Linegroup ID = 0

 

[Textron68]

intrigrant,
Thank you. Very useful information. In my mind planning it out, I was on the right track. Just needed confirmation. The info on N.SS for sending the CLI is good to know, but we typically send out our Main number on all calls with few exceptions.

 

[intrigrant]

Good luck then, it is not hard to set up if you know the basics.