4KV7 to CUCM

[jschnarkey]

Anyone have their 4K tied to a Cisco CUCM?
We have a 4K V7 tied to an OSV and we are adding a Cisco CUCM also. I have set 4 STMI's into a trunk group and mirrored the programming to the OSV and was just wondering if anyone knew of anything different for the COT, COT, LODR etc I should be aware of.
Not too worried about the RICH or netroute as thats pretty generic to route the calls. I'm more concerned with Station CID presentation, things like that....

 

[jschnarkey]

Still wondering if anyone has a 4K connected to a Cisco call manager via SipQ, STMI trunk group.
Also, If I have two call manager 'subscribers' would I be able to point these STMI's to both with the CGWB programming for Redundancy;

CHANGE-CGWB:MTYPE=CGW,LTU=3,SLOT=1,TYPE=SIPTRSSA,SIPREG=YES,REGIP1=0.0.0.0,
PORTTCP1=5060,PORTTLS1=5061,REGTIME=300E,RGIP2=0.0.0.0,PORTTCP2=5060,
PORTTLS2=5061;

And lastly, We do not use GKREG for our 4K to OSV SIPQ trunks, do I need it to trunk to our Cisco CUCM?

 

[member 1453342]

There are some guides googleable for 4K-Cisco config. Cot and cop are in there. I would probably copy OSV config for that and look at COT only if you have a problem. Even the guides you can find won't agree.

Don't use SIP-Q for connection to Cisco, it won't understand it. You need native SIP. So pay attention to number of channels in CGWB, make sure you have channels set for SIP not SIP-Q.

For where to enter the Cisco IP address - CGWB REGIP1 and REGIP2 are for connection to OSV. You don't use that. Also GKREG is no longer the preferred method. For V7, a profile from the STMI GUI should be used, it's in the web interface to the STMI. There is more flexibility with using profiles, a finer degree of control on the configuration. But it means the STMI is forced to that endpoint only. With GKREG one STMI can reach multiple endpoints. Not if you are using profiles.

Connection to Cisco from 4K is still PSR - Project Specific Release. Not supported without agreed PSR status. But it will work.

 

[jschnarkey]

Thank You Moriendi.
I'll be able to digest this info later this week. I suppose If I have issues I can always get our maintenance agreement to sort it out for us.
I have a couple of months to get this worked out while the CUCM is on order and then gets programmed and installed.

 

[jschnarkey]

I have had some time now to work with this and I have the 4K v5 to CUCM 8.5 PDF. I received three copies , one from Unify (ATOS) 4K engineer.
I now have a few questions.
1. You say that "CGWB REGIP1 and REGIP2 are for connection to OSV. You don't use that" So I would enter 0.0.0.0 for both reg1 and reg2 but leave the rest as is for codecs and such?
2. What are the gateway parameters in LDAT? GW1, GW2, etc?
3. In the WBM of the STMI's I see the customer lan page of the PDF (PDF Pictures) shows the STMI IP address and gateway but then on the SIP parameters page the SIP server (Registrar) address is the same address. This makes no sense to me. Should this be the CUCM subscriber that I want to send traffic to?
4. My 4K to OSV trunks are setup with 30 channels per STMI. example, 1-3-1-0 = 30 and 1-3-1-1 = 20. Can I use 30 and 30 for a total of 60 per STMI?

Regards,
Jake

 

[donb01]

I don't know the integration, but can tell you that a STMI4 card can be partitioned for multiple device support, such as both SIP and HFA phones. In that case the gateway IP is the same for both SIP and HFA, but the two protocols use different network ports for one thing, and the board knows the difference of what is SIP vs HFA. I haven't done anything with SIP trunking so I don't know if it is good practice to partition a board for some SIP phones and some SIP trunks, for example, but if that was the case the IP of both gateways would still be the same.

You can use BFDAT to look at the FCTID assigned to the STMI or NCUI board and that will tell you how that board is currently partitioned.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[jschnarkey]

Thanks Donb01,
All of my STMI's are either trunk or HFA, no mixing on a board and I have plenty of boards and licensing to make anything happen.
I also do not use SIP on the 4K. We have an OSV for that but I see that the trunks to that are built with SIPQ. I will change the CGWB parameters on these boards to SIP for the CUCM. We also have an Avaya definity and a Shoretel tied to that, with three main hospital campuses. The 16 Fujitsus have just been decommed so finally they are not an issue any longer.
I'll ignore the gateway parameters in LDAT. I have never used those before.
The plan is to be 100% CUCM in a couple years, starting this summer, late spring.

I'll figure it out eventually. I have most all of it built and just need to build the profiles in the STMI WBM.
I think there is a typo in the PDF that UNIFY sent me and am working to get that verified.

 

[jschnarkey]

OK so the engineers at UNIFY have told me that I will need to use GKREG in order to use the Cisco UCM profile in my STMI's
I do believe I'll need a crash course in GKREK please. I do not know what info you will need to assist me with this so just ask and I'll provide STMI counts, ip addresses, etc....

 

[member 1453342]

Dear oh dear. "F" for "Fail" for your Unify engineer. GKREG was the way it used to be configured, when you didn't do much in the card GUI other than set codecs etc. But there's a limit to what can be configured in CGWB, so more configuration has been piled into the card GUI and GKREG configuration is now no longer used for native SIP connections. You cannot use profiles at the same time as GKREG and the Unify IP solutions document itself advises profiles should be used for "more security" (IP address checking for native SIP). The old GKREG functionality is still there, but it's superseded and unless you need to address multiple endpoints there's no reason to use it, and you will lose the functionality available in the profiles if you do.

Your query above
1 - regip are left at 0.0.0.0
2 - you don't need ldat parameters for GW, they represent the GKREG entries that you should not have.
3 - in WBM, under explorers, voice gateway, sip trunk profile parameter, make sure it's set to use profiles for native sip. It is by default.
4 - in WBM, under explorers, voice gateway, sip trunk profiles, find the CUCM profile and enter the IP of the Cisco SIP endpoint under "proxy". Above that you'll probably see it's set to UDP. Make sure Cisco is the same or change to TCP (can't do that with GKREG!). Apply that config, then right click on the CUCM profile and "Activate".

That's it. No GKREG required. But remember with profiles you cannot now share this trunk with any other partner system, it will only address that IP configured in 'proxy'. That restriction is for trunks only though, subscriber functionality is unaffected.

If this STMI has been used for something else you might have some config in CGWB that will cause you a problem, I would consider a delete and re-add or change-cgwb with an initcgw to default everything.

Pay attention to the number format being sent to CUCM. If you test it and it doesn't work, take a Wireshark trace... If there is no invite, it's likely WBM config. If the invite is there but the numbering is wrong, it's 4K LCR.

 

[jschnarkey]

Moriendi,
I know not why he would say that but it was at a point where I was getting an error and not able to assign a CUCM profile in the WBM. I have worked through that though.
I have two of my four STMI's programmed with profiles late Friday and called it a day. I'll do the other two today. I think I have learned that you have to start in the order that you have them in the trunk group / TDCSU. I tried starting in the middle for no particular reason and it would not allow me to set a CUCM profile but when I started at the beginning I was able to get the first two completed.

I think I have everything I need but have a question with the COT. I have two PDF documents of approximately the same age and they are different.
One has:
PRIORITY FOR AC WILL BE DETERMINED FROM MESSAGE PRI
RECALL IF USER HANGS UP IN CONSULTATION CALL RCL
TRUNK CALL TRANSFER XFER
TRUNK SIGNALING ANSWER ANS
KNOCKING OVERRIDE POSSIBLE KNOR
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
NETWORKWIDE AUTOMATIC CALLBACK ON BUSY CBBN
NETWORKWIDE AUTOMATIC CALLBACK ON FREE CBFN
REGISTRATION OF IMPLAUSIBLE EVENTS IEVT
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
END-OF-DIAL FOR BLOCK IS SET BLOC
EMERGENCY OVERRIDE/DISCONNECT VIA S0/S2 LINE PROV
SEND NO NODE NUMBER TO PARTNER LWNC
ACTIVATE TRANSIT COUNTER ADMINISTRATION FOR S0/S2 LINE ATRS
CONNECTION TO ROUTE OPTIMIZATION NODE ROPT
TSC-SIGNALING FOR NETWORKWIDE FEATURES (MANDATORY) TSCS
TRUNK SENDS CALL CHARGES TO ORIGINATING NODE NUMBER TRSC
USE DEFAULT NODE NUMBER OF LINE DFNN
CALL FORWARDING PROGRAMING FOR OTHER SUBSCRIBERS CFOS
PIN NETWORKWIDE POSSIBLE PINR
AOC PER CALL (AUTOMATICAL OR ON REQUEST), MAND. CORNET-NQ AOCC
AUTOM.DTMF CONVERSION ON INCOM.CALL WHILE IN TALK STATE AMFC
SEND DIGITS VIA IN.BAND DTMF BEFORE ANSWER IBBA
NO TONE NTON

And the other has:
TRUNK SIGNALING ANSWER ANS
CALL EXTEND FOR BUSY, RING OR CALL STATE CEBC
DON'T RELEASE CALL TO BUSY HUNT GROUP BSHT
END-OF-DIAL FOR BLOCK IS SET BLOC
SEND NO NODE NUMBER TO PARTNER LWNC
INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR NLCR
TSC-SIGNALING FOR NETWORKWIDE FEATURES (MANDATORY) TSCS
USE DEFAULT NODE NUMBER OF LINE DFNN
INCOMING CIRCUIT FROM SYSTEM WITHOUT LCR (DATA) NLRD
LINE WITH IMPLICIT NUMBERS FOR CARRIER LINC
NO FLAG TRACE NOFT
NO TONE NTON
AMO-COT -111 CLASS OF TRUNK FOR CALL PROCESSING
DISPLAY COMPLETED;

I suppose we'll find out when testing commences. I used the second one because thats the PDF that Unify sent to me.
I'll get the other two STMI's completed today and holler if I run into any problems.