Subject: Re: [Megaco] Generic announcement package Rules (h.248.7)

From: Christian Groves <[email-masked]>
Date: Fri, 14 Oct 2005 11:00:49 +1000

Hello Jerry,

Please see below.

Regards, Christian

Kamitses, Jerry wrote:

>During interop testing some confusion has arisen regarding how "flexible" 
>the an/apf is intended to be. 
>
>As defined this signal supports the parameter "an" to specify the desired 
>announcement. Is only one instance of this parameter allowed per apf signal?
>
>  
>
[CHG] You can only have one instance of a parameter eg. "an" if it 
occurs twice you will get error code 456.

>If the MGC wants to string together a sequence of announcements to play 
>in succession is it valid to use a comma separated list of "an" parameters,
>using a signal descriptor such as ... 
>	signals {an/apf{an=600,an=911}}
>  
>
[CHG] See above comment.

>Does h.248.7 somehow preclude multiple instances of the "an" parameter 
>(and if so shouldn't a specification actually make this point clearly?)
>
>  
>
[CHG] Yes H.248.7 is sketchy on this as it states "enumeration of 
announcements". It the "of announcements" which leads to the confusion. 
Enumeration is a single value unless parameter type "sub-list of 
Enumeration" is used. I believe the original intention was a single 
value (you can check pl-35 from Feb 2000).

>The syntax 
>	signals {an/apf{an=600},an/apf{an=911}}
>would not have this effect since in this case the two signals should play 
>concurrently.
>
>Must the sequence of an/apf signals be encapsulated in a signal list signal?
>
>  
>
[CHG] Using a signal list would be the best way to play a list of 
announcements.

>_______________________________________________
>Megaco mailing list
>[email-masked]
>https://www1.ietf.org/mailman/listinfo/megaco
>
>
>  
>

_______________________________________________
Megaco mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/megaco