Running isdncta automatically
If you’re using ISDN, set the audio.nms.isdncta service property on each Telephony Session service instance to automatically start the D-channel on the T1(s) used by that instance. The values set on audio.nms.isdncta are the options shown in the following table:
|
-aaccessID |
Network Access Identifier |
|
|
-bnumber |
CG board number (Terminal Equipment side) |
|
|
-ooperator |
Network operator variant |
|
|
Northern Telecom DMS100 |
8 |
|
|
AT&T 5ESS10 |
23 |
|
|
AT&T 4ESS |
24 |
|
|
National ISDN 2 |
20 |
|
Specify the value as follows:
"-aaccessID -b|Bnumber -ooperator"
Quotes are required because the value contains spaces. For example, to start the D-channel on the first T1 of the first board using the NI2 protocol, set the value on audio.nms.isdncta service property to this string:
"-a0 -b0 -o20"
Stopping the Telephony Session service instance also stops the D-channels on the T1s used by that instance.
Starting the D-channel on multiple trunks
If the Telephony Session service needs to start D-channels on multiple trunks, you can differentiate the settings by appending a number or trunk name to the service property name string. The NMS audio provider looks only for the string “audio.nms.isdncta”. For example:
audio.nms.isdncta1= ...
audio.nms.isdncta2= ...
audio.nms.isdncta-myT1trunk= ...
If multiple Telephony Session service instances share a common T1 for outgoing lines, each instance must set the audio.nms.isdncta service property for both the T1 it uses for incoming calls and for the common T1. The D-channel on the common T1 is started once by the first Telephony Session service instance to initialize. Conversely, the D-channel is killed only when the last Telephony Session service instance terminates.
As an example, consider a host configured with three Telephony Session service instances to receive inbound lines on the first three T1s with the fourth T1 for outgoing lines. Normally, these lines would require starting four isdncta processes on the command line:
isdncta -a0 -b0 -o20 // for the first T1 inbound only
isdncta -a1 -b0 -o20 // for the second T1 inbound only
isdncta -a2 -b0 -o20 // for the third T1 inbound only
isdncta -a3 -b0 -o20 // for the fourth T1 outbound only
However, using the audio.nms.isdncta service property, you can automatically start the D-channel on each T1 through the Telephony Session service:
- On the Telephony Session service instance properties page, click the Advanced tab.
- For the first Telephony Session service instance, add these service properties:
audio.nms.isdncta1="-a0 -b0 -o20"
audio.nms.isdncta2="-a3 -b0 -o20"
This starts the D-channel on the first T1 and on the fourth T1, if it has not already been started.
- For the second Telephony Session service instance, add these service properties:
audio.nms.isdncta1="-a1 -b0 -o20"
audio.nms.isdncta2="-a3 -b0 -o20"
This starts the D-channel on the second T1 and on the fourth T1, if it has not already been started.
- For the third Telephony Session service instance, add these service properties:
audio.nms.isdncta1="-a2 -b0 -o20"
audio.nms.isdncta2="-a3 -b0 -o20"
This starts the D-channel on the third T1 and on the fourth T1, if it has not already been started.
Shutting down or aborting one of the Telephony Session service instances stops the D-channel on the T1 used for incoming calls by that Telephony Session service instance. However, the D-channel on the fourth T1 is not stopped if either one of the other Telephony Session service instances remains active. The last Telephony Session service instance to terminate stops the D-channel on the common T1.
Explicitly identified D-channel IDs
If you've provisioned your T1s to have explicitly identified D-channel IDs, then you'll need to set up an NFAS group on the NMS board. Skip this section if the T1s are provisioned with implicitly identified D-channel IDs. If you're unsure, please contact your provider to find out how the D-channel ID was provisioned.
- Open the board’s configuration file under NMS_path\cg\cfg. Right under this section:
NetworkInterface.T1E1[0..3].Type = T1
NetworkInterface.T1E1[0..3].Impedance = DSX1
NetworkInterface.T1E1[0..3].LineCode = B8ZS
NetworkInterface.T1E1[0..3].FrameType = ESF
NetworkInterface.T1E1[0..3].SignalingType = PRI
NetworkInterface.T1E1[0..3].D_Channel = ISDN
Add a new section using this template:
==============================================================
#
# NFAS configuration
#
#=============================================================
#
# NFAS group information is associated with the trunk where the
# primary D-channel is located. A unique number must be
# assigned to each NFAS group for reference:
#
# NetworkInterface.T1E1[x].ISDN.NFASGroup = group number#
# For each NFAS group member (including primary D-channel),
# specify the following configuration information:
#
# NetworkInterface.T1E1[x].ISDN.NFAS_Member[y].Board = board
# number
# NetworkInterface.T1E1[x].ISDN.NFAS_Member[y].Trunk = trunk
# number (from 0)
# NetworkInterface.T1E1[x].ISDN.NFAS_Member[y].NAI = assigned
# NAI number (unique within group)
# Where:
# x = trunk number for primary D-channel# y = NFAS member number (starting with 0 without any gaps in numbering)
For example, say you had a 32 DSP CG6060 board with four trunks, a board number of 0, and an explicitly identified D-channel ID of 0, the NFAS configuration would look like this:
#
# Assigning group number (to D-channel trunk)
#
NetworkInterface.T1E1[0].ISDN.NFASGroup = 0
#
# Configuring group members
#
NetworkInterface.T1E1[0].ISDN.NFAS_Member[0].Board = 0
NetworkInterface.T1E1[0].ISDN.NFAS_Member[0].Trunk = 0
NetworkInterface.T1E1[0].ISDN.NFAS_Member[0].NAI = 0
#
# Assigning group number (to D-channel trunk)
#
NetworkInterface.T1E1[1].ISDN.NFASGroup = 1
#
# Configuring group members
#
NetworkInterface.T1E1[1].ISDN.NFAS_Member[0].Board = 0
NetworkInterface.T1E1[1].ISDN.NFAS_Member[0].Trunk = 1
NetworkInterface.T1E1[1].ISDN.NFAS_Member[0].NAI = 0
#
# Assigning group number (to D-channel trunk)
#
NetworkInterface.T1E1[2].ISDN.NFASGroup = 2
#
# Configuring group members
#
NetworkInterface.T1E1[2].ISDN.NFAS_Member[0].Board = 0
NetworkInterface.T1E1[2].ISDN.NFAS_Member[0].Trunk = 2
NetworkInterface.T1E1[2].ISDN.NFAS_Member[0].NAI = 0
#
# Assigning group number (to D-channel trunk)
#
NetworkInterface.T1E1[3].ISDN.NFASGroup = 3
#
# Configuring group members
#
NetworkInterface.T1E1[3].ISDN.NFAS_Member[0].Board = 0
NetworkInterface.T1E1[3].ISDN.NFAS_Member[0].Trunk = 3
NetworkInterface.T1E1[3].ISDN.NFAS_Member[0].NAI = 0
- Run oamsys to update your board with these changes.
- Once the board has successfully started after running oamsys, you need to modify the audio.nms.isdncta service property.
For example, say the original values were:
|
Service property |
|---|
|
audio.nms.idsncta= "-a0 -b0 -o24" |
|
audio.nms.idsncta= "-a1 -b0 -o24" |
|
audio.nms.idsncta= "-a2 -b0 -o24" |
|
audio.nms.idsncta= "-a3 -b0 -o24" |
After configuring the NFAS groups, you would specify:
|
Service property |
|---|
|
audio.nms.idsncta= "-g0 -a0 -b0 -o24" |
|
audio.nms.idsncta= "-g1 -a0 -b0 -o24" |
|
audio.nms.idsncta= "-g2 -a0 -b0 -o24" |
|
audio.nms.idsncta= "-g3 -a0 -b0 -o24" |
Where:
- -g refers to the group number assigned to NetworkInterface.T1E1[x].ISDN.NFASGroup
- -a refers to the Network Access Identifier
- -b refers to the CG board number
- -o refers to the Network operator variant
Note that the values are enclosed in quotes. These are required when values contain spaces.