Re: Selection of media (m=) at MG

"Makaraju, Maridi Raju (Raju)" <[email protected]> Mon, 12 Dec 2011 16:46:45 -0600
Newsgroups gmane.ietf.megaco
Message-ID <31939CE9629A7F46885A9F97CEA9BF577C79C6F9@USNAVSXCHMBSD3.ndc.alcatel-lucent.com>
Javi,

> Raju,
> 
> In addition, [TS 183 002/Clause 7.1.4] indicates that if announcement 
> are remote to MG, "the MGC shall initiate a connection to an external 
> announcement machine (MRF), by
> temporarily adding a termination into the context.".
> 
> I understand that this context should be the same that contains the 
> termination play announcements. For example, in:
> 
> TE <--->  MG <--->  MRF
> 
> 
> MG must ge the announcements from MRF and play them to TE. 
> For that, I 
> understand MGC must create the next contexto in the MG:
> 
> TE <-- [Termination A (codec PCMU)] -- *  -- [Termination B (codec 
> PCMU)] --> MRF
> 
> So, termination B is used to get the announcements, and 
> termination A is 
> used to play them.
> 
> But, if "when a signal (tone/annc) is played on one termination, the 
> termination is temporarily disconnected oneway", then while 
> termination 
> A playing a announcement, it can not continue to receive announcement 
> that continue to get the termination B.
[Raju] In this case where MRF is playing announcement, there is no signal
played either on Termination A or B. MRF sends the announcement RTP bearer
packets to termination B which in turn forwards them to A and then to UE.
Terminations A and B are not aware of the actual contents of the bearer,
it could be a tone, announcement or a some other media.

Regards
raju

> 
> Javi
> 
> 
> El 12/12/2011 12:31, Javi Muñoz escribió:
> > Raju,
> >> In fact, when a signal (tone/annc) is played on one termination 
> >> (signal going outside of the context),
> >> the termination is temporarily "disconnected oneway" (so it won't 
> >> receive any data, but can send) from
> >> the other terminations (as if the termination has "oneway" 
> topology 
> >> to others).
> >>
> >>
> > When a signal is played by the MG, does the MG 
> automatically applied 
> > that "oneway" topology, or it should be explicitly indicated by the 
> > MGC in the configuration of the termination?(it would be on the 
> > Stream, rather than on the termination, since it migth be a 
> > multistream termination)
> >
> > Javi
> >>
> >>> -----Original Message-----
> >>> From: [email protected]
> >>> [mailto:[email protected]] On Behalf Of Javi Muñoz
> >>> Sent: Thursday, December 01, 2011 12:43 PM
> >>> To: [email protected]
> >>> Cc: Bhattacharjee, Arindam (Arindam)
> >>> Subject: Re: [Megaco] Selection of media (m=) at MG
> >>>
> >>> Arindam,
> >>>
> >>>> You can use another option: have reserve value on and use
> >>> both g711 and Clearmode on both remote and local SDP and MG
> >>> will send in g711 only because that has higher preference
> >>> when G711 appears before CLearMode codec in the list as follows:
> >>>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
> >>>>    a=rtpmap:<PT_dinámico>    CLEARMODE/8000
> >>> When the Remote descriptor has several audio codecs in 
> the line "m=":
> >>>
> >>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
> >>>
> >>>
> >>> I understand that:
> >>>
> >>> 1º First codec in the line is used if it is possible.
> >>>
> >>> 2º In case that codec may not be used (for an error, for
> >>> example), the
> >>> second codec would be tried (I understand this is the 
> reaseon why the
> >>> Remote descriptor may have several audio codecs in the 
> same line "m=).
> >>>
> >>>
> >>> If it is so, and we use:
> >>>
> >>>    m=audio<puerto>    RTP/AVP 0 [8]<PT_dinámico>
> >>>
> >>>
> >>> What would happen if when MG needs to send the tone/ann., the
> >>> codecs "0"
> >>> and "8" may not be used?. MG would try to send the 
> tone/ann. to the
> >>> terminal using CLEARMODE, when terminal is not ready to 
> receive that.
> >>>
> >>> 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
> >
> 
>