Does sipxBridge attempt to generate in-audio DTMF tones? If the outside ITSP
claims it won't support RFC2833 RTP telephony event messages and the inside
session (with the phone) has negotiated the RFC2833 inband event style DTMF
what's supposed to happen?
This morning outbound calls via voip.ms to two different conference bridges are
very difficult, DTMF digits being repeated or ignored on many calls. Inside my
network I see the usual inband telephony events (101), I'm wondering if there's
any way the SBC could be responsible for this (I haven't tried tcpdumping the
outside, I was hoping someone here would know OTOH before setting up that test).
Environment: Polycom 650 3.2.2 -> sipxecs SVN 017896 -> voip.ms trunk (uLaw) ->
... -> 305-848-8888 ("Magic Jack" conference service, I don't expect this to
work often) or 719-387-5556 (paid for conference service).
What happens: after connect you try to dial a conference code and with the
'magic jack' thing it misses most of the DTMF; with the paid for service DTMF
gets duplicated (I enter 123 and it hears 112233).
If you call enough times you end up with a connection that works fine, so I'm
leaning toward this being a problem at voip.ms (and have opened a ticket
there), mostly I'm interested in how fancy sipxbridge is and if it might be
trying to make real audio DTMF from inband RFC2833 messages.
-Eric
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
