[Freeswitch-users] Hint for DTMF handling in sofia.c

[Helmut Kuper]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Mike,

I guess the workaround refers to INFO messages with "dtmf" mime type
instead of "dtmf-relay"?

With the actual trunk (11090) it works.

DTMF event F is still converted to zero (0). Im not sure if this event
will ever transmitted via INFO.

If you use FS switch_utils function "SWITCH_DECLARE(unsigned char)
switch_char_to_rfc2833(char key)" instead of the big if-statement
(checking for *,#,A,...) befor calling "switch_rfc2833_to_char()"
function you can clean up the code a bit and handle all rfc2388 DTMF events.

The INFO message my Snom and AVM phones send, looks like this:

recv 506 bytes from udp/[85.16.245.220]:1024 at 14:59:40.229120:
   ------------------------------------------------------------------------
   INFO sip:mod_sofia at 85.16.246.6:5060;transport=udp SIP/2.0
   Via: SIP/2.0/UDP 85.16.245.220:1024;branch=z9hG4bK-0a38f681korf;rport
   From: "HK at FreeSWITCH" <sip:2709 at 85.16.246.6>;tag=v0fmpqh4nz
   To: <sip:xxxxxxxx at xxxxxxx;user=phone>;tag=m0NcZ8BDZ8pcD
   Call-ID: 3c26a924030f-p23y096nom3i
   CSeq: 3 INFO
   Max-Forwards: 70
   Contact: <sip:2709 at 85.16.245.220:1024;line=3tzvc1jp>;reg-id=1
   User-Agent: snom370/7.3.12
   Content-Type: application/dtmf-relay
   Content-Length: 27

   Signal=*
   Duration=160
   ------------------------------------------------------------------------

regards
Helmut

Am 08.01.2009 15:09, schrieb Michael Jerris:
> This workaround was added to address phones that specifically send  
> info dtmf incorrectly.  Do you have a specific device that is not  
> working with 1.0.2?  If so, can you please show the exact packet it is  
> sending.
> 
> Mike
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAklmHIoACgkQ4tZeNddg3dzR9gCghxxkOUeYyBEq82BfWsdZ/IWy
zMUAnRZ+pf1FmdipqwUZ8YYqbvNscd2q
=TzvT
-----END PGP SIGNATURE-----