We have a customer looking at running QSIG between an NEC 2400 PBX and a 2600/w HDV-T! module. There is a call manager on the IP side. Requirement is simply to route calls from the CCM to PBX and vice-versa. All PSTN access is via PBX.. I can see no reason why QSIG could not be used between the 2600 and the PBX, but the customerm syas that another vendor and "Cisco' told them that QSIG would not be supported in that environment. Is anyone aware of any issues that woud prevent this from working? Thanks
Im not sure why "Cisco" told them this scenario would not be supported. He can run QSIG with the 2600 with an NM-HDV. Now the only problem here is QSIG uses facility messages to transfer propietary information form the PBX to the Call Manager. The Call Manager cannot decode facility messages at this time and therefore that would not work. With regards to basic call routing that should work without any problems.
Just out of curiosity - last year we implemented an NEC NEAX2400 / CallManager integration using 5ess/NI2 over PRI a 3662 HDV module. It took a while back then but we got it working. The whole time we were struggling getting the 5ess/NI2 emulation up - the NEC rep kept commenting that he wished we could support QSIG.
Not being a protocol or NEC expert :-) Is QSIG anthoer protocol that would replace 5eSS/NI2 if we used it here? Since we currently have 5ESS up and running - would we see any noticeable benefit from this - I presume the proprietary information that's not supported probably contains calling name. etc. We currently have calling number working of course.
Just trying to see if there's any reason we'd want to move to QSIG or exactly what it could do for us in the future (ie will future Cisco support include things we might covet like calling name, etc.) Just figured it might be a "tighter" integration than the generic 5ESS/NI2...
I wouldn't see any reason to convert now that your setup is workiing. QSIG was introduced primarily to provide interoperability between different ISDN vendors. It does seem to be implemented pretty consistently across vendors, so generally your life will be easier if you use QSIG in cases where more than one vendor is involved. I'm not positive but I believe calling name is not supported - just ANI.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...