That's what I thought thanks.
Yea the BCM didn't start playing nice with SIP until release 5. Do you have the latest patches loaded on the system that were avalible?
This should work on BCM 50 R3. The "trick" is in the settings. We have SIP Trunks between UCx 50 and BCM 50 R5 & R6. Per the BCM 50 R3 documentation:
"This system supports SIP trunks and H.323 trunks. Both types of trunks support connections to
other BCMs, a central call server such as Succession 1000/M, and trunk-based applications. SIP
trunks and H.323 trunks are assigned to a single Pool, and the routing decision to route calls via
H.323 or SIP is made based on the routing modes of the two services (Direct/Gatekeeper/Proxy)
and the combined routing table."
I have mine setup as a simple peer trunk between the systems. In the fields of the BCM IP Trunks, check these settings.The domain would be the UCx domain. Example, the default is "ucx50.local" in my case. Set the IP Address of the UCx . Port "0". Be SURE to set the Gateway type to "other' and turn the MCDN to OFF
This should work as long as you have either H.323 or SIP Trunks activated with keycodes. H.323 keycodes will support BOTH H.323 or SIP. SIP keycodes support SIP ONLY!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.