Shared Line Appearance in Asterisk 1.4.13 Newbie Help

Hi,

I’m desperately trying to get SLA working on my 1.4.13 system. I’ve read the SLA.pdf as well as many posts on the net and I must be doing something wrong. Here’s what’s going on:

Asterisk 1.4.13
Polycom IP 601 phone.

I have two PSTN trunks on zap channels that I want to have appear on the Polycom as trunk appearances so all I have to do is press the line button and be connected to that trunk where I can then dial my number. First trunk is SxS, second is Vonage. I’ve configured my zap channels (zap/21 and zap/22) for this service.

I’ve configured my sla.conf as follows:

[general]
attemptcallerid=no

[SxS]
type=trunk
device=Zap/21
autocontext=SxS

[Vonage]
type=trunk
device=Zap/22
autocontext=Vonage

station
type=station
trunk=SxS
trunk=Vonage
autocontext=sla_stations

station1
device=SIP/Station1

Zapata.conf:

context=SxS ;
txgain = +0.0 ;
rxgain = +0.0 ;
callerid=asreceived
group= 5
signalling=fxs_ls
Channel=>21
;
context=Vonage ;
txgain = +0.0 ;
rxgain = +0.0 ;
callerid=asreceived
group= 6
signalling=fxs_ls
Channel=>22

I’m thinking that either my sip.conf entries or extensions.conf entries are mucked up (or both). In my SIP.conf, each Polycom line appearance is a separate sip definition. The [SxS] sip definition is for line 5 on the Polycom and the [Vonage] definition is for line 6 on that same Polycom.

SIP.conf:

[SxS] ;
maxexpiry=60
allow=ulaw
context=SxS
type=friend
;username=Line5
;password=polycom
host=dynamic
dtmfmode=inband
defaultip=166.77.201.21
progressinband=no
accountcode=SIP_SxS
;
[Vonage] ;
maxexpiry=60
allow=ulaw
context=Vonage
type=friend
;username=Line6
;password=polycom
host=dynamic
dtmfmode=inband
defaultip=166.77.201.21
progressinband=no
accountcode=Vonage

Here’s the portion of the extensions.conf - which I know is mucked up:

[SxS]
exten => s,1,SLATrunk(SxS)

[Vonage]
exten => s,1,SLATrunk(Vonage)

Can someone post what the valid entries for sla.conf, sip.conf, extensions.conf and zapata.conf would look like. I know I’m getting hosed on the sip.conf part and extensions.conf.