Merged revisions 290648 via svnmerge from
authorDavid Vossel <dvossel@digium.com>
Wed, 6 Oct 2010 21:09:14 +0000 (21:09 +0000)
committerDavid Vossel <dvossel@digium.com>
Wed, 6 Oct 2010 21:09:14 +0000 (21:09 +0000)
commit3a986a75c1ce08e2ff0bcea20d42a213db934391
treec63b8da4f0c2cb079c4c9a7860ac6113955acf01
parent0e8c87d9b0c595a3ddc3fec01a4f36e3d6002d8e
Merged revisions 290648 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8

........
  r290648 | dvossel | 2010-10-06 16:08:19 -0500 (Wed, 06 Oct 2010) | 12 lines

  Fixes gtalk outbound DTMF to work properly.

  Outbound DTMF with gtalk needs to be done within the RTP stream.  I discovered
  this after investigating a packet capture from the gmail client.  Instead of
  performing jingle signaling DTMF, the gtalk servers expect all DTMF to arrive
  on the RTP stream using RFC2833 way of doing things.  Chan_gtalk also had an issue
  with negotiating RTP payload type 106 for the telephony-event and then sending
  DTMF as payload 101.  This has been resolved by always negotiating 101 as the payload
  type like we do everywhere else.  With this patch, incoming google voice calls forwarded
  to Asterisk via gtalk work.
........

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@290649 65c4cc65-6c06-0410-ace0-fbb531ad65f3
channels/chan_gtalk.c