Topic: SAIL -414

[SARK devs]

HI

We've put SAIL -414 up onto the download site.  

ftp://81.149.154.14/Pre-Releases/

There are two new features/fixes in this release...

It has an onboard facility to echo tune Digium analogue FXO circuits using fxotune.  Not only will it tune the circuits, it will also auto-load the coefficients at asterisk startup so there's nothing for you to do other than hit the button.   Go into PCI cards and stop the PBX.  If, and only if, SAIL detects any TDM cards on your system, then a new button marked "Echo Tune" will appear.  Er...  press it.  SAIL will run fxotune for you.  It takes four or five minutes to run so be patient.  When it finishes you will be shown a report of what occurred and the coefficients will be listed for you.

Exit the screen and restart the PBX.  Er... that's it.

414 also contains a fix involving a bug in custom apps.  You can now decide which cluster your Capp will be owned by/run for.

414 will ONLY install with smeserver-asterisk-1.2.10-2 so you will have to upgrade to that release.  You can get it at contribs here...

http://mirror.contribs.org/smeserver/contribs/selintra/RPMS/AsteriskForSail-2.1.13/None-ISDN/

Finally, if you are running ISDN then we've done a new set of rpms for you - watch for a post on this.

Regards

Selintra

[sonoracomm]

Hi Selintra,

Thanks again for a new version to test.  I appreciate it very much.

I just installed -414 on two Internet connected machines and did some testing.  One of the machines has a TDM04B (4 FXO) board.

Two questions/issues,

1) this must be a newbie question...what do I have to do to allow key-presses that are not actual IVR menu choices?  For example, I announce "if you know your party's extension, please dial it at any time".  I would like the caller to just be able to enter any valid extension.  Custom app?

2) the new Echo Tune button doesn't seem to work on my server - I get this:

Code: [Select]

Beginning echo tune - loading drivers...

Waiting for udev...
waited 0 seconds for udev
starting zaptel...
Waiting for udev (second phase)...
waited 0 seconds for udev(second phase)

starting tuner task...
Tuning module /dev/zap/1
Failure!
Tuning module /dev/zap/2
Failure!
Tuning module /dev/zap/3
Failure!
Tuning module /dev/zap/4
Done!

In this case, there are only three analog lines in the first three ports - port 4 is empty (disconnected).  Those three ports fail every time, even after a reboot.

Any ideas?

Thanks again,

G

[hervep]

...
414 will ONLY install with smeserver-asterisk-1.2.10-2 so you will have to upgrade to that release.  You can get it at contribs here...

http://mirror.contribs.org/smeserver/contribs/selintra/RPMS/AsteriskForSail-2.1.13/None-ISDN/
...

Hi Selintra,

Just wanted to mention that after upgrade from asterisk 1.2.10-1 to 1.2.10-2, the asterisk was not starting automatically after reboot ... .
After quick check, I saw the service symlink to be missing (S93asterisk ...).
I don't know why ... maybe something previously wrong at my side... ?
If somebody has the same issue : #/bin/ln -s /etc/rc.d/init.d/e-smith-service /etc/rc.d/rc7.d/S93asterisk

Kind regards,

Hervé

[SARK devs]

Hi Herve

Hope you are well.

I don't like the 0 second delays waiting for udev.  It should take a few seconds so I don't think the drivers are loading properly.  

You may want to try running fxotune manually to see what is happening on your machine.  Stop asterisk at the console with 'stop now' and do...

/home/selintra/fxotune -i 4

Let me know what you see.

I'm not sure why the symlink would go missing but I'll have it checked on a test server.

For the IVR - I need to check something on this and I'm not at the office at the moment.  I'll get back to you shortly.

Best

Jeff

[SARK devs]

Hi Herve,

I'm at the ofice now.  I just checked the IVR question.  For a default greeting which just asks for an extension number you can simply reference the greeting directly from the inbound route in the trunk.  You don't need to  create an IVR.    If you want to "mix" key presses and extension numbers you create a greeting that says something like ....  "press 1  for sales, press 2 for enquiries or, if you know the extension of the person you require, press *".

In the * entry on the IVR, reference another greeting which says something like "enter the extension you require".  SAIL will then allow a multi-digit extension to be entered.

Hope I've answered what you asked.

Best

Jeff

[SARK devs]

Hmmmmm

I just a fresh install of 414 on a test server here and this is my output...  (the card fitted to this particular machine is a 22B)

Code: [Select]

Beginning echo tune - loading drivers...


Waiting for udev...
waited 6 seconds for udev
starting zaptel...
Waiting for udev (second phase)...
waited 12 seconds for udev(second phase)

starting tuner task...
Tuning module /dev/zap/1
Failure!
Tuning module /dev/zap/2
Failure!
Tuning module /dev/zap/3
Done!
Tuning module /dev/zap/4
Done!
/dev/zap/5 absent: No such file or directory
/dev/zap/6 absent: No such file or directory
/dev/zap/7 absent: No such file or directory
/dev/zap/8 absent: No such file or directory
....


So it's working fine here.  The two failures are because of the two FXS channels - which is to be expected.

I have found a minor error in the subsequent load and I'll fix that today but I am intrigued as to why your tune isn't working.

Best

Jeff

[ldkeen]

Hey Jeff,
This'll have to be quick - I have to go outside and finish my rain dance. Aussies are in deep trouble at the moment in the cricket.

It has an onboard facility to echo tune Digium analogue FXO circuits using fxotune.

Seems to work OK although I don't know how to read the output:

Code: [Select]

Beginning echo tune - loading drivers...


Waiting for udev...
waited 0 seconds for udev
starting zaptel...
Waiting for udev (second phase)...
waited 0 seconds for udev(second phase)

starting tuner task...
/dev/zap/1 absent: No such device or address
/dev/zap/2 absent: No such device or address
Tuning module /dev/zap/3
Done!
Tuning module /dev/zap/4
Done!
/dev/zap/5 absent: No such file or directory
......
......
/dev/zap/252 absent: No such file or directory
fxotune: successfully set echo coeffecients on FXO modules
Stopping zaptel...
 
Unloading drivers
 
Output from the Echo tune follows...

3=0,0,0,0,0,0,0,0,0
4=0,0,0,0,0,0,0,0,0

Echo tune is complete

also contains a fix involving a bug in custom apps. You can now decide which cluster your Capp will be owned by/run for

I can't see that? I've gone into Custom Apps - then create a new app and all I can see is Context Name, Description and Span (Internal, external, both or neither). Am I looking in the right place?

Just wanted to mention that after upgrade from asterisk 1.2.10-1 to 1.2.10-2, the asterisk was not starting automatically after reboot ... .

I can also confirm that asterisk failed to start after upgrading smeserver-asterisk.
Thanks for the great work.
Lloyd

[sonoracomm]

Well, I think you are right about the udev issue...the devices are not listed in /dev/zap:

Code: [Select]

# ll /dev/zap/
total 0
crw-rw----  1 root root 196, 254 Feb 11 03:55 channel
crw-rw----  1 root root 196,   0 Feb 11 03:55 ctl
crw-rw----  1 root root 196, 255 Feb 11 03:55 pseudo
crw-rw----  1 root root 196, 253 Feb 11 03:55 timer
If I enter this command, it replies instantly:

Code: [Select]

# /home/selintra/fxotune -i -e 4
/dev/zap/1 absent: No such file or directory
/dev/zap/2 absent: No such file or directory
/dev/zap/3 absent: No such file or directory
/dev/zap/4 absent: No such file or directory
fxotune: successfully set echo coeffecients on FXO modules

If I start fxotune with the button in SAIL, I can see that the /dev/zap/1-4 are created properly.  And I see this in /var/log/messages:

Code: [Select]

Feb 11 04:07:04 linus kernel: ACPI: PCI interrupt 0000:04:08.0[A] -> GSI 17 (level, low) -> IRQ 225
Feb 11 04:07:06 linus kernel: Freshmaker version: 71
Feb 11 04:07:06 linus kernel: Freshmaker passed register test
Feb 11 04:07:06 linus kernel: Module 0: Installed -- AUTO FXO (FCC mode)
Feb 11 04:07:06 linus kernel: Module 1: Installed -- AUTO FXO (FCC mode)
Feb 11 04:07:06 linus kernel: Module 2: Installed -- AUTO FXO (FCC mode)
Feb 11 04:07:06 linus kernel: Module 3: Installed -- AUTO FXO (FCC mode)
Feb 11 04:07:06 linus kernel: Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)
Feb 11 04:07:06 linus kernel: Registered tone zone 0 (United States / North America)
Feb 11 04:07:06 linus kernel: Registered tone zone 0 (United States / North America)
Feb 11 04:07:12 linus kernel: -- Setting echo registers:
Feb 11 04:07:12 linus kernel: -- Set echo registers successfully
Feb 11 04:07:17 linus kernel: -- Setting echo registers:
Feb 11 04:07:17 linus kernel: -- Set echo registers successfully
Feb 11 04:07:17 linus kernel: -- Setting echo registers:
Feb 11 04:07:17 linus kernel: -- Set echo registers successfully
Feb 11 04:07:18 linus kernel: -- Setting echo registers:
Feb 11 04:07:18 linus kernel: -- Set echo registers successfully

The server has been working for about a week.  This server was fresh last weekend and has had little more than the previous versions of Asterisk/SAIL installed.

I'll play with the IVR/inbound tomorrow...4AM here...

Thanks much,

G

[SARK devs]

Hi guys,

I found two glitches - thanks a lot for the quick input from you all.

Also - Lloyd - did you have the card connected to the phone lines when you ran the test ?

Normally I wouldn't expect to see an output of zeros.

Also I'm assuming your card is an 02B which is why you got the failures on dev/zap/1 & 2 (which is OK).

Otherwise you guys look to be in good shape - the tune ran fine, which leaves the question of why Herve's didn't.

Lloyd - re your customApp fix,  the packager pulled the wrong version off SVN - he has been taken outside and given a sound beating.    

The cleaned up version for SAIL is 416 and it's already up on the server.  I will look into the missing symlink issue on asterisk and post another release to the mirrors shortly.

Thanks again to you all.

Best

Jeff

[sonoracomm]

To be more precise, I have a TDM04B (4 FXO ports) and I did this test:

I stopped Asterisk then immediately ran the fxotune command manually before any udev entries could fade:

Code: [Select]

linus*CLI> stop now
linus*CLI>
Disconnected from Asterisk server
Executing last minute cleanups
[root@linus ~]# asterisk -vvvvvvvvvvvvvvvr
Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)
[root@linus ~]# /home/selintra/fxotune -i -e 4
Tuning module /dev/zap/1
Could not fill input buffer - got -1 bytes, expected 4000 bytes
Failure!
Tuning module /dev/zap/2
Could not fill input buffer - got -1 bytes, expected 4000 bytes
Failure!
Tuning module /dev/zap/3
Could not fill input buffer - got -1 bytes, expected 4000 bytes
Failure!
Tuning module /dev/zap/4
Done!
Unable to tune 3 devices, even though those devices are present
There are 3 analog lines connected to the first 3 ports which fail.  The 4th port is disconnected.

BTW, when I run the Echo Tune with the button, it does take a good while to output this:

Code: [Select]

Waiting for udev...
waited 0 seconds for udev
starting zaptel...
Waiting for udev (second phase)...
waited 0 seconds for udev(second phase)

starting tuner task...
Tuning module /dev/zap/1
Failure!
Tuning module /dev/zap/2
Failure!
Tuning module /dev/zap/3
Failure!
Tuning module /dev/zap/4
Done!

I'll be going into the office later where I can be at the console.  I'm gonna see what I can do about shared interrupts...

G

[SARK devs]

hi

I googled this....

"I finally isolated the problem, hope it works for you too. The default -m
(silencegoodfor) default of 18 seconds is too long for my telco and the test is getting interrupted. I listened in on the line with a splitter and realized what was happening. I had to set -m down to 15 seconds in my case and it works. "

You can find the full thread here...

http://www.mail-archive.com/asterisk-users@lists.digium.com/msg170601.html

Maybe your Telco is like this one??

Sugest you break the dialtone and see how long it takes before the Telco puts something onto the line...

I can always put a switch-list field into the panel to handle different Telco requirements.  

Best

Selintra

[sonoracomm]

I had found this myself Googling...I'll try it when I get into the office.

Thanks very much,

G

[sonoracomm]

I put an analog phone on the line, pressed '5' and counted 14 seconds before the phone company complained.  So I ran this command at the console which limited the tests to 12 seconds:

fxotune -i 5 -m 12 -e 4

and it worked properly.

G

[SARK devs]

perfect....

I'll add parameters to the panel for m and the linebreak code.

Thanks for helping test this.

Kind Regards

J

[ldkeen]

Also - Lloyd - did you have the card connected to the phone lines when you ran the test ?

No, I'll retry with the line in and see how it goes.

Also I'm assuming your card is an 02B which is why you got the failures on dev/zap/1 & 2 (which is OK).

Yep that's correct.

Lloyd - re your customApp fix,  the packager pulled the wrong version off SVN - he has been taken outside and given a sound beating.

   
Well the beating seemed to fix the problem, it's working like a dream now.
Thanks heaps
Lloyd