[cisco-voip] media resource

Nate VanMaren VanMarenNP at ldschurch.org
Thu Jan 5 18:31:34 EST 2012


It would either allocate a Transcoder to do g.729 or the phones would do g.729 to the conference bridge.



-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Roger Wiklund
Sent: Thursday, January 05, 2012 3:32 PM
To: Shaihan Jaffrey
Cc: Cisco VOIP
Subject: Re: [cisco-voip] media resource

I'm not 100% clear how resources are selected if all are in the same MRG, but you can try this:

Create a hardware CFB and allow G.729 only. Put that resoure in HW-CFB-MRG Then put the software CFB in SW-CFB-MRG.

Create a MRGL and put HW-CFB-MRG on top, then SW-CFB-MRG after it.
(This is an ordered list)
That way it should always try with the hardware first, fine for G.729 calls but wont work for G.711 so it _should_ try the second MRG
(software) then.

I'm not sure if it just fails for a G.711 call or if it will try with the second resource, but give it a try.

/Roger

On Thu, Jan 5, 2012 at 8:58 AM, Shaihan Jaffrey <schaehan at gmail.com> wrote:
> Any suggestions on below email.
>
>
> On Wed, Jan 4, 2012 at 7:38 PM, Shaihan Jaffrey <schaehan at gmail.com> wrote:
>>
>> hi,
>> What is the best way to keep media resouces in media resource list.
>>
>> I want hardware conference bridge to be used only for G.729 calls, 
>> for all other conference calls G.711 i want to use software 
>> conference bridge. How to accomplish this?
>>
>>
>>
>> Regards
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.





More information about the cisco-voip mailing list