Re: Example of MeGaco messages for Multiplex terminations

Hello Javi,

There's no means via the multiplex descriptor to indicate StreamIDs in 
addition to the TerminationID. The multiplex descriptor can only have 
TerminationIDs. 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.

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.

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).

Regards, Christian

On 17/10/2011 10:58 PM, Javi Muñoz wrote:
> Albrecht, Tom, Claudio and Christian,
>
> The proposed scenario was just an example with the intention of asking 
> about the syntax for creating multiplex terminations and mapping 
> StreamIDs.
>
> The real scenario that I need to solve is the next one, related to 
> convey ISDN D-channel SAPI 16 flows on HDLCPW pseudowires:
>
>   Tmux1=Mux(1x64K(TermA/StreamID=1,TermA/StreamID=2,TermB/StreamID=1)) 
> -- * -- TermC (HDLCPW1)
>                                     |
> TermA (D-Channel, UNI p)            |
>    StreamID=1 (SAPI 16, TEI r)      |
>    StreamID=2 (SAPI 16, TEI s)      |
>                                     |
> TermA (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) 
> -- * -- TermC (HDLCPW1)
>
>
> Every HDLCPW may convey SAPI 16 flows from different channels D (so, 
> the Mux termination has Streams from different terminations). I do not 
> know if these multiplex terminations are possible and, if so, how to 
> define them in a MeGaCo message (how to define "TermA/StreamID=1" in 
> the Mux descriptor).
>
> Regards,
>
> Javi
>
>
>
>
> El 16/10/2011 21:13, Tom Taylor escribió:
>> Start with H.248.1v3/clause 6.2. That should give you some idea of 
>> how to construct the syntax. Details for the MUX descriptor are given 
>> in clause 7.1.3. I can put the whole picture together for you if you 
>> have trouble, but I should warn you that my views differ from those 
>> published as H.248.20.
>>
>> On 14/10/2011 6:29 AM, Javi Muñoz wrote:
>>> Hi,
>>>
>>> I have read that a multiplexing termination hides all of the
>>> terminations it contains from the rest of the context, so the streamIDs
>>> of the streams flowing between the contained terminations and the
>>> multiplexing termination are local rather than global in scope.
>>>
>>> If e have the following situation:
>>>
>>> Context interior ---->
>>> _________ _________
>>> Data stream | H.226 | | H.223 | Audio stream
>>> Ckt 1 ..............| "MUX" | | MUX | .................
>>> . . . | term | Data stream | term |
>>> Data stream | | ................| | Video stream
>>> Ckt n ..............| | | | .................
>>> | | | |
>>> --------- ---------
>>>
>>> How we know that the stream between the H.226 and H.223 multiplexing
>>> terminations is a data stream, while the streams passing from the H.223
>>> termination to the rest of the context are audio and video?. I think we
>>> need an explicit description of the exterior-side and context-side
>>> streams supported by each multiplex somewhere within our Megaco/H.248
>>> documentation but, how may it be indicated in a MeGaCo meesage?
>>>
>>> Also, if we want to use separate RTP terminations for audio and 
>>> video, I
>>> need to be able to tell that mux stream 1 shall be mapped to RTP
>>> termination T3, and stream 2 into RTP termination T4. How may it be
>>> indicated?
>>>
>>>
>>> In summary, may someone propose the full MeGaCo messages to create this
>>> scenario with multiplex terminations?
>>>
>>> _______________________________________________
>>> Megaco mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/megaco
>>>
>>>
>>
>
>