Topic: SAIL 2.3.1-4 + SPA3102 - Confused

[ntblade]

Hi all,
Fresh installation of SAIL 2.3.1-4 on SME 7.4

Code: [Select]

[root@gromit ~]# uname -r
2.6.9-78.0.22.EL
[root@gromit ~]# rpm -qa | grep -i dahdi
dahdi-linux-2.1.0.4-60.el4
dahdi-tools-2.1.0.2-59.el4
dahdi-linux-kmdl-2.6.9-78.0.22.EL-2.1.0.4-60.el4
[root@gromit ~]# rpm -q libpri
libpri-1.4.9-22.el4
[root@gromit ~]# rpm -q asterisk
asterisk-1.4.23.1-72.el4
[root@gromit ~]# rpm -q asterisk-addons
asterisk-addons-1.4.7-21.el4
[root@gromit ~]# rpm -q sox
sox-12.17.7-3
[root@gromit ~]# rpm -q sail
sail-2.3.1-4
[root@gromit ~]#

I got the kernel dependent stuff from atrpms.
Now, my account with Voiptalk works fine for incoming / outgoing calls but I just can't get my PSTN line working fully.  I have:
PSTN <--> SPA3102 <--> SAIL
I managed to create an extension via the adoption method for my SPA and provisioning works so that the internal extensions can call each other (the SPA3102 has an analogue phone connected).

However, I cannot for the life of me figure out how to create a PSTN trunk.  The SPA3102 appears in the drop down list in the create trunks panel but I don't know what to do from there.

Do I still have to configure via the web interface of the SPA or is the config entirely provisioned?

Any docs for this at all?

Oh, is this still a good way to use PSTN?  (compred with x100p clones etc)

Thanks,

Norrie

[Tib]

ntblade,

Here is a link that may help

http://sarkpbx.com/twiki/bin/view/Main/DocChapter093

http://sarkpbx.com/twiki/bin/view/Main/DocChapter253

Just read through the docs pages to find more details.

I'm using an SP3000 ... not much diff I don't think

Regards,

Tib

[ntblade]

Thanks for the reply,
It seems the docs are out of date as when a new trunk is added in 2.3.1-4, and SPA3102 is selected we are presented with this:

I tried entering the PSTN number and mac address but this doesn't work.

Any ideas?

Thanks

[SARK devs]

I have a feeling there is a BIG greenie here somewhere but I'm going to have to look at the code.  These things happen from time to time when we make changes to the extension or trunk processing.  We just don't have the time or the people to test that every device still generates OK.  This looks like a case in point.

For now, if you need to get it working in a hurry, you can just generate the trunk (without the MAC address) and provision the unit manually.  The trunk creates OK, but the MAC Address gubbins looks to be missing.

Also...

Oh, is this still a good way to use PSTN?  (compred with x100p clones etc)

If it works on your line then it is fine.  These little Sipura (now Cisco/Linksys) 3000 and 3102 units have a wide range of tuning options (unlike the X100P or TDMx) which means you should, in theory, be able to achieve a much better match with your local PPT signalling requirements. We use a lot of Spa2102 and PAP2 FXS units in the field to operate analogue devices like FAX, remote door openers, external bells and the like and they are indispensible for that. 

Best

S

s   

[SARK devs]

OK - we have a fix for you.  Turns out it is a database error and not a coding error.

Code: [Select]

db selintra setprop SPA-3000FXO carriertype Spa3xxx
db selintra-work setprop SPA-3000FXO carriertype Spa3xxx
db selintra setprop SPA-3102FXO carriertype Spa3xxx
db selintra-work setprop SPA-3102FXO carriertype Spa3xxx

See how you get on with that and let us know so we can correct the DB in the next release

Best

S

[ntblade]

Thanks Tib, Selintra,

Deleted and recreated the trunk following the docs and it seems to be fine although I did this remotely so I'll check when I get back to the office.

Let me know if you want some testing help when the greenie's squashed.

Norrie

[SARK devs]

The db change is the squash Norrie.

Let me know if it works OK for you.

Best

Jeff

[ntblade]

Sorry, Didn't notice you'd provided the fix before I'd tried manually.
Deleted extension,
entered the db commands above
Recreated the extension, entered a name, PSTN number and mac address, clicked save and got:

Code: [Select]

Operation status report - Trunk Name NOT Entered!!
??

Norrie

Edit:  The db changes don't survive a signal-event post-ugrade; reboot either.

[SARK devs]

Ok - I'll take a look

Seemed OK here but we may ahve some noise from other releases on the system I was using.

re DB changes - no they won't survive a post-upgrade event because our part of the DB gets rebuilt when you do that.  You'll get a full hard-fix in the next release.  In the meantime if you do a post-upgrade you'll need to redo the update.

[ntblade]

Back in the office.  Incoming OK, having checked and re-checked the installation instructionsoutgoing not working:

Code: [Select]

    -- Executing [dialednumber@internal:1] AGI("SIP/5000-09133770", "selintra|OutCluster|dialednumber") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [dialednumber@default:1] AGI("SIP/5000-09133770", "selintra|OutRoute|PSTN") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script Executing Application: (Dial) Options: (SIP/dialednumber@mypstn||)
    -- Called dialednumber@mypstn
    -- SIP/mypstn-09168bf0 is circuit-busy
  == Everyone is busy/congested at this time (1:0/1/0)
    -- AGI Script Executing Application: (Background) Options: (were-sorry)
    -- <SIP/5000-09133770> Playing 'were-sorry' (language 'en')
    -- AGI Script Executing Application: (Background) Options: (call-cannot-complete)
    -- <SIP/5000-09133770> Playing 'call-cannot-complete' (language 'en')
  == Spawn extension (default, dialednumber, 1) exited non-zero on 'SIP/5000-09133770'
    -- Executing [h@default:1] Hangup("SIP/5000-09133770", "") in new stack
  == Spawn extension (default, h, 1) exited non-zero on 'SIP/5000-09133770'
...

Norrie

[SARK devs]

I'm assuming you have substituted the string dialednumber for the actual number?

[SARK devs]

After looking at the code for this Norrie, I've come to the conclusion that provisioning for the spa3K is buggered. 

Sad thing is, I can even remember when we buggered it (and it was a while ago, so that tells you how many folk are attempting use spa3Ks with SAIL - not very many).  To fix it, we are going to need an spa3xxx for testing and the last one we had committed suicide a couple of months ago. I'll request a 3102 from the distributor (fortunately, they also distribute SARK so I should be able to get a unit pretty quickly) and we'll revisit it. 

For now, you will have to create separate trunk and extension entries for the device (I would suggest you use the "General SIP" trunk template) and provision it manually. 

Best

S

[ntblade]

OK, thanks,
Have to go out first thing but I'll try later and report back.
ATB

Norrie