atcomsystems.ca/forum Forums TDM Business Telephone Systems NEC Telephones & Systems K-CCIS/CCIS between SV8100 and 2000 IPS?

Hi Everyone

I am trying to integrate a new SV8100 into an existing network of 2000 IPS standalones, which use H.323 IPtrunk and CCIS to talk to one another. So I'm quite familiar with trunking between IPS systems but have never had to get extension dialling to and from an SV8100. Does anyone have any programming examples/hit lists/tips for me that might expadite my success!?

Many Thanks in advance.

Alex

What card(s) are you using in the 2000 IPS & sv8100?

Hi

I'm using an R14 CPU and E1 32IPLA card in the IPS and in the SV8100 I have the 32IPLA card + the SV8100 main software is 6.01.

On the IPS I I have CCIS and IPT licenses. On the SV8100 I have 4 x IP Trunk, and a KCCIS license.

I'm trying to do CCIS over IP.

Thanks!

Do you have a copy of the SV8100 networking manual?

Hi

I have found one that can be viewed online only (but not downloaded. We are an NEC dealer, but that is one of the manuals they have not supplied...

Despite being an IPS engineer for 10 years now (so I know the command manual, amongst others, for the IPS like the back of my hand). I didn't quite know where to start...

Thanks

Just to clarify - do you believe I have the correct hardware and licenses? I am going to go through the KCCIS programming in the VoIP manual and give it a go. Unfortunately in the UK, you'd expect a multi-billion dollar company like NEC to have a large technical presence - but they don't. Which is why I resort to forums like this...

If you have a CCIS/IP license on the IPS (which you must, since you have an existing network) and if you IPS licenses support enough links to include the 8100, then you should be golden so far as the IPS is concerned.

Of course, you presumably also have to have the CCIS/IP licenses and sufficient link licenses on the 8100.

Do remember that NEC treats CCIS/IP as if it were a physical topology, that is, every PBX links to a specific other PBX...

A <--->B<---->C
A needs one link license, B needs two, C needs one.

The H.323 part gives me some concern. You get a smaller feature set using that according to the networking manual.

Telephoneguy: Not sure if the licensing is different where you are, but our licensing for CCIP/IPT on the IPS doesn't work like that. You buy 1 x IP Trunk and 1 x CCIS and you can connect to as many IPS systems as you like. I have one installation with 12 seperate IPS systems, all communicating using IP trunk/CCIS and each only has one license of each...

Ok so I decided to try and get dialling from the IPS first to the SV8100, as I know the IPS far better. So far I get busy tone. The IPS is on 10.44.0.21 (22 for IPPAD) and the IPLA within the SV8100 is on 10.44.0.41 (42/43 for the DSPS). So far I get busy tone. I think there may be something extra I need, or something which isn't cross compatible between the systems, but I don't what it is, because there is no manual for saying what it necessary for IPS > SV8100 programming!

I did the following on the IPS:

CM 050 > spare AP card number : 38
Where the 1st spare AP card will usually be 08 and 38 indicates this is a virtual
IP trunk
CM 054 > AP card number from above: virtual PIM number
12 and 13 are virtual PIM’s used for virtual IP trunks
CM 056 > 08 : 0
Where 08 is the AP card number and 0 indicates signalling converter.
CM 14 > xxzzz : D180
Where xx= the AP card number used above ie. 08 and zzz is the LEN number of the virtual PIM eg. 000 to 063. D180 is the first available trunk number for the IP trunk as specified in the easy install script. This command needs to be repeated for every trunk(Channel) before moving to command 0607 below.

CM 0607 > 0 : 08 Where 0 is the IPT virtual circuit (Normally 0 as with IPS usually only one circuit
fitted as it supports Point to Multi-Point) and 08 is the AP card number.

CM 3000 > 180 : 60
180 is the 1st trunk number and 60 is the trunk route number used for an IP trunk. This command needs to be repeated for every trunk number as defined in command 14 above.

3500 > 60 : 04
This assigns trunk route 60 that was administered above to be a tie line (04).

CM 3504 > 60 : 2
The 2 indicates that answer signal arrives for trunk route 60.

CM 3505 > 60 : 1
The 1 indicates that release signal arrives for trunk route 60.

CM 3509 > 60 : 03
This administers the trunk route 60 incoming connection signal for wink
start/CCIS.
? Execute CM 3520 > 60 : 00
This administers the trunk route 60 outgoing start conditions for wink start/CCIS.

CM 3590 > 60 : 0 indicates that trunk route 60 will use No7 CCIS signalling.
CM 3591 > 60 : 0 This command assigns trunk route 60 to IPT virtual circuit 0.
CM 3035 > trunk number : 001 Here we are assigning the 1st IP trunk namely 180 to the CCIS circuit number (CIC No) eg 001. Therefore 181 would go to 002 and so on for all the IP trunks administered in command 14.
CM 360 > 6060 : 0 This will allow trunk to trunk connection of the IP trunk route ie.60
CM A700 > 0 : 254 0 is the IPT virtual circuit number, 254 is used here as a control channel for the
virtual IPT circuit. (254 is the last available trunk number)

CM A701 > 0 : 00002 - Original Point Code

CM A746 > 0 : 0 This administers virtual IPT circuit 0 for point to multipoint connection type.

CM 200 > 4: A129 This assigns the far end extension number plan to the LCR group table 3.

CM 8AA000 > 3 space 4003 Here we are assigning LCR group table 3 to area code development table
4003.

CM 8A4003 > 1st digit of far end extension numbers : 0100 is used here as the route pattern number.
CM 8A0100 > 1 : 10060 100 is the LCR pattern number 60 is the IP trunk route number
CM 8A5100 > 167 : 000 167 denotes that LCR pattern number 100 is to be steered to 1st IP pattern
number 000.
CM 8A5100 > 168 : 00001 Original point code of the far end (OPC of the SV8100) 168 denotes the OPC number of the far end which is input as a 5 digit number
CM 5B01 > 00000 : 010044000041 - IP address of far end processor
The 00000 is broken down into 000 which is the IP address pattern number from 8A5100 (FD 167) above and the 00 which NEC manuals state means its IP address 0.
CM 853 > 1st digit of the far end extension number : the extension length If the extensions were 2xxx you would enter 2 and then 04.
CM A726 > 0 : 0 This will pass CLI information across the Virtual IP Trunk.

This is all normal stuff as far as I am concerned. I have simply modified what I would do for another IPS CCIS connection for the SV8100.

On the SV8100, I used the wizard for KCCIS and assigned it the OPC of 1, told it the other end's IP address.....any not much else.

Anyone got any ideas?!

Thanks

Ok, I spoke too soon. I can dial from the IPS to the SV8100. I get speech!

I'm a bit stuck now going the other way - because I'm still a bit naive on the whole F-Route thing... Does anyone have a shortlist of commands on the SV8100 just to get it to send any 4xxxx number in the numbering plan to be pushed out to the IPS sitting on OPC 2 / 10.44.0.21?

thanks!