Re: Multiple Streams and mutiplex terminations

Hello Javi,

H.248 allows wildcarding at different levels of a TerminationID. So you 
could use a subtract like below. However its not unambigious, would 
../D/* still match ISDNTerm/*/D? As I've mentioned previously I think 
its good practise to separate ephemeral and physical terminations at the 
highest level in the heirarchy. 3GPP do this in their naming scheme, ie. 
see TS 29.232 etc.

Regards, Christian

On 15/11/2011 9:14 PM, Javi Muñoz wrote:
> Hello Christian,
>>
>> 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.
>
> May we use  Subtract(ISDNTerm/*/D/*)  ?
>
> Regards,
>
> Javi
>
>>
>> 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
>>>
>> _______________________________________________
>> Megaco mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/megaco
>>
>
>