has anyone heard of using this card for teleconfrencing with a T1 PRI in MICS 7.0 so what the customer wants to accomplish is use a device that used to connect to a local provider ISDN lines to tleconfrence but someone told him he can do it through the KSU is this possible.
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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
ISDN/BRI-U4 1
- Thread starter firenut1
- Start date
I have seen a customer use a BRI interface for videoconferencing. Basically, they use a Prime to gain access to the outside world, and Basic Rate (Norstar emulating the C.O. via BRI card) towards the videoconferencing eq. It works, but it is 1) tricky to set up, and 2) Norstars get a bit whiggy when they get too big or reach their limitations. It can be done, though.
- Thread starter
- #3
The procedures are too long to list here, but when you select BRI (either one) under 'Hardware', a whole bunch of BRI parameters show up. You will absolutely need the book to set it up. I don't have the 7.0 docs, but you will need them. It isn't rocket science from what I remember, but it was tricky. Soory I can't be more specific......my hands are already smoking....ha ha ha ha
-
1
- #5
I have info on this .I did it with a BCM BRI card.It was used for video conf.It took alot of trial and error.
Good-Luck
Configuration Rules:
Norstar and High Speed Video
Norstar and
Polycom ViewStation 512
This configuration guide and walkthrough is
the second part of the High speed
Videoconferencing solution found on the
ITAS Customer Solutions web site. The first
part details how to chose a
videoconferencing unit. This second part
along with others that will be published,
detail how to connect various products from
differing manufacturers.
Polycom has recently renamed their product
line. The product tested here is now called
simply ViewStation and is capable of speeds
up to 512k. The ViewStation MP is capable
of hosting multi-site videoconferences but
basically connects the same. The
ViewStation V.35 can connect at up to 786
kb/s and adds direct to LAN connections as
well as a T1/PRI jack.
Installation & Configuration
The following steps will show you how to
configure your Norstar system with a
Polycom videoconference unit. The process
was tested with a Polycom ViewStation 512
running at 384 kb/s (only 3 of the 4 available
BRI loops active). This unit has an S loop
ISDN interface. To keep costs lower, we
used an S loop card instead of 4 NT1s. We
also tested with MICS 4.0 PRI and BRI
ISDN. If you choose to use U loops on the
station-side, please refer to the Solutions
and TIPS on the ITAS web page. The URL
and TIPS list is included on page 10 just
before the Troubleshooting section at the
end of this Tip.
BRIBRI
PRI
PSTN
Station-sideTrunk-side
Further references to S loops can be replaced with
station or set-side U loops and NT1s (if the product
requires an S interface and you use U loops).
STEP 1: Deployment Considerations
Hardware Requirements
• Perform a traffic assessment of existing
voice and data traffic to determine if the
number of videoconferences you want to
hold (time, duration and bandwidth) will
impact existing traffic.
• Does your traffic assessment indicate
the need for more ISDN channels (via
PRI trunks or additional U loop BRI
trunks and cards). Additional BRI trunk
cards may lead to additional trunk
modules and a fibre expansion card.
See the chart below.
Existing
Equipment
384 Kb/s video
system
512 Kb/s video
system
CICS
(CICS 2.0+)
3 BRI trunks for
video (U loop)
4 BRI trunks for
video (U loop)
3 station loops per
unit (U or S Loop)
4 station loops per
unit (U or S loop)
6 CO numbers 8 CO numbers
6 DNs 8 DNs
Clock control Card Clock Control Card
MICS PRI 3 or 6 CO numbers 4 or 8 CO numbers
(MICS 4.x) 3 loops per unit
(U or S loop)
4 loops per unit
(U or S loop)
6 DNs 8 DNs
Optional Fibre expansion Fibre expansion
MICS BRI
(MICS 2.0+)
Numbers, DNs and
loops as MICS PRI
Numbers, DNs and
loops as MICS PRI
Trunks as per
CICS
Trunks as per
CICS
Clock control card Clock control card
Optional Fibre expansion Fibre expansion
• Do you have Sufficient BRI loops and
trunk cards to connect the video unit(s)?
• Central Office assigned phone numbers
(network DNs). BRI One per channel or
one per trunk
• Which trunks will the calls be routed out
over? Do you need routing table
entries? Do you use different Long
Distance Carriers?
• Do you have 6 target lines available?
• Can you map your internal Norstar DN
numbering plan to accommodate
matching the last four of the network
DNs?
TIP You can use the Video network DNs for voice calls
and regular appearances on sets as Norstar sets will
not present a video call and the Polycom will not
answer a voice call.
The Diagram and configuration table below will clarify the following details. If using PRI, there will
not be any SPIDs from your SP (Service Provider) or CO (Central Office).
PRI or
3 BRI
3 U or S BRI
Mux
Polycom 512
Videoconference Unit
CO Trunk-side Loop Norstar Configuration Video unit
Ntwk DN BRI SPID
394-2439 00139424390100 401 00139424390100 394-2439 220 439 2439
394-2651 00139426510100 00139426510100 394-2651 221 651 2651
394-2924 00139429240100 402 00139429240100 394-2924 222 924 2924
394-2992 00139429920100 00139429920100 394-2992 223 992 2992
394-3012 00139430120100 403 00139430120100 394-3012 224 012 3012
394-3054 00139430540100 00139430540100 394-3054 225 054 3054
Trunk-side U Loop
U Lp Lp SPID Ntwk DN
Target Line
Tgt Line Rcvd # N* DN
Station-side S Loop
S Loop DNs on Lp Loop DN
Unit SPID Unit DN
201 2439 2439
243900 394-2439
2651
265100 394-2651
202 2924 2924
292400 394-2924
2992
299200 394-2992
203 3012 3012
301200 394-3012
3054
305400 394-3054
The following definitions will be used:
PSTN (or CO) Details:
Network DN The 3 or 6 phone numbers assigned by the CO that you advertise as being
answered by the videoconferencing unit. The CO may give you 1 DN per BRI
loop. You do not require 6 DNs. If this applies to you, enter the DN in both
locations as if it were a different number. If you have PRI, you will need 6
DNs. The network DNs do not need to be contiguous.
SPID (if BRI) Program the SPID directly into the matching U loop
N* DN The Norstar DN that is assigned to a station-side U or S Loop and has an
appearance of a target line with the appropriate received digits (if PRI or
BRI), or a direct Appear&Ring of that BRI line.
Loop DN (s) 2 Norstar DNs programmed per loop. One will be assigned as Loop DN.
Unit SPID Matches the Norstar DN assigned to that loop plus 00 on the end.
Unit DN Matches the Network DN above and is programmed into the videoconference
unit.
S Loop Anywhere an ISDN S loop is mentioned an ISDN U loop terminated at an
NT1 can be substituted. Configurations with NT1s have been tested.
System Considerations
• As you can see from the table above, Network DNs match the CO SPIDs that match the
trunk-side U loop programming (ISDN rules) AND must also match Norstar DNs assigned to
the station-side loops. These then match the Unit SPIDs (ISDN rules). Finally, the unit must
have the Network DNs programmed into it as its DNs.
• Depending on the configuration you have (N* DNs already deployed and Network DNs for the
video unit), you may be forced to go to 3, 4 or even 5 digit numbering plan on the Norstar.
The Polycom system rules have been tested with 3, 5 and 7 DN numbering plans.
Example The lowest Network DN is 394-2439. In a 3 digit system, 439 cannot be assigned as a DN. The
system needs to be boosted to a 4-digit pattern. But then you may find that 24xx cannot be assigned. A
workaround here is to accept 2667 (earliest ISDN DN available) and then “change DN” from 2667 to 2439.
• If you cannot assign DNs that match the last series of Network DNs (2439 from 394-2439),
you must then rework your DN deployment and “change DNs”. In MICS or CICS 2.x to 4.0,
Norstar DNs must match Network DNs.
TIP MICS/CICS 4.1 will allow the addition of separate Network DNs for ISDN sets. So a video unit added to
Norstar will essentially have a separate internal and external DN. Technically, instead of presenting a call to the
Norstar DN, the call is presented to the Network DN. The video unit programmed with this number will
recognize that the call is for it.
• The SPIDs of the station-side U loops must match the Network DN and thus the Norstar DN
with the following pattern: If the network DN is 394-2439, the Norstar DN is 2439 and the
SPID is 243900. This is not a limitation of this configuration, but is a requirement of ISDN.
• If the incoming video call is via PRI, target lines are required to present the call to the video
unit. If you are using BRI trunks as shown above, you will need to auto-answer the lines
associated with the BRI trunks. The received digits can be as small as 3 in length. The CO on
that trunk type must send digits. BRI “lines” can also be programmed directly onto the set.
Example A call presented on 394-2439 is handed to target line 201 programmed with received digits of 2439.
Line 201 is assigned to Appear&Ring on DN 2439 (video unit). 2439 is also the DN assigned to LT U loop 201
on KSU card 1 (right most card on KSU).
CICS versus MICS
CICS
A CICS system is limited to only 8 loops. To support 384 kb/s video, you would need to use 6
loops (3 loops to your video unit and 3 loops to your ISDN LEC) when holding a conference. This
would restrict the system to 4 simultaneous voice connections (2 loops or 4 lines). A 512kb/s
system would use all the trunks. The next diagram illustrates the trunk requirements of a 384 kb/s
during a videoconference:
PSTN
3 Video
3 Video
2 Voice
NT1s Mux
The solid lines are trunks from the 1st BRI card. Three are used for 384 video and one is available
for other traffic shown as voice at the bottom. The dashed line trunks are from the 2nd card. Three
trunks are used for the unit and one is available for other traffic. Here, we’ve shown the spare
trunk from 2nd card being used as a voice trunk to the network. If you want to do this, the 2nd card
must be a U loop card or the U loop is terminated in an external NT1.
TIP You may want to limit the video unit to 128 kb/s during peak voice traffic periods.
MICS
You have several options with a MICS system. Not limited to PRI on core, you can deploy BRI
off-core in expansion modules, so unless you have a fully populated system, you may or may not
need additional trunk modules or fibre expansion cards.
TIP If you are adding ISDN cards (PRI or BRI) to an existing system, you will need a clock control card.
TIP Loops allocated to the video system do not need to be on the same card. You can use up spare loops on
existing cards before purchasing more ISDN trunk cards.
You will need to have numbers dialed specifically for the video units. These numbers are then
assigned to Target Lines. This is most powerful with PRI in that when not using the video unit, all
channels are available to voice or data traffic. However, the video units will not answer voice calls
and Norstar sets will not answer video calls.
BRI This solution will deal with PRI as the trunking connection to your LEC. BRI specific details will be
differentiated by TIP style bullets such below:
BRI BRI Trunks on the other hand give you the flexibility of using dedicated lines depending on the amount of
use you will require.
Step 2: Local Exchange Side
CO Assigned Data
PRI
If you have a PRI trunk, select 6 numbers from the pool of numbers assigned. These numbers will
be associated with the video conference unit e.g. 394-2439 to 304-3054. The numbers don’t have
to be contiguous. These numbers will be assigned to target lines.
You will also need to confirm whether the CO is allocating channels in an ascending or
descending method. Ascending means the first call coming in will be assigned to channel 1 and
moves up. Descending starts at channel 23 and moves down. This is to ensure the PRI link
allocates channels with minimum potential for collisions with incoming calls. This also applies to
other data and voice calls, not just video.
Which protocol is the PRI trunk? Norstar supports NI2, DMS100 and AT&T 5ESS.
BRI If you have BRI trunks you will need target line numbers and received digits. Refer to the additional TIPS
listed for specific BRI programming such as SPIDs and network DNs. Units require one BRI loop per 128 kb/s of
speed.
NOTE BRI trunks must not be programmed with EKTS.
Step 3: Local Exchange Side
PRI Configuration
MICS 4.x is required for PRI trunking.
Before changing any system setting, backup your system. This will allow you to repeat the
process if it fails after the first attempt.
Disable the PRI card in: Administration/Maintenance/Module Status (Feature **Config). PRI cards
must go on-core (module 2) and require a clock control card. Set card as PRI in
Admin/Hardware/Module 2/Card 2/PRI
PRI in slot 1 will have lines 001-023 while a PRI card in slot 2 will have lines 024-046.
In Administration/Hardware/Module 2/Card 1
Select the appropriate protocol: NI2, DMS100, 5ESS.
Select the B Channel sequence: Ascending, or Descending
TIP You can reduce collisions (glare) with channels grabbed by incoming calls by choosing the opposite method than the
CO e.g. if the CO is ascending, choose descending.
Set all other values to those assigned by the CO or leave them default.
Enable the PRI card or the specific lines if partial PRI in: Administration/Maintenance/Module
Status.
You may require Softkeys to activate additional PRI lines. Contact your Norstar Rep.
Enable required lines in: Administration/Maintenance/Provisioning
NOTE PRI and BRI lines can also be referred to as channels.
BRI Identify which lines are assigned to the BRI loops you will receive incoming calls for the video terminal. There are 2
lines per loop. BRI cards can be located in modules other than module 2. Each loop must be provisioned and also has 2
lines that must be provisioned as above for PRI.
Step 4: Video Set Side
Program Trunk Module and S Loops
If you have the expansion space and are considering a device that is equipped with
an S loop interface we recommend you purchase an S loop BRI ISDN card. One S loop card may
cost less than 3 or 4 NT1s. NT1s are required to convert U loops to S.
Our example has an S loop card off-core in trunk module 4. Disable the ISDN BRI S loop card in:
Admin/Maintenance/Module Status.
For each loop (401 to 403 are the first three of card 1 in module 4), set the loop type to S and
leave the sampling to the default fixed. Admin/Lines/Trunk Data/Trunk Type
Assign DNs to the loop and each B1 and B2 channels of that loop. For example 401 B1: 2439
and B2: 2651, 402 B1: 2924 etc (one DN per line). Admin/Hardware/Module 4/Card 1/Assign DN/
and Admin/Hardware/Module 4/Card 1/Assign DN/Show loop 401/Assign
TIP If no DNs are shown as available, you will need to convert portable DNs to ISDN DNs. This can be done in
Admin/System Programming/Change DN Type
NOTE Some video units will require one DN per loop while others will require one DN per channel (2 per loop).
Repeat for each loop that will be connected to the video unit.
Provision each loop under Maintenance/Provisioning/Module.
Change DNs to match the last series of the Network DNs chosen. Some units may not require the
Norstar DN to be changed to match. SysProgramming/Change DNs/Old DN – New DN. 2669
becomes 2439 in this example or for a 3 digit numbering plan 669 would become 439. We will
use the 4-digit example moving forward.
TIP If you are using U loops for the unit, you will also need to enable each channel (line) in each loop.
NOTE MICS 4.1 does not require DN matching. There is an option available to ISDN sets where the network DN is
mapped to the OLI number programmed for that set. Under set options, program the network DN as the OLI number, then
turn on the mapping option.
Step 5: Outgoing Calls
Program Line Pools and Routing
Assign Line Pool access code. If using PRI, select Pool PRI-A (card in slot 1) or Pool PRI-B (card
in slot 2) for outgoing calls.
TIP If you cannot assign the number you want to use, it may be in use elsewhere.
You may want to utilize Norstar’s powerful routing table feature to route the video call setup out
specific trunk types depending on time of day, long distance carrier rates etc.
TIP you may be able to simplify the number(s) dialed by the video unit if you use the dial out feature of the routing
service.
TIP If you need to call to a PBX or key system in a specific country, you may want to examine public DN lengths to see if
the Norstar defaults are long enough to support the number of digits you may have to dial. These defaults are found in:
Services/Public DN lengths/011 etc
BRI Before you can assign line pool access to the video unit, you need to assign BRI lines to those line pools.
Step 6: Incoming Calls
Target Lines and Received Digits
For the following steps, a spreadsheet table is included at the end of this document to show the
relationship of all the DNs and lines programmed into the Network, Norstar, ISDN loops and
Video Unit. Please refer to this as we discuss the programming steps.
Select and program each target line (you will need one for each 64 kb/s you want to use) as
public and the received digits that are unique to each channel coming in. For example, the
numbers chosen from the CO pool noted earlier were 394-2439 to 394-3054 would indicate
received numbers of 2439 to 3054 (or the minimum number length to identify a unique number of
all incoming received digits – three shown here for example only).
TIP Your video unit may be able to function with 1 Network DN, or with 3 (one Network DN for each BRI loop).
The first line will have 2439 as its received digits while the last will have 3054.
Admin/Lines/line 145/Line Type/Public
Admin/Lines/line 145/Rec’d #/2439
Target Lines can be chosen from the line ranges:
MICS 4.x 145-272
CICS 2.0+ 49-75
For example: The far end originating the call will dial 394-2439. This will come in any PRI
channel. The system will see 2439 and note that target line 145 has been programmed for
received digits 2439. The call will be passed to any device with an appearance of that target line.
BRI BRI trunks from the LEC each have their own numbers associated with them. You can assign this line without having
to use a target line. This is referred to as a dedicated line.
BRI BRI trunks used in conjunction with LEC hunt group type features can also operate the same as the PRI example.
Step 7: Video Set
Program Norstar DN Line Access
For each DN, assign line access (appear and ring) of the appropriate target line and line pool
access for outgoing calls(PRI-A yes).
Admin/Set/Show Set: 2439/Line Assignment/Show Line 145/Appear & Ring
Admin/Set/Show Set: 2439/Line Assignment/Line Pool Access/PRI-A Yes
Repeat this for each DN (6 for 384 kb/s) chosen in Step 4.
NOTE Some systems may require 6 DNs (one per line or two per loop) while others may only require 3 (one per loop). For those
systems that only require 3 DNs, you will still need to use 6 DNs. The unit will then only require 3 DNs programmed in it.
Step 8: Video Set
Program Video Unit Line Access
This is where the huge variation and potential problems may lie: basic video conferencing should
be able to be established with the following steps:
Program the network DNs you have chosen for the video units (example 394-2439and loop 401,
977-2924 for loop 402 etc) for each loop or channel into the video unit. You may want to try at this
time to program the same Network DN into each B Channel of a BRI loop. These numbers are so
that when the unit advises a remote end who it is, multiple links can be established (refer to the
Walkthroughs below).
Setup/Configuration/Mux/Numbers
Program the SPIDs to match your Norstar programming: DNs padded on the following rules:
2439 converts to 243900. The SPID needs to be formatted from Norstar DN on that loop. A
minimum padding of 2 zeros on the end is required but some units may require additional zeros
on the front to reach a specific SPID length. Do not set PBX option on.
Setup/Configuration/Mux/ISDN
Select the ISDN type for each loop: NI-1
NOTE Norstar only supports NI-1 BRI ISDN on S loops.
Program the destination phone numbers of any videoconference units to be dialed. Depending on
the system to be dialed you may need anywhere from 3 to 8 numbers.
The same process applies to systems from 128 kb/s to 786 kb/s.
Some systems may have address books that allow you to select the destination ad then will
automatically dial all the numbers preprogrammed. Others will require you to enter all the DNs.
Yet others will only require one DN to be dialed initially and the units will then negotiate the
remainder.
Walkthrough 1: Outgoing Calls
In order to help clarify what each of the above programming will accomplish, this section will walk
you through an outgoing call. This walkthrough will describe the end-to-end establishment of a
point-to-point videoconference with 2 Polycom ViewStation 512s.
1. Power on the video unit and monitor
2. As the unit comes on line, it displays the status of each BRI link. The Norstar BRI card also
displays the status of each link. Solid green lights indicate that the link is fully established.
3. Either dial in the number of the remote video unit or select it from the included phonebook.
Only one number is required. We will use 394-2439 as the first number of the target unit. You
can also select the videoconference speed at this point. A limitation in the Polycom is that
calls that are up to 128kb/s can be dialed independently i.e. 2 numbers dialed
simultaneously. This actually circumvents the problem of requiring multiple DNs: 1 DN can be
used twice. Above 128 kb/s, the call is bonded and the unit dials one number then waits for
the receiving unit to transmit the other Network DNs assigned to it. The sending unit then
dials these other 5 numbers simultaneously. This is where 6 numbers are required as the unit
can get confused with multiple calls dialed to the same Network DN. Other products may
behave differently. The ITAS Customer Solutions Group will test and publish the engineering
rules for other products as we can.
4. The unit will display 6 yellow circles on the screen. Each represents a B channel.
5. The number is dialed (with a 9 preceding to select pool PRI-A). The device on loop 401 is
associated with the Norstar DN on loop 401 (2439). 2439 has access to pool PRI-A. If no
Line Pool code was used, the Norstar would examine the number dialed to see if Routing
tables and Destination Codes applied. If they did, the Norstar would route the call over the
specified trunk (s)
6. The far end ViewStation acknowledges the inbound call and the request for a conference at
384 kb/s. It transmits the other 5 network DNs it is programmed with (394-2651 to 394-3054
in this example). The ViewStation uses one DN per loop as opposed to one DN per channel.
7. Our near end displays a 50% green circle on the first B Channel to indicate that a connection
is under negotiation.
8. Our near end then dials on all the remaining channels simultaneously. These circles go 25,
50% solid yellow displaying status.
9. When all the links go 100% green, the connection is established and the monitor displays the
far end with a temporary picture of your local end.
You have the option here of setting the ViewStation for full 384 kb/s speed. The connection will
drop if it can’t reach this speed and it cannot negotiate a speed with the receiving unit.
Walkthrough 2: Incoming Calls
This walkthrough will describe the end-to-end establishment of a point-to-point videoconference
with 2 Polycom ViewStation 512s.
1. The far end will call the first network DN you have allocated to the ViewStation. For example
394-2439.
2. The PRI line will pass 394-2439
3. The Norstar will see 2439 realize it is assigned to target line 146 and hand the call to the set
with target line 146 assigned (2439). 2439 is the DN assigned to loop 401. The device on
loop 401 will receive the call.
4. Your ViewStation will display a Yellow circle quickly changing to a 50% yellow and 5 more
yellow circles as it agrees to speed and transmits it’s other network DNs (394-2439 to 3943054).
5. The far end will dial the remaining numbers it has received. Each will go through the same
process above for the different network DNs, target numbers and Norstar DNs.
6. As both ends establish the different layers associated with ISDN, each channel represented
by a circle will turn green by degree; usually 25% yellow for number dialed, 50% yellow for
acknowledge received, 25% green for layer 1 established, 50% for layer 2 and 100% for
connection established.
Differences in other videoconferencing units will include the numbers of DNs required (either one
or two per ISDN loop), diagnostic displays of status per channel or per call and more.
Other Video Conferencing Products
While we only tested the above process with Polycom ViewStation 512k systems that fall within
the Single Site class, the following manufactures where contacted for information:
Nortel Networks -Symposium Multimedia
Polycom -ViewStation 512k
PictureTel - Live 200 384
The PictureTel and Symposium units are also the subjects of Solution TIPs and sell in the 128
kb/s single user size. Information on where to find this TIP is found below.
We recommend you fully investigate your alternatives and chose the system(s) that meets your
needs. Hopefully, this Solution TIP will help step you through your decision process.
We provide these links as the starting point of your investigation only.
Solution Tips on the Internet
Additional Solution Tips are available on the Norstar ITAS web site under the Solutions Heading.
. Also watch this site for other Engineering Deployment Rules as they
become available.
The specific tips on installing U loop ISDN devices mentioned can be found here.
Connecting ISDN Devices to your Norstar 18/11/998
Norstar and PictureTel Video 200 Solution 2/10/1998
Norstar Multimedia Conferencing Solution 2/10/1998
Norstar CTA 500dm and Motorola BitSurfer Pro Telecommuting Solution 2/10/1998
What to consider when buying Videoconferencing TBD
For more information contact your Norstar sales representative.
Troubleshooting
Many variables may contribute to any problems that you may be experiencing. As such it is
important to perform a verification process to accurately isolate faults. The following provides a
brief guide to troubleshooting but you must use basic elimination to isolate the problem before
calling anyone. After doing this, repeat the process.
1-Backup your system programming before starting.
2-Do you have your PRI or BRI link programmed with the correct settings provided by the CO?
3-Confirm settings with your CO. They may not have given all the different settings to you.
4-Are the indicator lights on the PRI/BRI cards green and steady?
5-Does the video unit see the BRI trunks?
6-Have you assigned line pool access?
7-Have you assigned appear and ring?
8-Are you dialing the correct number(s)?
9-Try using more or less numbers of Network DNs
10-Do the SPIDs in the video unit relate to the loop DNs in the Norstar?
11-Are the correct Network DNs (and number of Network DNs) programmed into the video unit?
12-Can you connect to the far end at slower speeds (try 64, then 2x64 then 128).
Schematic
The Schematic below is only intended to show the potential a video system may grow into. There is no
requirement in any of the systems mentioned here for a network connection, nor do you need a multimedia
server or an SNMP workstation. You may decide that they add value to your system as your needs grow or
you have the scope to reduce costs by deploying these systems.
PSTN
PRI or
3 BRI
3 U or S BRI
Mux
Polycom 512
Videoconference Unit
Note: this diagram is designed only to show a high level overview of the connections for this solution and does not accurately reflect
the exact product sizes or physical connections. For physical connection information please refer to the installation guides for the
various products depicted in this schematic. The picture of a Polycom ViewStation does not endorse that product.
Glossary
AT&T 5ESS American Telephone and Telegraph Central Office Switch model 5ESS
CO Central Office. The
DMS100 Digital Multiplex Switch model 100 Central Office switch from Nortel Networks
DN Directory Number provided by LEC or in numbering plan of Norstar
G.711 ITU standard that defines a voice sampling rate of 8 bits in 8 kHz = 64 kb/s
G.721 ITU standard for 64 kb/s voice transmission over digital with clear channel
G.722 ITU standard for 56 kb/s voice over digital with in-band signaling (non clear)
G.729 ITU standard that defines compression of voice to 8 kb/s instead of 64 kb/s
H.323 ITU recommended standard for multimedia over IP networks with no QoS
IP Internet Protocol used in data networks such as ethernet and the internet
ISDN Integrated Services Digital Network
ITU International Telecommunications Union standards body
LEC Local Exchange Carrier that supplies you with your local phone service
Mux Multiplexor is a device that combines several cables/signals/channels into one
NI1 Network Interface 1 point in the ISDN definitions
NT1 Network Terminator 1 a part of the ISDN definitions and required hardware
PSTN Public Switched Telephone Network that carries most voice calls
QoS Quality of Service guarantees for multimedia delivery over IP networks
SPID Service Profile ID used to identify each ISDN device as a DN identifies a set
SNMP Simple Network Management Protocol adopted as the data industry standard
Contact Us
This Tip is one in a series of Solutions Tips. Please take time to contact us and let us know if this
information is relevant and clearly presented. All Tips are living documents that can be quickly
edited and updated
· Are there any solutions you would like us to document?
· Any suggestions for the format and content of this particular Solutions Tip?
Your comments are appreciated.
Please forward comments or concerns to Dennis Yakimenko dyakimen@nortelnetworks.com
(phone: 403.291.7500) or Hagen Hohn hhohn@nortelnetworks.com (phone: 613.763.9595)
For more information on any of the Norstar solutions for voice, data, and messaging,
please contact your local Norstar distributor or District Sales Manager. Also visit Nortel at
*Nortel, the Nortel globemark, Nortel Networks, and Norstar are trademarks of Northern Telecom. PictureTel and Live200
are trademarks of and owned by PictureTel Incorporated. Polycom and ViewStation are trademarks of and owned by
Polycom. All other trademarks are property of their respective owners. Northern Telecom reserves the right, without
notice, to change its products as progress in engineering or manufacturing methods or other circumstances may warrant.
© 1998, Northern Telecom. ALL RIGHTS RESERVED.
Good-Luck
Configuration Rules:
Norstar and High Speed Video
Norstar and
Polycom ViewStation 512
This configuration guide and walkthrough is
the second part of the High speed
Videoconferencing solution found on the
ITAS Customer Solutions web site. The first
part details how to chose a
videoconferencing unit. This second part
along with others that will be published,
detail how to connect various products from
differing manufacturers.
Polycom has recently renamed their product
line. The product tested here is now called
simply ViewStation and is capable of speeds
up to 512k. The ViewStation MP is capable
of hosting multi-site videoconferences but
basically connects the same. The
ViewStation V.35 can connect at up to 786
kb/s and adds direct to LAN connections as
well as a T1/PRI jack.
Installation & Configuration
The following steps will show you how to
configure your Norstar system with a
Polycom videoconference unit. The process
was tested with a Polycom ViewStation 512
running at 384 kb/s (only 3 of the 4 available
BRI loops active). This unit has an S loop
ISDN interface. To keep costs lower, we
used an S loop card instead of 4 NT1s. We
also tested with MICS 4.0 PRI and BRI
ISDN. If you choose to use U loops on the
station-side, please refer to the Solutions
and TIPS on the ITAS web page. The URL
and TIPS list is included on page 10 just
before the Troubleshooting section at the
end of this Tip.
BRIBRI
PRI
PSTN
Station-sideTrunk-side
Further references to S loops can be replaced with
station or set-side U loops and NT1s (if the product
requires an S interface and you use U loops).
STEP 1: Deployment Considerations
Hardware Requirements
• Perform a traffic assessment of existing
voice and data traffic to determine if the
number of videoconferences you want to
hold (time, duration and bandwidth) will
impact existing traffic.
• Does your traffic assessment indicate
the need for more ISDN channels (via
PRI trunks or additional U loop BRI
trunks and cards). Additional BRI trunk
cards may lead to additional trunk
modules and a fibre expansion card.
See the chart below.
Existing
Equipment
384 Kb/s video
system
512 Kb/s video
system
CICS
(CICS 2.0+)
3 BRI trunks for
video (U loop)
4 BRI trunks for
video (U loop)
3 station loops per
unit (U or S Loop)
4 station loops per
unit (U or S loop)
6 CO numbers 8 CO numbers
6 DNs 8 DNs
Clock control Card Clock Control Card
MICS PRI 3 or 6 CO numbers 4 or 8 CO numbers
(MICS 4.x) 3 loops per unit
(U or S loop)
4 loops per unit
(U or S loop)
6 DNs 8 DNs
Optional Fibre expansion Fibre expansion
MICS BRI
(MICS 2.0+)
Numbers, DNs and
loops as MICS PRI
Numbers, DNs and
loops as MICS PRI
Trunks as per
CICS
Trunks as per
CICS
Clock control card Clock control card
Optional Fibre expansion Fibre expansion
• Do you have Sufficient BRI loops and
trunk cards to connect the video unit(s)?
• Central Office assigned phone numbers
(network DNs). BRI One per channel or
one per trunk
• Which trunks will the calls be routed out
over? Do you need routing table
entries? Do you use different Long
Distance Carriers?
• Do you have 6 target lines available?
• Can you map your internal Norstar DN
numbering plan to accommodate
matching the last four of the network
DNs?
TIP You can use the Video network DNs for voice calls
and regular appearances on sets as Norstar sets will
not present a video call and the Polycom will not
answer a voice call.
The Diagram and configuration table below will clarify the following details. If using PRI, there will
not be any SPIDs from your SP (Service Provider) or CO (Central Office).
PRI or
3 BRI
3 U or S BRI
Mux
Polycom 512
Videoconference Unit
CO Trunk-side Loop Norstar Configuration Video unit
Ntwk DN BRI SPID
394-2439 00139424390100 401 00139424390100 394-2439 220 439 2439
394-2651 00139426510100 00139426510100 394-2651 221 651 2651
394-2924 00139429240100 402 00139429240100 394-2924 222 924 2924
394-2992 00139429920100 00139429920100 394-2992 223 992 2992
394-3012 00139430120100 403 00139430120100 394-3012 224 012 3012
394-3054 00139430540100 00139430540100 394-3054 225 054 3054
Trunk-side U Loop
U Lp Lp SPID Ntwk DN
Target Line
Tgt Line Rcvd # N* DN
Station-side S Loop
S Loop DNs on Lp Loop DN
Unit SPID Unit DN
201 2439 2439
243900 394-2439
2651
265100 394-2651
202 2924 2924
292400 394-2924
2992
299200 394-2992
203 3012 3012
301200 394-3012
3054
305400 394-3054
The following definitions will be used:
PSTN (or CO) Details:
Network DN The 3 or 6 phone numbers assigned by the CO that you advertise as being
answered by the videoconferencing unit. The CO may give you 1 DN per BRI
loop. You do not require 6 DNs. If this applies to you, enter the DN in both
locations as if it were a different number. If you have PRI, you will need 6
DNs. The network DNs do not need to be contiguous.
SPID (if BRI) Program the SPID directly into the matching U loop
N* DN The Norstar DN that is assigned to a station-side U or S Loop and has an
appearance of a target line with the appropriate received digits (if PRI or
BRI), or a direct Appear&Ring of that BRI line.
Loop DN (s) 2 Norstar DNs programmed per loop. One will be assigned as Loop DN.
Unit SPID Matches the Norstar DN assigned to that loop plus 00 on the end.
Unit DN Matches the Network DN above and is programmed into the videoconference
unit.
S Loop Anywhere an ISDN S loop is mentioned an ISDN U loop terminated at an
NT1 can be substituted. Configurations with NT1s have been tested.
System Considerations
• As you can see from the table above, Network DNs match the CO SPIDs that match the
trunk-side U loop programming (ISDN rules) AND must also match Norstar DNs assigned to
the station-side loops. These then match the Unit SPIDs (ISDN rules). Finally, the unit must
have the Network DNs programmed into it as its DNs.
• Depending on the configuration you have (N* DNs already deployed and Network DNs for the
video unit), you may be forced to go to 3, 4 or even 5 digit numbering plan on the Norstar.
The Polycom system rules have been tested with 3, 5 and 7 DN numbering plans.
Example The lowest Network DN is 394-2439. In a 3 digit system, 439 cannot be assigned as a DN. The
system needs to be boosted to a 4-digit pattern. But then you may find that 24xx cannot be assigned. A
workaround here is to accept 2667 (earliest ISDN DN available) and then “change DN” from 2667 to 2439.
• If you cannot assign DNs that match the last series of Network DNs (2439 from 394-2439),
you must then rework your DN deployment and “change DNs”. In MICS or CICS 2.x to 4.0,
Norstar DNs must match Network DNs.
TIP MICS/CICS 4.1 will allow the addition of separate Network DNs for ISDN sets. So a video unit added to
Norstar will essentially have a separate internal and external DN. Technically, instead of presenting a call to the
Norstar DN, the call is presented to the Network DN. The video unit programmed with this number will
recognize that the call is for it.
• The SPIDs of the station-side U loops must match the Network DN and thus the Norstar DN
with the following pattern: If the network DN is 394-2439, the Norstar DN is 2439 and the
SPID is 243900. This is not a limitation of this configuration, but is a requirement of ISDN.
• If the incoming video call is via PRI, target lines are required to present the call to the video
unit. If you are using BRI trunks as shown above, you will need to auto-answer the lines
associated with the BRI trunks. The received digits can be as small as 3 in length. The CO on
that trunk type must send digits. BRI “lines” can also be programmed directly onto the set.
Example A call presented on 394-2439 is handed to target line 201 programmed with received digits of 2439.
Line 201 is assigned to Appear&Ring on DN 2439 (video unit). 2439 is also the DN assigned to LT U loop 201
on KSU card 1 (right most card on KSU).
CICS versus MICS
CICS
A CICS system is limited to only 8 loops. To support 384 kb/s video, you would need to use 6
loops (3 loops to your video unit and 3 loops to your ISDN LEC) when holding a conference. This
would restrict the system to 4 simultaneous voice connections (2 loops or 4 lines). A 512kb/s
system would use all the trunks. The next diagram illustrates the trunk requirements of a 384 kb/s
during a videoconference:
PSTN
3 Video
3 Video
2 Voice
NT1s Mux
The solid lines are trunks from the 1st BRI card. Three are used for 384 video and one is available
for other traffic shown as voice at the bottom. The dashed line trunks are from the 2nd card. Three
trunks are used for the unit and one is available for other traffic. Here, we’ve shown the spare
trunk from 2nd card being used as a voice trunk to the network. If you want to do this, the 2nd card
must be a U loop card or the U loop is terminated in an external NT1.
TIP You may want to limit the video unit to 128 kb/s during peak voice traffic periods.
MICS
You have several options with a MICS system. Not limited to PRI on core, you can deploy BRI
off-core in expansion modules, so unless you have a fully populated system, you may or may not
need additional trunk modules or fibre expansion cards.
TIP If you are adding ISDN cards (PRI or BRI) to an existing system, you will need a clock control card.
TIP Loops allocated to the video system do not need to be on the same card. You can use up spare loops on
existing cards before purchasing more ISDN trunk cards.
You will need to have numbers dialed specifically for the video units. These numbers are then
assigned to Target Lines. This is most powerful with PRI in that when not using the video unit, all
channels are available to voice or data traffic. However, the video units will not answer voice calls
and Norstar sets will not answer video calls.
BRI This solution will deal with PRI as the trunking connection to your LEC. BRI specific details will be
differentiated by TIP style bullets such below:
BRI BRI Trunks on the other hand give you the flexibility of using dedicated lines depending on the amount of
use you will require.
Step 2: Local Exchange Side
CO Assigned Data
PRI
If you have a PRI trunk, select 6 numbers from the pool of numbers assigned. These numbers will
be associated with the video conference unit e.g. 394-2439 to 304-3054. The numbers don’t have
to be contiguous. These numbers will be assigned to target lines.
You will also need to confirm whether the CO is allocating channels in an ascending or
descending method. Ascending means the first call coming in will be assigned to channel 1 and
moves up. Descending starts at channel 23 and moves down. This is to ensure the PRI link
allocates channels with minimum potential for collisions with incoming calls. This also applies to
other data and voice calls, not just video.
Which protocol is the PRI trunk? Norstar supports NI2, DMS100 and AT&T 5ESS.
BRI If you have BRI trunks you will need target line numbers and received digits. Refer to the additional TIPS
listed for specific BRI programming such as SPIDs and network DNs. Units require one BRI loop per 128 kb/s of
speed.
NOTE BRI trunks must not be programmed with EKTS.
Step 3: Local Exchange Side
PRI Configuration
MICS 4.x is required for PRI trunking.
Before changing any system setting, backup your system. This will allow you to repeat the
process if it fails after the first attempt.
Disable the PRI card in: Administration/Maintenance/Module Status (Feature **Config). PRI cards
must go on-core (module 2) and require a clock control card. Set card as PRI in
Admin/Hardware/Module 2/Card 2/PRI
PRI in slot 1 will have lines 001-023 while a PRI card in slot 2 will have lines 024-046.
In Administration/Hardware/Module 2/Card 1
Select the appropriate protocol: NI2, DMS100, 5ESS.
Select the B Channel sequence: Ascending, or Descending
TIP You can reduce collisions (glare) with channels grabbed by incoming calls by choosing the opposite method than the
CO e.g. if the CO is ascending, choose descending.
Set all other values to those assigned by the CO or leave them default.
Enable the PRI card or the specific lines if partial PRI in: Administration/Maintenance/Module
Status.
You may require Softkeys to activate additional PRI lines. Contact your Norstar Rep.
Enable required lines in: Administration/Maintenance/Provisioning
NOTE PRI and BRI lines can also be referred to as channels.
BRI Identify which lines are assigned to the BRI loops you will receive incoming calls for the video terminal. There are 2
lines per loop. BRI cards can be located in modules other than module 2. Each loop must be provisioned and also has 2
lines that must be provisioned as above for PRI.
Step 4: Video Set Side
Program Trunk Module and S Loops
If you have the expansion space and are considering a device that is equipped with
an S loop interface we recommend you purchase an S loop BRI ISDN card. One S loop card may
cost less than 3 or 4 NT1s. NT1s are required to convert U loops to S.
Our example has an S loop card off-core in trunk module 4. Disable the ISDN BRI S loop card in:
Admin/Maintenance/Module Status.
For each loop (401 to 403 are the first three of card 1 in module 4), set the loop type to S and
leave the sampling to the default fixed. Admin/Lines/Trunk Data/Trunk Type
Assign DNs to the loop and each B1 and B2 channels of that loop. For example 401 B1: 2439
and B2: 2651, 402 B1: 2924 etc (one DN per line). Admin/Hardware/Module 4/Card 1/Assign DN/
and Admin/Hardware/Module 4/Card 1/Assign DN/Show loop 401/Assign
TIP If no DNs are shown as available, you will need to convert portable DNs to ISDN DNs. This can be done in
Admin/System Programming/Change DN Type
NOTE Some video units will require one DN per loop while others will require one DN per channel (2 per loop).
Repeat for each loop that will be connected to the video unit.
Provision each loop under Maintenance/Provisioning/Module.
Change DNs to match the last series of the Network DNs chosen. Some units may not require the
Norstar DN to be changed to match. SysProgramming/Change DNs/Old DN – New DN. 2669
becomes 2439 in this example or for a 3 digit numbering plan 669 would become 439. We will
use the 4-digit example moving forward.
TIP If you are using U loops for the unit, you will also need to enable each channel (line) in each loop.
NOTE MICS 4.1 does not require DN matching. There is an option available to ISDN sets where the network DN is
mapped to the OLI number programmed for that set. Under set options, program the network DN as the OLI number, then
turn on the mapping option.
Step 5: Outgoing Calls
Program Line Pools and Routing
Assign Line Pool access code. If using PRI, select Pool PRI-A (card in slot 1) or Pool PRI-B (card
in slot 2) for outgoing calls.
TIP If you cannot assign the number you want to use, it may be in use elsewhere.
You may want to utilize Norstar’s powerful routing table feature to route the video call setup out
specific trunk types depending on time of day, long distance carrier rates etc.
TIP you may be able to simplify the number(s) dialed by the video unit if you use the dial out feature of the routing
service.
TIP If you need to call to a PBX or key system in a specific country, you may want to examine public DN lengths to see if
the Norstar defaults are long enough to support the number of digits you may have to dial. These defaults are found in:
Services/Public DN lengths/011 etc
BRI Before you can assign line pool access to the video unit, you need to assign BRI lines to those line pools.
Step 6: Incoming Calls
Target Lines and Received Digits
For the following steps, a spreadsheet table is included at the end of this document to show the
relationship of all the DNs and lines programmed into the Network, Norstar, ISDN loops and
Video Unit. Please refer to this as we discuss the programming steps.
Select and program each target line (you will need one for each 64 kb/s you want to use) as
public and the received digits that are unique to each channel coming in. For example, the
numbers chosen from the CO pool noted earlier were 394-2439 to 394-3054 would indicate
received numbers of 2439 to 3054 (or the minimum number length to identify a unique number of
all incoming received digits – three shown here for example only).
TIP Your video unit may be able to function with 1 Network DN, or with 3 (one Network DN for each BRI loop).
The first line will have 2439 as its received digits while the last will have 3054.
Admin/Lines/line 145/Line Type/Public
Admin/Lines/line 145/Rec’d #/2439
Target Lines can be chosen from the line ranges:
MICS 4.x 145-272
CICS 2.0+ 49-75
For example: The far end originating the call will dial 394-2439. This will come in any PRI
channel. The system will see 2439 and note that target line 145 has been programmed for
received digits 2439. The call will be passed to any device with an appearance of that target line.
BRI BRI trunks from the LEC each have their own numbers associated with them. You can assign this line without having
to use a target line. This is referred to as a dedicated line.
BRI BRI trunks used in conjunction with LEC hunt group type features can also operate the same as the PRI example.
Step 7: Video Set
Program Norstar DN Line Access
For each DN, assign line access (appear and ring) of the appropriate target line and line pool
access for outgoing calls(PRI-A yes).
Admin/Set/Show Set: 2439/Line Assignment/Show Line 145/Appear & Ring
Admin/Set/Show Set: 2439/Line Assignment/Line Pool Access/PRI-A Yes
Repeat this for each DN (6 for 384 kb/s) chosen in Step 4.
NOTE Some systems may require 6 DNs (one per line or two per loop) while others may only require 3 (one per loop). For those
systems that only require 3 DNs, you will still need to use 6 DNs. The unit will then only require 3 DNs programmed in it.
Step 8: Video Set
Program Video Unit Line Access
This is where the huge variation and potential problems may lie: basic video conferencing should
be able to be established with the following steps:
Program the network DNs you have chosen for the video units (example 394-2439and loop 401,
977-2924 for loop 402 etc) for each loop or channel into the video unit. You may want to try at this
time to program the same Network DN into each B Channel of a BRI loop. These numbers are so
that when the unit advises a remote end who it is, multiple links can be established (refer to the
Walkthroughs below).
Setup/Configuration/Mux/Numbers
Program the SPIDs to match your Norstar programming: DNs padded on the following rules:
2439 converts to 243900. The SPID needs to be formatted from Norstar DN on that loop. A
minimum padding of 2 zeros on the end is required but some units may require additional zeros
on the front to reach a specific SPID length. Do not set PBX option on.
Setup/Configuration/Mux/ISDN
Select the ISDN type for each loop: NI-1
NOTE Norstar only supports NI-1 BRI ISDN on S loops.
Program the destination phone numbers of any videoconference units to be dialed. Depending on
the system to be dialed you may need anywhere from 3 to 8 numbers.
The same process applies to systems from 128 kb/s to 786 kb/s.
Some systems may have address books that allow you to select the destination ad then will
automatically dial all the numbers preprogrammed. Others will require you to enter all the DNs.
Yet others will only require one DN to be dialed initially and the units will then negotiate the
remainder.
Walkthrough 1: Outgoing Calls
In order to help clarify what each of the above programming will accomplish, this section will walk
you through an outgoing call. This walkthrough will describe the end-to-end establishment of a
point-to-point videoconference with 2 Polycom ViewStation 512s.
1. Power on the video unit and monitor
2. As the unit comes on line, it displays the status of each BRI link. The Norstar BRI card also
displays the status of each link. Solid green lights indicate that the link is fully established.
3. Either dial in the number of the remote video unit or select it from the included phonebook.
Only one number is required. We will use 394-2439 as the first number of the target unit. You
can also select the videoconference speed at this point. A limitation in the Polycom is that
calls that are up to 128kb/s can be dialed independently i.e. 2 numbers dialed
simultaneously. This actually circumvents the problem of requiring multiple DNs: 1 DN can be
used twice. Above 128 kb/s, the call is bonded and the unit dials one number then waits for
the receiving unit to transmit the other Network DNs assigned to it. The sending unit then
dials these other 5 numbers simultaneously. This is where 6 numbers are required as the unit
can get confused with multiple calls dialed to the same Network DN. Other products may
behave differently. The ITAS Customer Solutions Group will test and publish the engineering
rules for other products as we can.
4. The unit will display 6 yellow circles on the screen. Each represents a B channel.
5. The number is dialed (with a 9 preceding to select pool PRI-A). The device on loop 401 is
associated with the Norstar DN on loop 401 (2439). 2439 has access to pool PRI-A. If no
Line Pool code was used, the Norstar would examine the number dialed to see if Routing
tables and Destination Codes applied. If they did, the Norstar would route the call over the
specified trunk (s)
6. The far end ViewStation acknowledges the inbound call and the request for a conference at
384 kb/s. It transmits the other 5 network DNs it is programmed with (394-2651 to 394-3054
in this example). The ViewStation uses one DN per loop as opposed to one DN per channel.
7. Our near end displays a 50% green circle on the first B Channel to indicate that a connection
is under negotiation.
8. Our near end then dials on all the remaining channels simultaneously. These circles go 25,
50% solid yellow displaying status.
9. When all the links go 100% green, the connection is established and the monitor displays the
far end with a temporary picture of your local end.
You have the option here of setting the ViewStation for full 384 kb/s speed. The connection will
drop if it can’t reach this speed and it cannot negotiate a speed with the receiving unit.
Walkthrough 2: Incoming Calls
This walkthrough will describe the end-to-end establishment of a point-to-point videoconference
with 2 Polycom ViewStation 512s.
1. The far end will call the first network DN you have allocated to the ViewStation. For example
394-2439.
2. The PRI line will pass 394-2439
3. The Norstar will see 2439 realize it is assigned to target line 146 and hand the call to the set
with target line 146 assigned (2439). 2439 is the DN assigned to loop 401. The device on
loop 401 will receive the call.
4. Your ViewStation will display a Yellow circle quickly changing to a 50% yellow and 5 more
yellow circles as it agrees to speed and transmits it’s other network DNs (394-2439 to 3943054).
5. The far end will dial the remaining numbers it has received. Each will go through the same
process above for the different network DNs, target numbers and Norstar DNs.
6. As both ends establish the different layers associated with ISDN, each channel represented
by a circle will turn green by degree; usually 25% yellow for number dialed, 50% yellow for
acknowledge received, 25% green for layer 1 established, 50% for layer 2 and 100% for
connection established.
Differences in other videoconferencing units will include the numbers of DNs required (either one
or two per ISDN loop), diagnostic displays of status per channel or per call and more.
Other Video Conferencing Products
While we only tested the above process with Polycom ViewStation 512k systems that fall within
the Single Site class, the following manufactures where contacted for information:
Nortel Networks -Symposium Multimedia
Polycom -ViewStation 512k
PictureTel - Live 200 384
The PictureTel and Symposium units are also the subjects of Solution TIPs and sell in the 128
kb/s single user size. Information on where to find this TIP is found below.
We recommend you fully investigate your alternatives and chose the system(s) that meets your
needs. Hopefully, this Solution TIP will help step you through your decision process.
We provide these links as the starting point of your investigation only.
Solution Tips on the Internet
Additional Solution Tips are available on the Norstar ITAS web site under the Solutions Heading.
. Also watch this site for other Engineering Deployment Rules as they
become available.
The specific tips on installing U loop ISDN devices mentioned can be found here.
Connecting ISDN Devices to your Norstar 18/11/998
Norstar and PictureTel Video 200 Solution 2/10/1998
Norstar Multimedia Conferencing Solution 2/10/1998
Norstar CTA 500dm and Motorola BitSurfer Pro Telecommuting Solution 2/10/1998
What to consider when buying Videoconferencing TBD
For more information contact your Norstar sales representative.
Troubleshooting
Many variables may contribute to any problems that you may be experiencing. As such it is
important to perform a verification process to accurately isolate faults. The following provides a
brief guide to troubleshooting but you must use basic elimination to isolate the problem before
calling anyone. After doing this, repeat the process.
1-Backup your system programming before starting.
2-Do you have your PRI or BRI link programmed with the correct settings provided by the CO?
3-Confirm settings with your CO. They may not have given all the different settings to you.
4-Are the indicator lights on the PRI/BRI cards green and steady?
5-Does the video unit see the BRI trunks?
6-Have you assigned line pool access?
7-Have you assigned appear and ring?
8-Are you dialing the correct number(s)?
9-Try using more or less numbers of Network DNs
10-Do the SPIDs in the video unit relate to the loop DNs in the Norstar?
11-Are the correct Network DNs (and number of Network DNs) programmed into the video unit?
12-Can you connect to the far end at slower speeds (try 64, then 2x64 then 128).
Schematic
The Schematic below is only intended to show the potential a video system may grow into. There is no
requirement in any of the systems mentioned here for a network connection, nor do you need a multimedia
server or an SNMP workstation. You may decide that they add value to your system as your needs grow or
you have the scope to reduce costs by deploying these systems.
PSTN
PRI or
3 BRI
3 U or S BRI
Mux
Polycom 512
Videoconference Unit
Note: this diagram is designed only to show a high level overview of the connections for this solution and does not accurately reflect
the exact product sizes or physical connections. For physical connection information please refer to the installation guides for the
various products depicted in this schematic. The picture of a Polycom ViewStation does not endorse that product.
Glossary
AT&T 5ESS American Telephone and Telegraph Central Office Switch model 5ESS
CO Central Office. The
DMS100 Digital Multiplex Switch model 100 Central Office switch from Nortel Networks
DN Directory Number provided by LEC or in numbering plan of Norstar
G.711 ITU standard that defines a voice sampling rate of 8 bits in 8 kHz = 64 kb/s
G.721 ITU standard for 64 kb/s voice transmission over digital with clear channel
G.722 ITU standard for 56 kb/s voice over digital with in-band signaling (non clear)
G.729 ITU standard that defines compression of voice to 8 kb/s instead of 64 kb/s
H.323 ITU recommended standard for multimedia over IP networks with no QoS
IP Internet Protocol used in data networks such as ethernet and the internet
ISDN Integrated Services Digital Network
ITU International Telecommunications Union standards body
LEC Local Exchange Carrier that supplies you with your local phone service
Mux Multiplexor is a device that combines several cables/signals/channels into one
NI1 Network Interface 1 point in the ISDN definitions
NT1 Network Terminator 1 a part of the ISDN definitions and required hardware
PSTN Public Switched Telephone Network that carries most voice calls
QoS Quality of Service guarantees for multimedia delivery over IP networks
SPID Service Profile ID used to identify each ISDN device as a DN identifies a set
SNMP Simple Network Management Protocol adopted as the data industry standard
Contact Us
This Tip is one in a series of Solutions Tips. Please take time to contact us and let us know if this
information is relevant and clearly presented. All Tips are living documents that can be quickly
edited and updated
· Are there any solutions you would like us to document?
· Any suggestions for the format and content of this particular Solutions Tip?
Your comments are appreciated.
Please forward comments or concerns to Dennis Yakimenko dyakimen@nortelnetworks.com
(phone: 403.291.7500) or Hagen Hohn hhohn@nortelnetworks.com (phone: 613.763.9595)
For more information on any of the Norstar solutions for voice, data, and messaging,
please contact your local Norstar distributor or District Sales Manager. Also visit Nortel at
*Nortel, the Nortel globemark, Nortel Networks, and Norstar are trademarks of Northern Telecom. PictureTel and Live200
are trademarks of and owned by PictureTel Incorporated. Polycom and ViewStation are trademarks of and owned by
Polycom. All other trademarks are property of their respective owners. Northern Telecom reserves the right, without
notice, to change its products as progress in engineering or manufacturing methods or other circumstances may warrant.
© 1998, Northern Telecom. ALL RIGHTS RESERVED.
- Thread starter
- #6
- Status
Similar threads
- Locked
- Question
