Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: fpausp on May 22, 2009, 03:53:41 PM

Title: Incomming Call Problem
Post by: fpausp on May 22, 2009, 03:53:41 PM

Hi All,

This day i have done the update to 2.6.9-78.0.22.EL and sail-2.3.1-4.noarch.rpm with Dahdi.
I used this commands for installation:

yum install asterisk libpri dahdi-tools asterisk-addons --enablerepo=smecontribs
yum install dahdi-linux-kmdl-`uname -r` --enablerepo=atrpms

I use a TDM400P Telephony Card (PCI Card: pci:0000:00:06.0 wctdm+ e159:0001 Wildcard TDM400P REV I).

The Problem is i get an error when somebody calls me from the pstn side:

-- Starting simple switch on 'DAHDI/4-1'
    -- Executing [s@mainmenu:1] GotoIf("DAHDI/4-1", "1?DAHDI4-1|1") in new stack
    -- Goto (mainmenu,DAHDI4-1,1)
    -- Executing [DAHDI4-1@mainmenu:1] AGI("DAHDI/4-1", "selintra|Inbound|DAHDI4-1") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
[May 22 15:21:48] ERROR[5740]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
    -- AGI Script selintra completed, returning 0
    -- Sent into invalid extension 'DAHDI4-1' in context 'extensions' on DAHDI/4-1
    -- Executing [i@extensions:1] PlayTones("DAHDI/4-1", "congestion") in new stack
    -- Executing [i@extensions:2] Hangup("DAHDI/4-1", "") in new stack
  == Spawn extension (extensions, i, 2) exited non-zero on 'DAHDI/4-1'
    -- Executing [h@extensions:1] Hangup("DAHDI/4-1", "") in new stack
  == Spawn extension (extensions, h, 1) exited non-zero on 'DAHDI/4-1'
    -- Hungup 'DAHDI/4-1'


regards
fpausp

Title: Re: Incomming Call Problem
Post by: SARK devs on May 22, 2009, 05:34:12 PM

Yes - we've seen this

We will publish 2.3.1.7 in a day or two which should fix the issue.

S

Title: Re: Incomming Call Problem
Post by: fpausp on May 22, 2009, 09:10:07 PM

OK, thank you !

Best
fpausp

Title: Re: Incomming Call Problem
Post by: Teviot on May 23, 2009, 06:18:26 AM

S

Not being up with the latest and great linux procedures, what is the up grade procedure for the following system.

1. Kernal - 2.6.9-78.0.13.EL

2. Sail    - sail-2.2.1-759

3. I believe the system is using zaptel

Title: Re: Incomming Call Problem
Post by: SARK devs on May 23, 2009, 11:11:56 AM

The biggest problem is getting hold of .13 compatible asterisk and zaptel rpms.  The Firewall Services guys have deleted/replaced the .13 asterisk version they had on smecontribs and replaced it with .22 items, presumably because .22 is now the current SME kernel release.  Also, the release they appear to have harvested is based upon Asterisk 1.4.23 with DAHDI, so no Zaptel I'm afraid.

We just updated our main test units from .08 to .22 yesterday, but we chose to install asterisk-1.4.24 with DAHDI.  We should have that bedded in in a few days so you might wish to wait until then if you can't find the rpms you need.

As to procedure for an upgrade; here is one of our upgrades from yesterday

Code: [Select]

yum remove zaptel-kmdl-`uname -r`
yum update kernel
reboot
 
yum install dahdi-linux-kmdl-`uname -r` dahdi-tools libpri asterisk asterisk-addons --enablerepo=atrpms
yum localinstall sail-2.3.1-6.2.noarch.rpm --enablerepo=base
reboot


Kind Regards

S

   

Title: Re: Incomming Call Problem
Post by: David Harper on May 24, 2009, 03:49:17 AM

The Zaptel compatible Asterisk is still in my repository archive.

Title: Re: Incomming Call Problem
Post by: Teviot on June 04, 2009, 07:33:20 AM

selintra

Just checking, the quote below is still the current way to upgrade?  I feeling brave and just want to check that I have the right proceedure.

Also, is there anything else I should be looking for as I upgrade?

Quote from: selintra on May 23, 2009, 11:11:56 AM

The biggest problem is getting hold of .13 compatible asterisk and zaptel rpms.  The Firewall Services guys have deleted/replaced the .13 asterisk version they had on smecontribs and replaced it with .22 items, presumably because .22 is now the current SME kernel release.  Also, the release they appear to have harvested is based upon Asterisk 1.4.23 with DAHDI, so no Zaptel I'm afraid.

We just updated our main test units from .08 to .22 yesterday, but we chose to install asterisk-1.4.24 with DAHDI.  We should have that bedded in in a few days so you might wish to wait until then if you can't find the rpms you need.

As to procedure for an upgrade; here is one of our upgrades from yesterday

Code: [Select]

yum remove zaptel-kmdl-`uname -r`
yum update kernel
reboot
 
yum install dahdi-linux-kmdl-`uname -r` dahdi-tools libpri asterisk asterisk-addons --enablerepo=atrpms
yum localinstall sail-2.3.1-6.2.noarch.rpm --enablerepo=base
reboot


Kind Regards

S

 

S

Please look at http://www.craig.id.au/sme/sail/ (http://www.craig.id.au/sme/sail/) and let me know if this is correct? I want to save all the procedures that I use that I will use again elsewhere.

Title: Re: Incomming Call Problem
Post by: SARK devs on June 04, 2009, 08:38:36 AM

Latest release is 2.3.1.9.

Kind Regards

S

Title: Re: Incomming Call Problem
Post by: fpausp on July 04, 2009, 05:34:51 PM

Hi All,

Today i tried another install (sail-2.3.1-20 and Asterisk 1.4.25.1) of sail with dahdi on an up to date sme7.4 with a TDM400P.


When someone try to call me via pstn:

Code: [Select]

fpausp*CLI>
    -- Starting simple switch on 'DAHDI/4-1'
    -- Executing [s@mainmenu:1] GotoIf("DAHDI/4-1", "1?DAHDI4-1|1") in new stack
    -- Goto (mainmenu,DAHDI4-1,1)
    -- Executing [DAHDI4-1@mainmenu:1] AGI("DAHDI/4-1", "selintra|Inbound|DAHDI4-1") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [7000@internal-presets:1] AGI("DAHDI/4-1", "selintra|Alias||7000") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
  == Auto fallthrough, channel 'DAHDI/4-1' status is 'UNKNOWN'
    -- Executing [h@internal-presets:1] Hangup("DAHDI/4-1", "") in new stack
  == Spawn extension (internal-presets, h, 1) exited non-zero on 'DAHDI/4-1'
    -- Hungup 'DAHDI/4-1'
    -- Starting simple switch on 'DAHDI/4-1'
[Jul  4 17:30:15] NOTICE[5172]: chan_sip.c:7683 sip_reg_timeout:    -- Registration for 'voip@192.168.1.220' timed out, trying again (Attempt #1)
[Jul  4 17:30:18] NOTICE[5954]: chan_dahdi.c:6836 ss_thread: Got event 18 (Ring Begin)...
    -- Executing [s@mainmenu:1] GotoIf("DAHDI/4-1", "1?DAHDI4-1|1") in new stack
    -- Goto (mainmenu,DAHDI4-1,1)
    -- Executing [DAHDI4-1@mainmenu:1] AGI("DAHDI/4-1", "selintra|Inbound|DAHDI4-1") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [7000@internal-presets:1] AGI("DAHDI/4-1", "selintra|Alias||7000") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
  == Auto fallthrough, channel 'DAHDI/4-1' status is 'UNKNOWN'
    -- Executing [h@internal-presets:1] Hangup("DAHDI/4-1", "") in new stack
  == Spawn extension (internal-presets, h, 1) exited non-zero on 'DAHDI/4-1'
    -- Hungup 'DAHDI/4-1'
    -- Starting simple switch on 'DAHDI/4-1'
[Jul  4 17:30:30] NOTICE[5957]: chan_dahdi.c:6836 ss_thread: Got event 18 (Ring Begin)...
    -- Executing [s@mainmenu:1] GotoIf("DAHDI/4-1", "1?DAHDI4-1|1") in new stack
    -- Goto (mainmenu,DAHDI4-1,1)
    -- Executing [DAHDI4-1@mainmenu:1] AGI("DAHDI/4-1", "selintra|Inbound|DAHDI4-1") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [7000@internal-presets:1] AGI("DAHDI/4-1", "selintra|Alias||7000") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
  == Auto fallthrough, channel 'DAHDI/4-1' status is 'UNKNOWN'
    -- Executing [h@internal-presets:1] Hangup("DAHDI/4-1", "") in new stack
  == Spawn extension (internal-presets, h, 1) exited non-zero on 'DAHDI/4-1'
    -- Hungup 'DAHDI/4-1'
[Jul  4 17:30:35] NOTICE[5172]: chan_sip.c:7683 sip_reg_timeout:    -- Registration for 'voip@192.168.1.220' timed out, trying again (Attempt #2)
    -- Starting simple switch on 'DAHDI/4-1'
[Jul  4 17:30:42] NOTICE[5960]: chan_dahdi.c:6836 ss_thread: Got event 18 (Ring Begin)...
    -- Executing [s@mainmenu:1] GotoIf("DAHDI/4-1", "1?DAHDI4-1|1") in new stack
    -- Goto (mainmenu,DAHDI4-1,1)
    -- Executing [DAHDI4-1@mainmenu:1] AGI("DAHDI/4-1", "selintra|Inbound|DAHDI4-1") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [7000@internal-presets:1] AGI("DAHDI/4-1", "selintra|Alias||7000") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
  == Auto fallthrough, channel 'DAHDI/4-1' status is 'UNKNOWN'
    -- Executing [h@internal-presets:1] Hangup("DAHDI/4-1", "") in new stack
  == Spawn extension (internal-presets, h, 1) exited non-zero on 'DAHDI/4-1'
    -- Hungup 'DAHDI/4-1'
    -- Starting simple switch on 'DAHDI/4-1'
[Jul  4 17:30:54] NOTICE[5963]: chan_dahdi.c:6836 ss_thread: Got event 18 (Ring Begin)...
    -- Executing [s@mainmenu:1] GotoIf("DAHDI/4-1", "1?DAHDI4-1|1") in new stack
    -- Goto (mainmenu,DAHDI4-1,1)
    -- Executing [DAHDI4-1@mainmenu:1] AGI("DAHDI/4-1", "selintra|Inbound|DAHDI4-1") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
    -- Executing [7000@internal-presets:1] AGI("DAHDI/4-1", "selintra|Alias||7000") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
    -- AGI Script selintra completed, returning 0
  == Auto fallthrough, channel 'DAHDI/4-1' status is 'UNKNOWN'
    -- Executing [h@internal-presets:1] Hangup("DAHDI/4-1", "") in new stack
  == Spawn extension (internal-presets, h, 1) exited non-zero on 'DAHDI/4-1'
    -- Hungup 'DAHDI/4-1'
[Jul  4 17:30:55] NOTICE[5172]: chan_sip.c:7683 sip_reg_timeout:    -- Registration for 'voip@192.168.1.220' timed out, trying again (Attempt #3)
fpausp*CLI>


With zaptel i had no problems but with dahdi i dont know how i can fix that ?
Can somone help me please ?

fpausp

Title: Re: Incomming Call Problem
Post by: SARK devs on July 04, 2009, 09:08:55 PM

Does alias 7000 exist?

It has no extensions defined in it.

an alias call is selintra|Alias|extension list|alias name

here is a correct example...

Code: [Select]

Executing [9000@internal-presets:1] AGI("SIP/213.166.5.140-b7502750", "selintra|Alias|SIP/4110 SIP/4116 SIP/4020 SIP/5004|9000") in new stack
Here is yours

Code: [Select]

Executing [7000@internal-presets:1] AGI("DAHDI/4-1", "selintra|Alias||7000") in new stack
No extension list

Regards
S

Title: Re: Incomming Call Problem
Post by: fpausp on July 05, 2009, 08:26:17 AM

Hi,

Yes that was the problem, i tried to use an selintra-work and selintra file from an old installation, thats maybe not a good idea.

I made a new 7000 alias and after that the incomming call is working now, but i have at least one more problem in the operator panel. The panel shows old extensions and zaptel ?

Can i clean up the old selintra-work and selintra files or must i configure all from scratch ?


Best
fpaup

Title: Re: Incomming Call Problem
Post by: SARK devs on July 05, 2009, 12:21:41 PM

just aissue a commit to rebuild the panel and you should be OK

Title: Re: Incomming Call Problem
Post by: fpausp on July 07, 2009, 07:18:50 PM

Hi,

Thanks for your answer, the panel was not updated after the commit.

What else can i do ?

Best
fpausp

Title: Re: Incomming Call Problem
Post by: SARK devs on July 08, 2009, 12:55:54 PM

Sorry, FOP has not been upgraded for DAHDI yet.  That will not happen for another couple of weeks when we implement FOP2 .  You will than have the choice of FOP2 or FOP (probably)

Best

S

Title: Re: Incomming Call Problem
Post by: fpausp on July 08, 2009, 08:07:32 PM

OK, thanks for your help.

Best
fpausp