Arkansas Website Design, Fort Smith - page - Comments

Hi Thanks for the info. I

Anonymous — Mon, 08 Sep 2008 06:35:59 -0500

Thanks for the info.
I have installed the patch and asttapi OK.

But I cannot work out what to put in the extensions.conf to notify ASTTAPI. It doesnt make much sense.

My standard context for incoming calls is:

[incoming]
exten=>039012xxxx,1,Dial(SIP/clientphone,30,r)

How do I adapt the required context into the above string?

Got it working

Cygnus — Wed, 23 Jul 2008 12:08:13 -0500

Hi!

This works now for me. Thanks for providing information on Asterisk 1.2 and the corresponding patched file.

One should note that if you use a different line name and user channel the above given extensions do not work.

The dial line for incoming calls should then read:

exten => s,n,Dial(${ARG1},20,rtM(tapi^${UNIQUEID}|${ARG2}))

when the macro is called in the following way:Macro(stdexten,SIP/sipuserchannel,lineid)

Greetings Torge

Feedback

Cygnus — Wed, 23 Jul 2008 11:17:34 -0500

Hi!

I have followed your configuration using a Outlook 2007 client with Identapro on Windows XP. I can initiate outgoing calls, but incoming calls are not shown in the identapro debug log.

I have verified that asterisk is sending out the incoming phone event through the manager interface on port 5038. But on the astapi side i do not see any incoming call. Any ideas? I can send you a tcpdump on port 5038 of the incoming call.

Greetings Torge