Legacy Ports Stomping on CM Ports

[admin_2]

My apoloigies if this is covered in here somewhere - I hadn't been able to find it so hopefully some insight is available...<br><br>We were an EFT site for unity 3 and last week received word that for support from TAC we'd have to upgrade to 3.0(2) (we were on one fo the 3.0(1)... builds).<br><br>The upgrade went fine - but when the system came back up, no matter how we set the ports in Unity, all 16 logical ports on Unity get stolen by the traditional switch (we're on a dual switch integration with a dialogics 12-port board, supposed to be 12 ports for the NEC NEAX2400 and 4 ports for the Call Managers...<br><br>The Unity AV driver is registering the ports with call manager fine but they just ring and ring from call manager and on the status monitor you see nothign on those ports...while when dialing in from the NEAX side you see your call rotation zooming right past #12 and on to whap 13-16 :-(<br><br>How deep am I now - we're used to unity...we don't want to go back to Centigram...please o please o please... :-)<br><br>Ken Johnson<br>Mgr. Network Services<br>LeTourneau University<br>http://www.letu.edu/

[#2]

Hey Ken.

This is likely an issue with the Dialogic driver snarfing up all your allowed ports before the Cisco TSP can grab any. Here's a post from Steve a while back that probably will address your issue:

http://avforums.isomedia.com/cgi-bin/showthreaded.pl?Cat=&Board=unityent&Number=4273&Search=true&Forum=unityent&Words=upper&Match=Entire Phrase&Searchpage=0&Limit=25&Old=allposts&Main=4271


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

[#3]

Jeff,

Thanks for the post - I had recalled Brad (our EFT miracle worker) dealing with this during our EFT at about the same time I posted this and so I'd actually tried that - and was bummed out thinkning I had some strange new error - but upon looking at it from home tonight it looks like I entered the upper bound (which should be 12) as 12 in a DWORD *hexidecimal* - I converted it to decimal but of course across the street I have no 79xx's to try the CM integration so will try tomorrow - thanks for the tip! I hope that solves it. by the way - in that article I saw a bold/italic emphasis on the word "upper" - was that focusing on the odd capitalization (or lack thereof) (I wasn't sure if capitalization mattered or not on this key (or in the registry as a whole for that matter...

Here's praying that my hexidecimal error was tohe problem...

Glad to have "googled" across answermonkey and in turn this forum - it looks like a great resource :-)

Ken Johnson
Mgr. Network Services
LeTourneau University
http://www.letu.edu/

[#4]

OK - I opened a TAC case on this and was able to get it resolved...

Here was the fix:

When I preformed the upgrade from 3.0(1) to 3.0(2), I did not remove the Cisco AvTSP and the Dialogic software. Thus, when I upgraded unity, it reinstalled the dialogic software, reversing the proper order of the installations on those.

TAC had me remove the registry hacks, TSPs and Dialogics - reboot, and then reinstall the dialogic board, reboot, reinstall the TSPs - and everything worked great...

TAC couldn't find anything in the docs to instruct removal of that software prior to upgrade (at least not while we were talking) so they're trying to figure out whether it's in there somewhere and I missed it - but my error or not, it works! :-)

Thanks for everyone's help :-)

Ken Johnson
Mgr. Network Services
LeTourneau University
http://www.letu.edu/

[#5]

yeah, the Dialogic TSP has to load first (quirks with their TSP), so if the CiscoTSP loaded up front that'd cause all kinds of grief.

I think somewhere in the release notes (at least it used to be there) was the reccomendation to always remove the TSPs if you're going to install them again. Dialogic's setup (which we call in the background) doesn't behave real well on upgrades.


Jeff Lindborg
Unity Product Architect/Answer Monkey
Cisco Systems
lindborg@cisco.com
http://www.AnswerMonkey.net (new page for Unity support tools and scripts)

[#6]

Argh...even after I fixed the decimal/hexidecimal issue, calls to the dialogic-side are still tromping all over ports 13-16...

Tried removing, rebooting, readding, and twice rebooting the 4 CM ports back in and the same results...

Does this sound at all logical?

Thanks :-)

Ken Johnson
Mgr. Network Services
LeTourneau University
http://www.letu.edu/