Re: Multiple Streams and mutiplex terminations

Hello Javi,

I think you may need a different top level for the Physical and 
Ephemeral terminations to avoid any unwanted protocol problems..
i.e. What would happen if you do a Subtract(ISDN/Term/*)? The MG would 
try to subtract Termination in the NULL context which is not allowed.

Regards, Christian

On 14/11/2011 8:57 PM, Javi Muñoz wrote:
> Hello Christian,
>>>>> ISDNTerm/BA17/D [null context]
>>>>>
>>>>> ISDNTerm/BA17/D/SAPI16-TEI1 --- * --- HDLCPW1/BA17/D/SAPI16-TEI1
>>>>>
>>>>> ISDNTerm/BA17/D/SAPI16-TEI6 --- * --- HDLCPW2/BA17/D/SAPI16-TEI6
>> [CNG] I think there is only ever one physical termination. There can 
>> be empheral terminations to describe the connection topology. 
>> Something like the above would be possible 
>
> I agree.
>
>> although you would need to work on your naming conventions to ensure 
>> they are valid.
>
> I think this naming convention is valid:
>
> * Physical termination:     ISDNTerm/BA17/D
>
> * Ephemeral terminations: ISDNTerm/BA17/D/SAPI16/TEI23
>
>
> Do you think it has any problem?
>
> Regards,
>
> Javi
> _______________________________________________
> Megaco mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/megaco
>