[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Megaco] Regarding audio record

Hello,
Actually there's more to it.... The H.248.9 text mentions input stream because a H.248/Megaco stream is bi-directional. Typically the signal is applied at a termination level because the most common case is that there would be only one audio stream. So the MG knows which stream to apply the recording to. In the case a termination has multiple audio streams you can use the "StreamID" parameter associated with the Signal (this is core H.248) to indicate which stream is to be recorded.
In order to capture the incoming stream from all users the signal "direction" parameter is used. Normally the "external" direction is recorded however if "internal" is specific then the MG will record the audio received by the termination from all other terminations in the Context. i.e. the mixed stream. 

Regards, Christian

Tom Taylor wrote:

Hi.

I was the editor of that package years ago.

A Signals Descriptor applies to a specific termination. That means you
can select which party is to be recorded. If you look at the definition of the PlayRecord signal, it says it records the incoming stream from the user. So that is all there is to it. 

Tom Taylor

shalu dhamija wrote:


Hi All,


...


I have a query on advanced audio server recording (aasrec) package.
According to 3GPP 23.333, the functional requirements for the audio record 
states that:


...
“The MRFC shall request the MRFP to start the audio record from one or all 
parties connected in a call/session. If it is to record one party in a
call/session, only the input stream of the party is recorded. If it is to 
record all parties in a Call/session, the mixed stream of all parties is
recorded. “

...
I am unable to understand that how to specify the input stream of the party in a Megaco message. Can anybody illustrate how MRFC tells MRFP about the 
input stream to be recorded? I have not got any parameter in the aasrec
package. In this package, the mandatory parameter in the signals descriptor is the recording identifier (rid) which I think is just the URI (where the 
recording is to be stored).


...>

Thanks and Regards,



Shalu


...
_______________________________________________
Megaco mailing list
Megaco at ietf.org
https://www.ietf.org/mailman/listinfo/megaco