[asterisk-users] Continued TAPI Trouble

[Steve Davies]

2008/6/21 Gert-Jan de Boer <boerg at nosco-ict.nl>:
> Hi All,
>
> I am still working on an TAPI solution for my customer.
> They are trying to connect Asterisk to Navision.
>
> I am using the Activa TSP and an TAPI connector for Navision.
> When a customer calls I use the following rule:
>
> exten => s,n,Dial(LOCAL/11&LOCAL/991013,25,tTr)
>
> 991013 is an extension that waits 10 seconds and then dials the number 13.
>
> This results in a couple of TAPI lines in the logfile:
>
[snip]
>
>
> SUPER
> As you can see all the lines are logged as connected but this is not
> actually the case, in this test only the number 11 has picked up the call.
>
> The 11 and 13 extension look like this:
>
> exten => 11,1,Macro(bel)
>
[snip]
>
> Could someone shine a light on this?

The activa TSP forum would probably be a better place for getting
answers on this, as none of the above gives any hint of a problem in
Asterisk.

I am not trying to be difficult, but the logging you provided is from
a TAPI application that is removed from asterisk by way of a TAPI TSP,
which is removed from Asterisk by way of the Asterisk Manager
interface!

...also, your call is being indirected through a Local/ channel, which
will make is virtually impossible for ActivaTSP to trace the call
status because it is being indirectly dialled. Activa may not
recognise the TAPI control information because it will be output
against the Local/11 or Local/13 channel, and not the originally
allocated channel for the TAPI dial.

Don;t know if that helps at-all.
Steve