I have not used the 3com but I do know that it is sip based adn call manager is not. if the 3com can support an h.323 trunk you should be able to tie the two together. if it can not do h.323 you may have to go the the least common demonator being a isdn line. one last thought would be the callmanager 4.0 supports sip trunks and may work with the 3com.
The 3Com NBX 100 and Superstack 3 doesn't support SIP today. It is their intention to implement it in the future. Today, your options to connect the two are via analog or digital (T1 or PRI). 3Com has a 4-port fxo and fxs board for the NBX, and they also have a 16 port high density fxs board from Citel available. The route you choose may depend on how many simultaneous calls you need to support. If 3Com would support Analog E&M, that would have been the best solution.
If you want to do this via software, you can open up H.323 on the NBX as well. The H.323 licensing is based on ports, and is $800 list per port for 3Com.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
[toc:faq]CUCM Database Replication is an area in which Cisco customers
and partners have asked for more in-depth training in being able to
properly assess a replication problem and potentially resolve an issue
without involving TAC. This document discusse...