Re: xAP Asterisk integration

[James <james@xxxxxxx>]

Kevin Hawkins wrote:

>Maybe partially - needs a call ended message though too so it knows the
>call has ended. Try it and see :-) IIRC James supports both
CID.incoming
>and Meteor CID schema as long as they arrive in the correct order.
>Indeed xAPTel can send both.
>
>
Yes, for telephone calls switchboard can use both schemas. The only
issue is, as Kevin mentioned, the order. Cid.incoming is a one shot
schema, nothings is tracked just looked up and logged. The meteor schema
updates throughout the calls and switchboard uses all of these. If a cid
device sends both schemas then the meteor once must be sent first. If
the cid.incoming is first then all logging and events will be duplicated
as Switchboard will think there are two calls not one. If a meteor call
is in progress then any other cid.incoming message from that line is
sent then it will be ignored. There are lots of advantages to using
both, especially when dealing with simple display devices as
cid.incoming is far simpler to track.
One issue that i don't think was raised was the use of correct
addressing for the xAP messages. It's important that each line, virtual
or real, uses a different xAP subaddress. So if your asterisk had 3 pots
lines an a maximum of 2 concurrent voip lines you should have xAP
sources of:
ove.asterisk.server:pots.1
ove.asterisk.server:pots.2
ove.asterisk.server:pots.3
ove.asterisk.server:voip:1
ove.asterisk.server:voip:2

this gives the listening applications a good basis for tracking calls.
If they all came form ove.asterisk.server it jsut wouldn't work!!


Below is a post from the dev list a little while a go detailing the
schemas that Switchboard uses:

Switchboard listens out for quite a few schemas but no apps really
register with Switchboad. Switchboard simply build lists of information
sources as it hears them. It doesn't need to know there is a modem
called a.b.c that may present caller id info, the first time a.b.c sends
a caller id message Switchboard will use it. Internally Switchboard uses
an array of lines and assigns any received message to a item in the
array based on the xAP source. The instant messenger side of Switchboard
works like this too. As, i'm guessing, you don't have a xAP enabled IM
client then Switchboard has a blank array of IM so that part of the app
is disabled. As soon as it hears an IM message it will fire up and start
displaying it. (xAPTel is also a skype connector, btw). So the list of
schemas used are

Incoming and Outgoing calls
cid.incoming
http://www.xapautomation.org/modules.php?name=Sections&op=viewarticle&artid=9
cid.meteor
http://www.xapautomation.org/modules.php?name=Sections&op=viewarticle&artid=9

Line status/monitoring/dialler support
cti.info/event
http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=49

IM messenger support
messenger.event/info http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=51


xAP Intranet links
web.service http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=48

Outlook support
outlook.contact

Switchboard sends:
message.display
http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=9
xAP-Osd.slimp3
http://www.xapautomation.org/modules.php?name=Sections&op=viewarticle&artid=11
tts.speak  http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=17
cid.lookup  http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=47
cti.cmd http://www.mi4.biz/modules.php?name=Content&pa=showpage&pid=50
and with raw support, any schema really!

hth

James