asterisk users - Oct 2005 - gotta be a dumb question...

...but I'm gonna ask it anyway, because I can't figger it out...

Every call that is bridged in my * system begins with a console message 
like this one...
 
-- Attempting native bridge of SIP/215-b09e and SIP/259412-5967

Now, I've got canreinvite=no in every sip definition, but it happens anyway.

Furthermore, every keypress of '*' during a call causes the message to 
be emitted again.  It wouldn't bother me so much except that this is 
apparently causing the keystroke to be swallowed, thus disabling other 
features (*1, *2...).

Clues, please?

On Sunday 30 October 2005 09:44, Bill Michaelson wrote:
> -- Attempting native bridge of SIP/215-b09e and SIP/259412-5967
>
> Now, I've got canreinvite=no in every sip definition, but it happens
> anyway.
That has nothing to do with reinvites.

In Asterisk terms, a native bridge between two channels is the lowest-latency 
connection between those channels without dropping out of the loop entirely.  
Essentially a native bridge just reads voice frames from one and transmits 
them to the other.  There is no codec translation or any other goodness going 
on.

When you hit a DTMF digit (you must be using inband DTMF here I think), the 
native bridge must be dropped because Asterisk needs to prepare to do 
something with the DTMF (transfer, etc.) -- when Asterisk has determined that 
it doesn't need to do anything special, it sets up the native bridge again
to
minimize the latency once again.

The fact that your * is getting "swallowed" tells me that you are
using * in
features.conf to denote special keypresses to Asterisk.  In Dial() you likely 
have the 't' or 'T' flags set, which causes Asterisk to
"think" that those
DTMF digits are for it, not for the other side.  Either edit features.conf, 
remove the 't' or 'T' flags from the Dial() command or rethink
your strategy.

I hope this is an acceptable answer, and I certainly hope it's accurate. 
It's
my understanding of the system anyway.  :-)  If you prefer not to have these 
types of messages, you need to turn DOWN the verbosity level.

-A.