CallManager 4.x and 6.x to Acme Session Border Controller

Unanswered Question
Apr 21st, 2008
User Badges:

Hello All,

I have a situation where a service provider wants to connect two Cisco CallManager clusters to a SIP Trunking provider. One cluster is running 4.2 and the other is running 6.x. They have suggested we purchase an Acme Session Border Controller to talk H.323 with the CallManager clusters and SIP with them.

I was curious if anyone on this forum has ever tried anything like this. Are there any proprietary Cisco features in H.323 that may be a problem when talking to the Acme? Will an MTP be needed between the Cisco CallManager and the Acme?

Any help is always appreciated....



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
ebreniz Fri, 04/25/2008 - 08:43
User Badges:
  • Silver, 250 points or more

The session border controller will be used instead of an ISDN gateway for outbound calls.

Please see the section 'H.323-to-SIP IP-to-IP Gateway Connections' for your case.

Restrictions for H.323-to-SIP Connections on an IP-to-IP Gateway

"Changing codecs during rotary dial peer selection is not supported.

"Delayed-media to slow-start signal interworking is not supported.

"Fast-start to delayed-media signal interworking is not supported.

"GSMEFR and GSMEFR are not supported.

"Media flow-around is not supported.

"Slow-start to early media signal interworking is not supported.

This should help alot.


This Discussion