Hi
Been lurking on the user list for a while but I have some what of an
immediate requirement and I'm wondering if you can suggest the best
solution (if mines a rubbish idea)
I have been testing Asterisk as a bolt on to our Mitel 3300.. its been
doing some softphones for users abroad, etc a
On Wed, 2 Apr 2008, Trixter aka Bret McDanel wrote:
> dtmf in asterisk (rfc2833) violates the rfc. There are many switches
> that usually are only "big carrier types" that do not properly deal with
> what asterisk sends. I gave oej specifics as he was doing something
> relating to a filed bug on
On Wed, 2008-04-02 at 20:15 -0400, Gregory Boehnlein wrote:
> > > This was only true with Asterisk up to and including 1.2; 1.4 and
> > beyond
> > > send proper RFC2833 (now RFC4833) DTMF telephone-events and
> > > interoperability has been dramatically improved.
> >
> > my patch was for 1.4 so t
> > This was only true with Asterisk up to and including 1.2; 1.4 and
> beyond
> > send proper RFC2833 (now RFC4833) DTMF telephone-events and
> > interoperability has been dramatically improved.
>
> my patch was for 1.4 so that is not true.
What specifically does the 1.4 DTMF implementation brea
On Wed, 2008-04-02 at 16:45 -0500, Kevin P. Fleming wrote:
> Trixter aka Bret McDanel wrote:
> > dtmf in asterisk (rfc2833) violates the rfc. There are many switches
> > that usually are only "big carrier types" that do not properly deal with
> > what asterisk sends. I gave oej specifics as he w
On Wed, 2008-04-02 at 16:45 -0500, Kevin P. Fleming wrote:
> Trixter aka Bret McDanel wrote:
> > dtmf in asterisk (rfc2833) violates the rfc. There are many switches
> > that usually are only "big carrier types" that do not properly deal with
> > what asterisk sends. I gave oej specifics as he w
Trixter aka Bret McDanel wrote:
> dtmf in asterisk (rfc2833) violates the rfc. There are many switches
> that usually are only "big carrier types" that do not properly deal with
> what asterisk sends. I gave oej specifics as he was doing something
> relating to a filed bug on this issue. I even
dtmf in asterisk (rfc2833) violates the rfc. There are many switches
that usually are only "big carrier types" that do not properly deal with
what asterisk sends. I gave oej specifics as he was doing something
relating to a filed bug on this issue. I even wrote a patch, but until
asterisk is no
The simplest solution is to just use a provider that implements this
properly. I know our providers (big international networks) all
support this with no problem, if you are seeing many different types of
DTMF you likely have a very broken reseller in the path...
John
-Original Message
On Wed, 2008-04-02 at 21:33 +0800, Si Tai Fan wrote:
> Hi Dave
>
> It's not that simple. All I need for now is to prove that the Asterisk
> manager interface can show the data messages that comes through the
> SIP trunk from the provider's end. Since the provider is not in the
> picture, for now
Hi Dave
It's not that simple. All I need for now is to prove that the Asterisk
manager interface can show the data messages that comes through the SIP
trunk from the provider's end. Since the provider is not in the picture,
for now I only need to somehow simulate this so that the customer coul
11 matches
Mail list logo
