Topic: Greetings

[Teviot]

If I'm not mistake and Selintra will confirm or deny this you should have got something like this

Code: [Select]

[root@sail ~]# uname -r
2.6.9-78.0.8.EL
[root@sail ~]# rpm -qa | grep zaptel-kmdl
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
zaptel-kmdl-2.6.9-67.0.1.EL-1.4.9.2-48.el4
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
zaptel-kmdl-2.6.9-67.0.1.ELsmp-1.4.9.2-48.el4
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
[root@sail ~]#
And ignoring the signature errors

[SARK devs]

Teviot is correct

You don't appear to have installed zaptel or zaptel-kmdl.  I also notice fom earlier that you don't have the extended sound pack installed either.

Kind Regards

S

[Graham]

Think I've fixed it must have mised it when I installed it, yum install zaptel-kmdl-`uname -r` --enablerepo=atrpms

I've just run these again, and the only one that did anything was the one above all the other ones reported nothing to do

yum install zaptel --enablerepo=atrpms
yum install libpri  --enablerepo=atrpms
yum install asterisk --enablerepo=atrpms
yum install zaptel-kmdl-`uname -r` --enablerepo=atrpms
yum install asterisk-addons  --enablerepo=atrpms

does that mean the extended sound pack is installed

[Teviot]

sprattgraham

Issue the following at the command prompt and check to see if you get a similar result as I did

uname -r

rpm -qa | grep zaptel-kmdl

[Graham]

I can only see one difference, zaptel-kmdl-2.6.9-67.0.1.ELsmp-1.4.9.2-48.el4

[root@server-1 ~]# uname -r
2.6.9-78.0.8.EL

[root@server-1 ~]# rpm -qa | grep zaptel-kmdl
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature
zaptel-kmdl-2.6.9-78.0.8.EL-1.4.12.1-54.99.el4
warning: only V3 signatures can be verified, skipping V4 signature
warning: only V3 signatures can be verified, skipping V4 signature

[Teviot]

Sprattgraham

Maybe run these again

Code: [Select]

yum install zaptel --enablerepo=atrpms
yum install libpri  --enablerepo=atrpms
yum install asterisk --enablerepo=atrpms
yum install zaptel-kmdl-`uname -r` --enablerepo=atrpms
yum install asterisk-addons  --enablerepo=atrpms
then run

Code: [Select]

uname -r and

Code: [Select]

rpm -qa | grep zaptel-kmdland see what you get.

Other then that I don't have enought knowledge about SAIL to advise you any further than I have.  Selintra or someone with a little knowledge in this area would be the ones to help you with this.

Good Luck

[SARK devs]

UK GB soundpack is here...

http://www.sarkpbx.com/sail/languagepack/sme-ast-en-uk-gpl-sounds-1.0.0-3.noarch.rpm

download it with wget and install it with rpm...

Code: [Select]

wget http://www.sarkpbx.com/sail/languagepack/sme-ast-en-uk-gpl-sounds-1.0.0-3.noarch.rpm
rpm -Uvh sme-ast-en-uk-gpl-sounds-1.0.0-3.noarch.rpm
Regards

[Graham]

Thanks again that sound pack is a lot better, do I need zaptel-kmdl-2.6.9-67.0.1.ELsmp-1.4.9.2-48.el4 or just zaptel-kmdl-2.6.9-67.0.1.EL-1.4.9.2-48.el4

I’ve checked the manual for my phone and it doesn’t say anything about HD, http://www.pirellibroadband.com/web/products-solutions/solutions/sme-net/terminals/default.page

[SARK devs]

The two kmdl versions; EL and ELsmp are for the two linux kernels EL (single processor) and ELsmp (Symmetrical Multi Processor).  As a general rule, run the smp kernel if you have a multicore CPU(s) and the EL kernel if you have a single CPU.   If you don't know what you've got then look in /proc/cpuinfo - like this....

Code: [Select]

cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 15
model           : 2
model name      : Intel(R) Pentium(R) 4 CPU 2.80GHz
stepping        : 9
cpu MHz         : 2802.630
cache size      : 512 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr
bogomips        : 5603.45
 

This will give you a summary of each CPU in the box.  The above example shows a single 2.8Ghz Pentium IV.

[Graham]

Had a play with this # issue I changed all the SIP settings to sipgate and made a call and had no issue if pressing the # key, they changed them back to Asterisk without restarting the phone and the outbound audio was no good after restarting it was fine again.

[Graham]

After a bit more of a play it now seems that pressing any key causes this outbound issue, but only when using Asterisk.

Now from reading this post, this user isn't having any issues: http://forums.digium.com/viewtopic.php?t=14924&highlight=dpl10

[Graham]

Anyone have any ideas

[SARK devs]

If it's only doing it on one phone type then it's phone related.  I can't recreate any of the symptoms you recount on our reference server and we've had no other reports of this nature so I'm satisfied that it definitely isn't SAIL related and it probably isn't Asterisk related. 

As an aside, it is generally NOT good practice to use # and *2 to do blind and attended transfers in the Asterisk environment, unless you have no choice.   Both of these depend upon the remote asterisk recognising the DTMF you are sending (which it may not always do).  Better to use SIP re-invites.  Pretty much ALL SIP phones (with the exception of one or two handheld DECT hybrids) are capable of SIP re-invite.  Usually this is done through a transfer button on the phone itself.  It involves no DTMF and, because the phone is in direct control, its usually much easier to retrieve an unanswered call or to abandon an incorrectly keyed transfer.   It is also less prone to losing calls "somewhere in the ether", which can be done quite easily with # and 2* transfers.

Kind Regards

S

[Graham]

Thanks, I don't think it's the phone as it doesn't cause issues with sipgate.

Maybe an Asterisk issue, it's not just # or * it's the number buttons as well that cause the issue.

[Graham]

Sorry to keep going on about this, is anyone know of an Asterisk server I can use to do an echo test to see if it’s my server.