Re: Multiple Streams and mutiplex terminations

Hello Javi,

Please see my replies below.

Regards, Christian

On 20/10/2011 8:29 PM, Javi Muñoz wrote:
> Hello Christian,
>
> Sorry, I missed it.
>
> You wrote:
>
> [Chistian] There's no means via the multiplex descriptor to indicate 
> StreamIDs in addition to the TerminationID. The multiplex descriptor 
> can only have TerminationIDs.
>
> [Javi] Then, Do you mean MeGaCo does not support this kind of context?
>
[CNG]No, I mean that the syntax doesn't support adding streams in the 
multiplex descriptor. This is different to what's happening in the Content.
>
> [Christian]  Also you can't specify a number for N in "Nx64k" in the 
> Multiplex descriptor. For Nx64k N is assumed by the number of 
> terminations added to the MuxDescriptor.
>
> [Javi] Again, MeGaCo would not support kind of multiplexing.
[CNG] No, Megaco does support Nx64K, the syntax doesn't support 
including N in the multiplex descriptor. As I mentioned its implied by 
the number of terminations in the list of termination assigned to the 
multiplex descriptor.
>
>
> [Christian] With regards to the example below I'm abit confused. There 
> are two TermA and two TermCs but no Term B? Should Tmux1 include 
> TermA/Stream=2? This would mean StreamID=2 is going to both muxes.
>
> [Javi] I hope the new picture has clarified these issues
[CNG] A little, I understand the termination aspect. I'm still not sure 
about the streams. I don't understand how you can have multiple H.248 
streams for the circuit termination TermA and TermB? With what 
information element (i.e. property) do you assign the SAPI and TEI to a 
Stream? What properties distinguish the Nx64K termination from a HDLCW1 one?
>
>
> [Christian] I'm not 100% sure what you're trying to do but if you're 
> only using a single Termination to represent each D-channel and a 
> single Termination for the HDLCPW it seems to me that you don't need a 
> mux termination and that it may be sufficient to simply use a property 
> to assign TEIs to Streams (or Terminations).
>
> [Javi] Each D-channel has several streams and I need to direct them to 
> different multiplex terminations.

[CNG] I think you're trying to solve this at a different level than what 
it should be. The multiplex descriptor describe the multiplex of 
terminations used to make up a stream. It doesn't describe what's 
happening at a stream level itself. We have the Stream Descriptor with 
associated (Local, Remote, LocalControl descriptors) to do this.


>
>
>
> Regards,
>
> Javi Muñoz
>
>
> El 20/10/2011 11:12, Christian Groves escribió:
>> Hello Javi,
>>
>> Did you see my email on the 18/10 which discusses this? Even with the 
>> clarification of the Terminations there's some questions.
>>
>> Regards, Christian
>>
>> On 20/10/2011 7:38 PM, Javi Muñoz wrote:
>>> Does MeGaCo support the next contexts?:
>>>
>>>
>>>   
>>> Tmux1=Mux(1x64K(TermA/StreamID=1,TermA/StreamID=2,TermB/StreamID=1)) 
>>> -- * -- TermC (HDLCPW1)
>>>                                     |
>>> TermA (ISDN D-Channel, UNI p)       |
>>>    StreamID=1 (SAPI 16, TEI r)------|
>>>    StreamID=2 (SAPI 16, TEI s)------|
>>>                                     |
>>> TermB (ISDN D-Channel, UNI q)       |
>>>    StreamID=1 (SAPI 16, TEI r)------|
>>>    StreamID=2 (SAPI 16, TEI s)------------|
>>>    StreamID=3 (SAPI 16, TEI t)------------|
>>>                                           |
>>>                     
>>> Tmux2=Mux(1x64K(TermB/StreamID=2,TermB/StreamID=3) -- * -- TermD 
>>> (HDLCPW2)
>>>
>>>
>>> where:
>>>
>>> (a) Every multiplex termination is multiplexing Streams from 
>>> different ISDN terminations, and only any Streams of each termination.
>>>
>>> (b) The result of the multiplexion must be a flow of "64 kbps".
>>>
>>> Javi Muñoz
>>> _______________________________________________
>>> Megaco mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>> _______________________________________________
>> Megaco mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/megaco
>>
>
>