[cisco-voip] H.225 Gatekeeper Trunk or ICT Non-Gatekeeper Controlled Trunk

Wes Sisk wsisk at cisco.com
Wed Sep 16 13:17:58 EDT 2009


You might find this interesting:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/7x/media.html

/Wes

On Wednesday, September 16, 2009 12:42:54 PM, steve.siltman at assurant.com 
wrote:
>
> The cluster I'm testing with doesn't have a gateway configured or any 
> hardware resources to use.   I could configure a dspfarm profile from 
> a router in my lab and test using those resources?   If the call is 
> between three ip phones on two different clusters, can they use 
> hardware resources like this?  This is eye opening for me.
>
> -Steve
>
>
>
> *Wes Sisk <wsisk at cisco.com>*
>
> 2009-09-16 11:09
>
> 	
> To
> 	steve.siltman at assurant.com
> cc
> 	cisco-voip at puck.nether.net
> Subject
> 	Re: [cisco-voip] H.225 Gatekeeper Trunk or ICT Non-Gatekeeper       
>  Controlled Trunk
>
>
>
> 	
>
>
>
>
>
> CM's software conference bridge only does g.711 so you would need a 
> transcoder. alternatively, you could just use the dsp's as a hardware 
> conference bridge for g.729 calls.  this is the typical approach.
>
> /wes
>
> On Wednesday, September 16, 2009 11:19:20 AM, 
> _steve.siltman at assurant.com_ <mailto:steve.siltman at assurant.com> wrote:
>
> I'm stuck.  Both of these trunks work great for call routing.  Neither 
> of these work when I try to conference two parties together.  What am 
> I missing?  I have these trunks using there own Device Pool with there 
> own region.  I have tried to put Call Manager software media resources 
> in an MRG/MRGL and applied it to both the device pool and trunks on 
> both sides.  I have these regions using G.729.  
>
> Throw me a bone please.
>
> -Steve
>
> ------------------------------------------------------------------------
> This e-mail message and all attachments transmitted with it may 
> contain legally privileged and/or confidential information intended 
> solely for the use of the addressee(s). If the reader of this message 
> is not the intended recipient, you are hereby notified that any 
> reading, dissemination, distribution, copying, forwarding or other use 
> of this message or its attachments is strictly prohibited. If you have 
> received this message in error, please notify the sender immediately 
> and delete this message and all copies and backups thereof.
>
> Thank you.
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> _cisco-voip at puck.nether.net_ <mailto:cisco-voip at puck.nether.net>
> _https://puck.nether.net/mailman/listinfo/cisco-voip_
>  
>
> ------------------------------------------------------------------------
> This e-mail message and all attachments transmitted with it may 
> contain legally privileged and/or confidential information intended 
> solely for the use of the addressee(s). If the reader of this message 
> is not the intended recipient, you are hereby notified that any 
> reading, dissemination, distribution, copying, forwarding or other use 
> of this message or its attachments is strictly prohibited. If you have 
> received this message in error, please notify the sender immediately 
> and delete this message and all copies and backups thereof.
>
> Thank you.
>
> ------------------------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090916/94d1c3ec/attachment.html>


More information about the cisco-voip mailing list