ADTEC Conference Server Integration

ADTEC Conference Server Integration1.00

ADTEC Conference Server Integration

Document Version

Overview

ADTEC Communications Centre is a SIP based conferencing server that offers multi-party audio conferencingfor a number of virtual meeting rooms. The testing detailed in this document is based on the connection of the ADTEC Conferencing server to the SV8500 platform via an MG-SIP gateway.

Scope

The scope of this testing has been to ensure that basic call scenarios from an SV8500/IPX Peer to PeerFusion environment that includes satellite Peer to Peer CCIS SV8300/IPS sites. In order to cater for all DTMF scenarios and the ability to call into multiple conference numbers simultaneously, the MG-SIP has been chosen for the integration.

Note: The MG-SIP can offer a maximum of 96 simultaneous calls into the ADTEC server.

Software

The following software was used as part of the testing:

ADTEC Communications Server

Adtec Communications Centre 3.2.1962

SV8500

+------+------+------+------+

| Type | Version | Issue | Date |

+------+------+------+------+

| MAIN | S03 | 02.19 | 2011/03/04 |

| ACDP | S03 | 02.16 | 2011/02/07 |

| MPH | S03 | 02.19 | 2011/02/28 |

| PHD | S03 | 02.19 | 2011/02/28 |

| PHI | S03 | 02.19 | 2011/02/28 |

| B2BUA_MAIN | S03 | 02.19 | 2011/02/28 |

| SP_BOOT | S03 | 02.19 | 2011/02/28 |

| SIPSV_PHE | S03 | 02.19 | 2011/02/28 |

| SIPSV_SIP | S03 | 02.19 | 2011/02/28 |

| LIBCMN | S03 | 02.19 | 2011/02/28 |

| LIBFSMTL | S03 | 02.19 | 2011/02/28 |

| LIBOSIP | S03 | 02.19 | 2011/02/28 |

| SV_GATE | S03 | 01.00 | 2010/04/26 |

| SV_TSKCTL | S03 | 01.00 | 2010/04/26 |

| SV_EMA | S03 | 01.00 | 2010/04/26 |

| SV_IOC | S03 | 01.00 | 2010/04/26 |

| PBXWATCHD | S03 | 01.00 | 2010/04/26 |

| SVSYSSUB | S03 | 02.16 | 2010/04/26 |

| SYS_NALL | S03 | 01.00 | 2010/08/06 |

| BASE_SYS | S02 | 02.02 | 2010/05/28 |

+------+------+------+------+

SV8300

SC-4934 E1-0003.00 2010/04/21

IPS2000

SC-3713 P1-0005.08 2011/04/25

Testing Environment

The environment used for this testing included SV8500 Direct, SV8500 FCCS, SV8300 CCIS, IPS2000 CCIS. The direct interface between the NEC systems and the ADTEC Server was done through an MG-SIP. Below is a diagram on the environment:

Test Results

The ADTEC Communications Server had the following requirements:

• Registration must be turned off on the ADTEC server. If the ADTEC tries to register to the MG-SIP it will receive a Method Not Allowed response.
• OPTIONS messages from the ADTEC box to the MG-SIP are used as keep alive messages. The MG-SIP will reply to these messages with Method Not Allowed responses. This response is enough for the ADTEC server to use as keep alive.
• The preferred method for DTMF transfer between the MG-SIP and the ADTEC server is RFC2833. However, PCM/G.711 was also tested.
• Internal connections from IP-PADs and NEC terminals to the MG-SIP will send DMTF as H.245 messages in most scenarios. New IPDA cards by default will send H.245 for DTMF (SW 11-7 can be used to change this, however, H.245 is highly recommended). See the test matrix below for more details of call scenarios.
• Pressing hold on a phone that has dialled into a conference will result in hold tone being sent to all the remaining parties in the conference.
• DTMF that is dialled into the conference will be heard by all parties in the conference.

Basic call and DTMF tested scenarios:

Outbound calls from ADTEC Server:

Note: for outbound calling the ADTEC system required number length information for allowed extensions/outside numbers to be set in its configuration.

Note: Station side Standard SIP connections (ASPTL/N) between the ADTEC Server and the SV8500 were originally tested. However, there were some scenarios where DTMF couldn’t be sent from DT Series phones to the ADTEC server via P-to-P CCIS. In addition to this, there was some additional development that was required for DTMF negotiation, and station side digest authentication. As a result MG-SIP was chosen as a more suitable integration.

System Configuration

SV8500 – MG-SIP Config

Note: the MG-SIP96 can be returned to default settings using the “set default” command

SV8500/IPX/SV7000 Programming

Note: Be sure to assign the data in the following order.

STEP 1: Enable ISDN in the System

ASYD – System Data 1, Index 186, Bit6 = 1 (ISDN)

Index 187 = 00

Index 220, Bit6 = 0 (ISDN is enabled)

STEP 2: Specify the Music-on-Hold source

ASYD – System Data 1, Index64, Bit7 = 1 (holding tone sending)

ASYDL – System Data 1, Index 810 Bit 2 = 0/1 [Internal Holding Tone (IP terminals)/External Holding Tone (EMA and PLO)]

Note: If External music (2) is selected, refer to M-7 Music On Hold.

STEP 3: Enable the Internal PHI in the System

ASYDL – System Data 1, Index 880 Bit 1 = 1 (Internal PHI is enabled)

STEP 4: Assign ToS settings for Protocol Handler Signalling Packets (Network Address 0.0.0.0)

ALOCL –

Network Address: Specify the Network Address (assign 0.0.0.0).

Mask Bit: Specify the Mask Bit (assign 32 when LOC-ID=0).

LOC-ID = 0

Setting of Type of Service (Signaling Packet): Specify the Quality of Service(IP Precedence/Diffserv).

When IP Precedence is selected:

Specify its priority [0-7] and the type (LOW DELAY/THROUGHPUT/RELIABILITY/MIN COST).

When Diffserv is selected:

Specify the DiffServ Code Point [0-63].

Note: It is essential to assign LOC-ID=0, however, other network LOC-ID’s are assigned according to the configuration requirements.

Note: When a change has been made, it is necessary to initialize the MGC (PHI) using the ADPM command.

Note: When the data change is to be applied to already-operating equipment (such as PH, IPPAD, and Dterm IP) it is necessary to perform the following:

- Reset the appropriate PH or IPPAD.

- Re-register the Dterm IP terminals.

ALOCL Example:

STEP 5: Initialize the Internal PHI

ADPM – PH TYPE = Internal PHI (BRI)

Menu = Initialize

ADPM Example:

STEP 6: Configure the Internal PHI

ALIDL – LENS: Specify the Line Equipment Number (even number)

TYPE = Internal PHI

REGMAX: Specify the registration capacity (1-6144).

Note: When the total number of channels using the PHI exceeds 256, increase the value of REGMAX.

ALIDL Example:

STEP 7: Assign the route to be used for the MG-SIP96 Virtual Speech Channels.

Note: It is not necessary to assign a signalling route.

ARTD – Assign the route data for the Virtual Speech Channel route, as follows:

CDN2 (ONSG)= 2 (PB, 60 ms Interruption, CCIS, or ISDN)

CDN4 (INSG) = 2 (PB, 60 ms Interruption, or CCIS)

CDN5 (TF) = 3 [Bothway Trunk (BWT)]

CDN6 (TCL) = 1 (DDD Line/Tie Line)

CDN7 (L/T) = 1 (Trunk)

CDN8 (RLP)= 2 [First Party Release (either station or trunk side)]

CDN15 (LSG)= 12 [Speech Line (B-Channel of ISDN)]

CDN28 (ANS)= 1 (Answer signal is provided)

CDN30 (PAD) = 7 [PAD OFF(0db)]

CDN31 (OGRL) = 1 (224 milliseconds)

CDN32 (ICRL) = 1 (224 milliseconds)

CDN34 (GUARD)= 1 (512 milliseconds)

CDN45 (A/D) = 0 (Analog)

CDN49 (TRKS) = 0 (Select from the trunk which becomes idle first)

CDN50 (DPLY)= 1 (Number Display of Dterm between offices is given)

CDN60 (TC/EC) = 1 (Echo Canceller)

CDN65 (INT) = 10 [Q-Sig, (ETS 300 172)/IS-11572]

CDN66 (DOC) = 1-15 (DID Addressing number)

Note: Assign the following additional route data to the Dummy Route.

ARTD – Dummy Route (eg. RT 63)

CDN111 (ADVPRA) = 1 (ISDN PRI Failure Routing Service).

STEP 8: Assign the application data for the route to be used for the MG-SIP96 Virtual Speech Channels.

ARTI – Assign the route application data for the Virtual Speech Channel route, as follows:

CDN47: INTD = 2 (SIP)

CDN68: VIR= 2 (MG connection)

CDN77: RA_RT = 0/1 (Virtual Register is used/Register card is used)

Assign the following parameters for FAX use:

CDN71: FXD = 1 (IP FAX data is in service)

CDN72: FXJS (Jitter Buffer Size for IP FAX [1-30] × 10 ms) ex. Enter “15” for 150 ms.

CDN73: FXPT = 1 (Payload Type for IP FAX is G.711)

CDN74: FXPS(Payload Size for IP FAX [1-4] × 10 ms) ex. Enter “2” for 20 ms.

STEP 9: Assign Virtual Speech Channel and Virtual Signalling Channel trunks.

ATRK - RT: Specify Route Number [1-255]

TK: Specify Trunk Number [1-255]

LENS: Specify Accommodating LEN Location (Six digits)

Data Setting Example for 96-channel operation

Example 1:Example 2:

Note 1: Thefirst Virtual Signalling Channel trunk is assigned in the AMGIL command.

Note 2: Virtual Speech Channels must be assigned in a continuous group on a 1HW (4-Group) basis without any unused ports between the first and last Virtual Speech Channel in the HW.

Note 3: Regardless of the total number assigned, the virtual trunks occupy channels on a 1HW (4-Group) basis. If for example, only a single trunk is assigned, the whole HW (32-channels) is committed exclusively for Virtual Speech Channels; other-type Virtual Channels cannot be assigned to the unused LEN’s.

Note 4: Group 0 of Unit 0 in even number Module groups cannot be used with MG-SIP96.

STEP 10: Assign a Point Code to the Virtual Speech Channel route

ADPC – RT: Specify a Route Number [1-255]

PC: Specify an unused Point Code, [1-16383]

Note: Do not use the Point Code used for CCIS or any ISDN services.

ADPC Example:

STEP 11: Assign the first LEN range of each 32-channel Highway to CSC Group Number

ACSC – CSCG: Specify the CSC Group Number

GROUP: Specify the CIC Group Number

CCH: Specify LEN Location (5 digits) as indicated below

Even CSCG:

For GROUP 0:CCH is the same location as the Virtual Signalling Channel (i.e. the 1st Group No. location in the 1st Highway).

For GROUP 1:If more the 32 channels are assigned then CCH is the 1st Group No. location in the 2nd Highway used, otherwise CCH is the same location as the Virtual Signalling Channel.

For GROUP 2:If more than 64 channels are assigned then CCH is the 1st Group No. location in the 3rdHighway used, otherwise CCH is the same location as the Virtual Signalling Channel.

For GROUP 3 to 7:CCH is the same location as the Virtual Signalling Channel (i.e. the 1st Group No. location in the 1st Highway).

Next Odd CSCG:

For GROUP 0 to 7:CCH is the same location as the Virtual Signalling Channel (i.e. the 1st Group No. location in the 1st Highway).

Example 1:

Example 2:

Note 1: Assign the location of Virtual Signalling Channel to CIC Group (CICG) Number 0

Note 2: The Virtual Signalling Channel is assigned using AMGIL command.

ACSC Example:

STEP 12: Associate the MG-SIP96 Point Code with the MG-SIP96 CSC Group

ACIC1 – PC: Enter Point Code assigned in ADPC

CSCG: Enter CSC group assigned in ACSC

ACIC1 Example:

STEP 13: Assign CIC numbers to the Speech Channel LEN’s:

ACIC2 – PC: Enter Point Code assigned in ADPC

CIC: Enter CSC numbers in sequential order.

LENS: Enter the LEN of the Speech Channel (B-Channel)

ACIC2 Example:

STEP 14: Make Idle the Virtual Speech Channels.

MBTK – RT: Enter Route Number

TK: Enter Trunk Number

MB = 0 (Make-Busy is cancelled.)

STEP 15: Assign the MG-SIP96 as follows:

AMGIL – MG-ID: Enter MAC Address (6 bytes)

FUNCTION = Setting

KIND = SIP-MG

LINE = 0 (fixed)

CH = 0 (fixed)

LENS: Enter the LEN used for the Virtual Signalling Channel

(i.e. the 1st LEN in the 1st Highway used by the MG-SIP96).

Retry = 0

Service Type: Specify QoS settings for Signalling Packets between the PHI and the MG-SIP96.

CH: Enter the number of channels to be used per MG-SIP96 [1-96].

AMGIL Example:

STEP 16: Assign voice control data when connecting to MG-SIP96.

If this command is not assigned, the values for Payload Size and Type will automatically be set to “G711” and “40ms”respectively.

AMGVL – A RT: Specify Physical Route Number used for the MG-SIP96.

LOC-ID: Specify Destination Location ID (LOC-ID=0 must be set when IPPAD card is mounted).or,B RT: Specify Physical Route Number (MG-SIP96) in the case of tandemconnection between MGs.

SETTING OF SERVICE TYPE (VOICE PACKET): Specify QoS settings for Voice Speech packets

PAYLOAD TYPE: Specify Payload type. (G.711 must be set for public SIP network)

PAYLOAD SIZE: Specify Payload size. (20ms must be set for public SIP network)

.

Note: AMGVL command will override AIVCL settings when the MG-SIP96 is used. If AMGVL command is not assigned, then AIVCL settings will apply.

AMGVL Example:

STEP 17:ACNAL, ACND, ACDD–These commands are usually used on the MG-SIP when it’s attached to the PSTN. However, for this scenario no number conversion/addition will be required. The “From” field in the SIP messaging should can be sent as extension number only to the ADTEC server.

STEP 18: After the registration has been completed, reboot the MG-SIP96.

Appendix 1: MG-SIP Complete Configuration

MG(SIP) > show config

[2010-05-11 10:08:56]

[SP-3987:02.00.00.00]

0 = MAC Data

1 = DRS Data

2 = Common Config Data

3 = Port Config Data

4 = SIP Config Data

5 = Route Config Data

9 = Exit

Select a reference number : 1

Primary DRS IP Address : 192.168. 0.130 : PortNo[3456]

Secondary DRS IP Address : 0. 0. 0. 0 : PortNo[3456]

Tertiary DRS IP Address : 0. 0. 0. 0 : PortNo[3456]

Quaternary DRS IP Address : 0. 0. 0. 0 : PortNo[3456]

MG(SIP) > show config

[2010-05-11 10:27:04]

[SP-3987:02.00.00.00]

0 = MAC Data

1 = DRS Data

2 = Common Config Data

3 = Port Config Data

4 = SIP Config Data

5 = Route Config Data

9 = Exit

Select a reference number : 2

set signaling_port_no :

Signaling Port Number : 61012

------

set registration_port_no :

Registration Port Number : 3456

------

set pre_negotiation_port_no :

Pre-negotiation Port Number : 61014

------

set ipx_rtp_port_no :

IPX side RTP Port Number : 51000

------

set sip_rtp_port_no :

SIP side RTP Port Number : 50000

------

set h245_base_port_no :

H245 base Port Number : 40000

------

Does it display more? Y/N = y

------

set drs_qos :

DRS QoS : 0xa0

PRECEDENCE : 5

DELAY : 0

THROUGHPUT : 0

RELIABILITY : 0

COST : 0

------

set rtp_qos :

RTP QoS : 0xa0

PRECEDENCE : 5

DELAY : 0

THROUGHPUT : 0

RELIABILITY : 0

COST : 0

------

Does it display more? Y/N = y

------

set sip_qos :

SIP QoS : 0xa0

PRECEDENCE : 5

DELAY : 0

THROUGHPUT : 0

RELIABILITY : 0

COST : 0

------

set domain :

Domain Name : 0

------

set dnsaddress :

DNS IP Address : 0.0.0.0

------

set hc_alarm :

H/C Alarm type : IPX and SIP Side enable

------

set hc_timer :

H/C timer value : 240sec

------

Does it display more? Y/N = y

------

set musictype :

Music Type : Type1

------

Does it display more? Y/N = y

------

set name_display :

Name Display : disable

------

MG(SIP) > show config

[2010-05-11 10:27:16]

[SP-3987:02.00.00.00]

0 = MAC Data

1 = DRS Data

2 = Common Config Data

3 = Port Config Data

4 = SIP Config Data

5 = Route Config Data

9 = Exit

Select a reference number : 3

Using one-port only

Ether[1]

IP Address : 192.168.0.172

Subnet mask : 255.255.255.0

Interface : Speed/Duplex = Auto/Auto

MG(SIP) > show config

[2010-05-11 10:27:22]