[asterisk-dev] asterisk sending connects when it shouldn't

[Simone Cittadini]

Eric "ManxPower" Wieling ha scritto:

> Playback, Background, and most any function that sends audio to the 
> caller will issue an Answer first unless you tell it not to.  (see 
> show application)
>
There is no Playback, Background or such, only a Dial to an IAX 
registered asterisk client which then dials a SIP connected GSM gateway, 
and...

> Paul Cadach wrote:
>
>>
>> Probably it's a behaviour of function executed by AGI script.
>>
... the dial isn't done in the agi, the agi just sets the correct 
argument to dial and pass it to asterisk.

and in response to Matthew Fredrickson :

 >Essentially, that's what an "answer" is, it's a CONNECT.  If the 
remote  end sends the CONNECT message, it's counted as a billable call.  
Not a  >whole lot you can do about that unless you want to complain to 
the  cellular provider.

The provider isn't sending a CONNECT, if you look at the isdn trace in 
my original post you see it's sending one Information message for every 
"char" of the dialed number, you also see that the sip portion of a call 
is different between an human answered (billable) call and a provider 
answered (not billed information message) one, with the latter 
immediatly sending audio after a 200 message instead of  ringing the 
channel with a 186 while waiting for the called to answer.

But  IAX then just ANSWER the call and this seems to be translated to  a 
CONNECT on the PRI, so my question is if we have a subclass of the type 
CONTROL which translates to a ISDN Information, or are we stucked with 
this behaviour ?