Cisco 7985G

Answered Question
Mar 14th, 2007
User Badges:
  • Cisco Employee,

Can two disparate voice networks from two different companies communicate using the Cisco 7985G?

Correct Answer by paolo bevilacqua about 10 years 2 months ago

I would use a 28xx router with the feature called "CCME" to which all your video devices will register.It is quite simple and well documented, beside it's a real router and can do many functions.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
paolo bevilacqua Wed, 03/14/2007 - 14:52
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

Absolutely, as long you have IP connectivity the possibility is there.

nbhat Wed, 03/14/2007 - 16:14
User Badges:
  • Cisco Employee,

Thanks. Any idea on the best way/product/box/solution to connect two disparate voice network specifically to enable video phone communication using Cisco 7985G?

Correct Answer
paolo bevilacqua Sun, 03/18/2007 - 20:53
User Badges:
  • Super Gold, 25000 points or more
  • Hall of Fame,

    Founding Member

I would use a 28xx router with the feature called "CCME" to which all your video devices will register.It is quite simple and well documented, beside it's a real router and can do many functions.

mmelbourne Tue, 03/20/2007 - 14:00
User Badges:
  • Silver, 250 points or more

I would consider the use of the Multiservice IP-IP Gateway (aka. Session Border Controller). This is an IOS feature which runs operates with a "via-zone" Gatekeeper (co-resident on the IPIPGW box).


I used this, and mapped my 7985 and VTA DNs (registered the CallManager) onto valid E.164 addresses with the necessary zone prefixes configured on the gatekeeper, which in turn, was registered with a Directory Gatekeeper.


The IPIPGW effectively re-originates call legs, effectively hiding the internal structure of the network (helping to solve the NAT issues with video conferencing), and the IPIPGW controls call admission control and can optionally support RSVP.


CallManager provides the interoperability between Skinny (SCCP) endpoints and more traditional H.323 VC endpoints. The IPIPGW can also provide interoperability between H.323 and SIP (usually used in this context to connect to service provider trunks).


Please rate helpful posts.

Actions

This Discussion