Re: Allocation resources for a call

Christian,

El 11/12/2011 23:56, Christian Groves escribió:
> HEllo Javi,
>
> I'm not sure what the issue is? This just sounds like a normal 
> transcoding case.
> i.e. For Termination connection to equipment A set codec X, for the 
> Termination connected to equipment B set codec Y. The MG simply 
> transcodes the codec format when sending a A or B.

The problem is that the connection with A and B is performed within the 
same call. Thus, in phase A, MG sends to equipment A with codec X, but 
also should allocate the resources needed for Phase B.

Otherwise, the call can start and, to change to Phase B, the MG may not 
have the resources to communicate with equipment B with the codecY, 
needing to release the call. Thus, the objective is to prevent this 
happening, ensuring that once the call begins, MG will have reserved all 
resources required for that call.

Javi
>
> Regards, Christian
>
> On 11/12/2011 12:03 AM, Javi wrote:
>> I have a callwith the following 3 phases:
>>
>> A) Phase A: MG may carry media to a equipment A using the codec x.
>>
>> B) Phase B: MG may carry media to a equipment B using the codec y.
>>
>> C) Phase C: again, MG may carry media to the equipment A using the 
>> codec x.
>>
>>
>> In that case, what is the most appropriate way to model the call on 
>> the gateway to ensure that once the call starts the gateway will have 
>> the necessary resources for all phases?
>>
>> (i) 2 terminations (in the same or different context?) using the 
>> property "StreamMode=Inactive":
>>
>> * Termination 1 with:
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>>
>> * Termination 2 with:
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y
>>
>> In phase:
>>     (A, C) Termination 1 with StreamMode=SendRecv; Termination 2 with 
>> StreamMode=Inactive
>>     (B) Termination 1 with StreamMode=Inactive; Termination 2 with 
>> StreamMode=SendRecv
>>
>> ===
>>
>> (ii) 1 termination with 2 session descriptions with ReserveGroup=true:
>>
>> In Phase A:
>> LocalControl {
>> ReserveGroup = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y
>> }
>>
>> In Phase B:
>> LocalControl {
>> ReserveGroup = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>> }
>>
>> In Phase C:
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>> }
>>
>> ===
>>
>> (iii) 1 termination with 1 session descriptions with 
>> ReserveValue=true to allocate the resources:
>>
>> Phase A)
>> LocalControl {
>> ReserveValue = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x  codec_y
>> }
>>
>> Phase B)
>> LocalControl {
>> ReserveValue = True},
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_B
>>     m=audio port_B  RTP/AVP codec_y  codec_x
>> }
>>
>> Phase C)
>> Local/Remote {
>>     v=0
>>     c=IN IP4 IP_A
>>     m=audio port_A  RTP/AVP codec_x
>> }
>>
>>
>>
>> Regards,
>>
>> Javi
>>
>> _______________________________________________
>> Megaco mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/megaco
>>
> _______________________________________________
> Megaco mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/megaco
>