Re: [Megaco] A question about DTMF erasion

If you don't have RFC2833, your alternative is for the sending gateway
to upspeed to G.711 when it detects tones.

shicao@harbournetworks.com wrote:
> RFC2833 is truely the best way to transmite digits between gateways right 
> now. But what should we do when both gateway don't support RFC2833 .One 
> solution is  MGC relay the digits from one gateway to another by 
> signaling. In this case, to avoid repeated digits(one from media stream, 
> the other from signaling),I think MG should automatically ERASE the digit 
> signal from the sending media stream. 
> examples of application:
> (1)   PHONE-PSTN-MG-----MGC------MG-PSTN-PHONE
>       PHONE-MG-----MGC------MG-PSTN-PHONE
> (2)   PHONE-MG-----MGC------MG-PBX-PHONE
> (3)   PHONE-MG-----MGC------MG-Service_Server
> 
> I Can NOT agree with Kevin on the opinion that MG SHOULD NOT alter the 
> media stream in anyway, because RFC2833 requests erase DTMF tones when 
> sending RFC2833 Events.
> 
> Bypass I find a similar question has been dicussed in SIP forum two years 
> ago. Is there any one who knows the final result?
>  
> 
> 
> 
> 
> "Tom-PT Taylor" <taylor@nortel.com>
> 2005-12-07 00:31
> 
>  
>         收件人：        "Kamitses, Jerry" <jkamitses@sonusnet.com>
>         抄送：  "Kevin Boyle" <kboyle@nortel.com>, shicao@harbournetworks.com, 
> megaco@ietf.org
>         主题：  Re: [Megaco] A question about DTMF erasion
> 
> 
> Gateway to gateway, the technical answer is RFC 2833, period.  RFC 2833, 
> particularly as rewritten (draft-ietf-avt-rfc2833bis-12.txt, just passed 
> WGLC) has advice on what to do with the audio signal.
> 
> In other applications you should view the SIP application framework:
> 
> draft-ietf-sipping-app-interaction-framework-05.txt
> 
> 
> 
...

_______________________________________________
Megaco mailing list
Megaco@ietf.org
https://www1.ietf.org/mailman/listinfo/megaco