4 SOPHO IS3000 Settings

This Whitepaper describes the projecting aspects how to configure SIP in the iS3000. When the iS3000 is already configured for "IP enabling", “CCIS over IP” or "Software SMA", some of the settings described below might be present already. In principle three things need to be configured : projecting a virtual SIP shelf, a virtual SIP trunk board and the ISG board.

4.1 SOPHO IS3000 System Requierement

• Call@Net 3.5 (or higher).
• CPU3000 with Accelerator Module (AM) and a 32 MB DRAM.
• CIE firmware release A100.10.05 (or higher).
• ISG firmware release 201.03.05 (or higher)
• ISG license number 59 is required to make "SIP trunk" calls.

It is assumed that the necessary SIP related boundaries are known.

4.2 Virtual Hardware

1. Check boundaries (max number of PMs & max number of virtual PMs in a unit)
2. Assign a virtual “SIP” shelf (PM-shelf)
3. Assign a PMC board and then set the PMC board in service.
4. Assign a virtual SIP trunk board
5. Assign the “SIP” service to a service client profile.

Note: Do not put the virtual SIP trunk board/circuits in service, before assigning SIP specific data to the SIP route.

4.2 Virtual Hardware

1. Check boundaries (max number of SIP signalling groups)
2. Assign the correct media access code to the signalling group(s)
3. Assign the Codecs used
4. Assign the payload
5. Assign whether RFC2833 is used (1) or not (0).
6. Check the changed signalling group data.

4.4 Number Analysis and Routes

1. Assign a Trunk Access Code to reach the SIP destination (XX)
2. Set the destination characteristics for destination XX
3. Assign the external numbering scheme
4. Create a route for SIP trunks
5. Enter the route in the route table
6. Set the route characteristics
7. Assign the internal number range in the incoming analysis tree
8. Set the bundle characteristics
9. Assign the bundle to the route
10. Assign the 32 lines to the bundle

4.5 SIP Trunk Specific Data

Before a SIP trunk may be taken into service, certain SIP related items have to be projected first. This is done using OM commands CHSIPD, CHSIPA and RESIPR.

1. Assign SIP specific data to the SIP route (XX).
2. Assign SIP IP related data to the SIP route (XX).
3. Activate registration of the SIP route
4. Check the projected SIP items.
5. Set the virtual PMC and SIP trunk board/circuits in service (board previously assigned in sub-section "Virtual Hardware")

4.6 Projecting the ISG

REMARKS:

• The ISG must be loaded with firmware release fa2010v1.305 or higher. Note that in a “CCIS over IP” network with an SV7000 release fa2010v1.305 or higher is required.
• The CIE (in CCS systems) must be loaded with firmware release fa1001.003 or higher.
• "IP-enabling", "IP-trunking" and “CCIS”may share ISG channels with SIP, provided that the ISG license is present. Besides the possibility to have only one route to the ISG it is also possible to project more routes and to apply bundle splitting. Bundle splitting can be done in order to leave a guaranteed amount of ISG-channels available for SIP calls. In that case, the no "ISG channels" license alarm will be generated when the to IP enabling, IP trunking routes and CCIS allocated channels are exhausted, congestion tone is given.
• It is possible to achieve load-sharing when two (or more) ISGs are present in the system.

1. Assign the ISG with board-type 18 in a 'real' PM shelf.
2. Assign an analysis tree to DIAL-TYPE 11: “media dialling”
3. Assign the media access code (trunk access code) to the destination (the ISG) in the analysis tree related to the dial type “media dialling”
4. Set the destination characteristics
5. Create a QSIG route
6. Enter the route in the route table
7. Set the route characteristics
8. Set the bundle characteristics
9. Assign the bundle to the route
10. Assign 10, 20, or 30 lines (depending on the ISG license) to the bundle
11. Make sure that on the TFTP server a prebisg.txt (or prebisg<mac-address>.txt in case only one specific ISG should be loaded) file is present. This file contains the name of the used ISG software package, e.g. fa2010v1.305.
12. Make sure that on the TFTP server the software package fa2010v1.305 is present
13. Set the ISG board and circuit 0 into service
14. To check the settings on the ISG, start up a browser and fill in the IP address of the ISG. To login, use "isgadmin" for both the Username and Password (case sensitive and fixed).

Keep in mind that the browser output is mainly for test/check-purpose. This means that the layout might be enhanced in the future release of the ISG. Furthermore not all data is valid e.g. when the data is "unknown", then it means default value. In the 'Channel Status Overview', the second column indicates the status of the channels. This can be :

Note that for a CCIS call it is not possible to discriminate between an incoming or outgoing call.

4.7 Security Aspect

From ISG release fa2010v1.501 onwards it is possible to switch OFF the ISG web server page. To achieve this the following text lines have to be included in the preisg.txt file :
[WebServer]
WebServerEnabled = 0

Default = webserver will be on.

4.8 SIP Trunking parameters overview

(note: to be used as a guide only)

4.9 Configuratiion Data Overview