Koozali.org formerly Contribs.org

Upgrade to DAHDI and sail 2.3.1

Upgrade to DAHDI and sail 2.3.1
« on: April 09, 2009, 02:31:27 AM »
Hi
Our system would not apply updates due to zaptel and zaptel-kmdl, so we excluded smecontribs and applied the updates. All OK but no analogue phones. Then applied the sail, asterisk and dahdi updates. We had some problems with loading Dahdi (it stopped on wcb4xxp not found). Removed all modules for zaptel and restarted Dahdi. Loaded OK. Continued to initialise the hardware and this has run without error.

Our problem is now an incoming call on the analogue line just rings outbut with this error on th console
Code: [Select]
[Apr  9 10:15:07] WARNING[30410]: chan_dahdi.c:6665 ss_thread: CallerID returned with error on channel 'DAHDI/1-1'
    -- Executing [s@mainmenu:1] AGI("DAHDI/1-1", "selintra|CheckState|") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
[Apr  9 10:15:07] ERROR[30410]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
    -- AGI Script selintra completed, returning 0
    -- Sent into invalid extension 's' in context 'extensions' on DAHDI/1-1
    -- Executing [i@extensions:1] PlayTones("DAHDI/1-1", "congestion") in new stack
    -- Executing [i@extensions:2] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, i, 2) exited non-zero on 'DAHDI/1-1'
    -- Executing [h@extensions:1] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, h, 1) exited non-zero on 'DAHDI/1-1'
    -- Hungup 'DAHDI/1-1'
Regards

Gordon............

Re: Upgrade to DAHDI and sail 2.3.1
« Reply #1 on: April 09, 2009, 02:43:41 AM »
This maybe a asterisk 1.4.23.1 see http://archives.free.net.ph/message/20090306.210230.8f2e9ab6.it.html
or
http://archivio.us/asterisk-users@lists.digium.com/msg03554.html
Still looking

An incoming call on the PSTN lines does not sense the caller hanging up and then just continually loops on the console until a dahdi restart command is issued.

Code: [Select]
[Apr  9 11:36:45] NOTICE[4576]: chan_dahdi.c:6525 ss_thread: Got event 18 (Ring Begin)...
[Apr  9 11:36:47] NOTICE[4576]: chan_dahdi.c:6525 ss_thread: Got event 2 (Ring/Answered)...
[Apr  9 11:36:48] NOTICE[4576]: chan_dahdi.c:6525 ss_thread: Got event 18 (Ring Begin)...
    -- Executing [s@mainmenu:1] AGI("DAHDI/1-1", "selintra|CheckState|") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
AGI Tx >> agi_request: selintra
AGI Tx >> agi_channel: DAHDI/1-1
AGI Tx >> agi_language: en
AGI Tx >> agi_type: DAHDItart
AGI Tx >> agi_uniqueid: 1239241004.30
AGI Tx >> agi_callerid: unknown
AGI Tx >> agi_calleridname: unknown
AGI Tx >> agi_callingpres: 0
AGI Tx >> agi_callingani2: 0
AGI Tx >> agi_callington: 0
AGI Tx >> agi_callingtns: 0
AGI Tx >> agi_dnid: unknown
AGI Tx >> agi_rdnis: unknown
AGI Tx >> agi_context: mainmenu
AGI Tx >> agi_extension: s
AGI Tx >> agi_priority: 1
AGI Tx >> agi_enhanced: 0.0
AGI Tx >> agi_accountcode:
AGI Tx >>
AGI Rx << GET VARIABLE EXTLEN
AGI Tx >> 200 result=1 ()
AGI Rx << DATABASE GET "STAT" "OCSTAT"
AGI Tx >> 200 result=1 (OPEN)
AGI Rx << SET VARIABLE REMOTENUM ""
AGI Tx >> 200 result=1
AGI Rx << GET VARIABLE VOICEINSTR
AGI Tx >> 200 result=1 (YES)
AGI Rx << SET VARIABLE OPEN "YES"
AGI Tx >> 200 result=1
AGI Rx << DATABASE GET "STAT" "IVRSTAT"
AGI Tx >> 200 result=0restart
AGI Rx << SET PRIORITY 1start
AGI Tx >> 200 result=0
AGI Rx << SET EXTENSION
AGI Tx >> 520-Invalid command syntax.  Proper usage follows:
AGI Tx >>  Usage: SET EXTENSION <new extension>
        Changes the extension for continuation upon exiting the application.
AGI Tx >> 520 End of proper usage.
AGI Rx << SET CONTEXT extensions
AGI Tx >> 200 result=0
[Apr  9 11:36:49] ERROR[4576]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
    -- AGI Script selintra completed, returning 0
    -- Sent into invalid extension 's' in context 'extensions' on DAHDI/1-1
    -- Executing [i@extensions:1] PlayTones("DAHDI/1-1", "congestion") in new stack
    -- Executing [i@extensions:2] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, i, 2) exited non-zero on 'DAHDI/1-1'
    -- Executing [h@extensions:1] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, h, 1) exited non-zero on 'DAHDI/1-1'
    -- Hungup 'DAHDI/1-1'
    -- Starting simple switch on 'DAHDI/1-1'
[Apr  9 11:36:58] NOTICE[4699]: chan_dahdi.c:6525 ss_thread: Got event 17 (Polarity Reversal)...
    -- Executing [s@mainmenu:1] AGI("DAHDI/1-1", "selintra|CheckState|") in new stack
    -- Launched AGI Script /var/lib/asterisk/agi-bin/selintra
AGI Tx >> agi_request: selintra
AGI Tx >> agi_channel: DAHDI/1-1
AGI Tx >> agi_language: en
AGI Tx >> agi_type: DAHDItart
AGI Tx >> agi_uniqueid: 1239241012.31
AGI Tx >> agi_callerid: unknown
AGI Tx >> agi_calleridname: unknown
AGI Tx >> agi_callingpres: 0t
AGI Tx >> agi_callingani2: 0t
AGI Tx >> agi_callington: 0rt
AGI Tx >> agi_callingtns: 0rt
AGI Tx >> agi_dnid: unknownrt
AGI Tx >> agi_rdnis: unknownt
AGI Tx >> agi_context: mainmenu
AGI Tx >> agi_extension: sart
AGI Tx >> agi_priority: 1tart
AGI Tx >> agi_enhanced: 0.0rt
AGI Tx >> agi_accountcode: rt
AGI Tx >> *CLI> dahdi restart
AGI Rx << GET VARIABLE EXTLEN
AGI Tx >> 200 result=1 ()
AGI Rx << DATABASE GET "STAT" "OCSTAT"
AGI Tx >> 200 result=1 (OPEN)
AGI Rx << SET VARIABLE REMOTENUM ""
AGI Tx >> 200 result=1
AGI Rx << GET VARIABLE VOICEINSTR
AGI Tx >> 200 result=1 (YES)
AGI Rx << SET VARIABLE OPEN "YES"
AGI Tx >> 200 result=1
AGI Rx << DATABASE GET "STAT" "IVRSTAT"
AGI Tx >> 200 result=0
AGI Rx << SET PRIORITY 1
AGI Tx >> 200 result=0
AGI Rx << SET EXTENSION
AGI Tx >> 520-Invalid command syntax.  Proper usage follows:
AGI Tx >>  Usage: SET EXTENSION <new extension>
        Changes the extension for continuation upon exiting the application.
AGI Tx >> 520 End of proper usage.
AGI Rx << SET CONTEXT extensions
AGI Tx >> 200 result=0
[Apr  9 11:36:58] ERROR[4699]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
    -- AGI Script selintra completed, returning 0
    -- Sent into invalid extension 's' in context 'extensions' on DAHDI/1-1
    -- Executing [i@extensions:1] PlayTones("DAHDI/1-1", "congestion") in new stack
    -- Executing [i@extensions:2] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, i, 2) exited non-zero on 'DAHDI/1-1'
    -- Executing [h@extensions:1] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, h, 1) exited non-zero on 'DAHDI/1-1'
    -- Hungup 'DAHDI/1-1'


Open to any suggestions. Thanks
« Last Edit: April 09, 2009, 03:41:56 AM by compsos »
Regards

Gordon............

Re: Upgrade to DAHDI and sail 2.3.1
« Reply #2 on: April 09, 2009, 03:59:55 AM »
Should all traces of zaptel be removed prior to installing Dahdi?
Regards

Gordon............

Re: Upgrade to DAHDI and sail 2.3.1
« Reply #3 on: April 09, 2009, 05:00:49 AM »
Removal of all the zaptel modules has not made any change other than no invalid modules being loaded. See 1st post.

But it has not solved the incoming call issues
Code: [Select]
AGI Tx >> 520-Invalid command syntax.  Proper usage follows:
AGI Tx >>  Usage: SET EXTENSION <new extension>
        Changes the extension for continuation upon exiting the application.
AGI Tx >> 520 End of proper usage.
AGI Rx << SET CONTEXT extensions
AGI Tx >> 200 result=0
[Apr  9 12:52:17] ERROR[23482]: utils.c:966 ast_carefulwrite: write() returned error: Broken pipe
    -- AGI Script selintra completed, returning 0
    -- Sent into invalid extension 's' in context 'extensions' on DAHDI/1-1
    -- Executing [i@extensions:1] PlayTones("DAHDI/1-1", "congestion") in new stack
    -- Executing [i@extensions:2] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, i, 2) exited non-zero on 'DAHDI/1-1'
    -- Executing [h@extensions:1] Hangup("DAHDI/1-1", "") in new stack
  == Spawn extension (extensions, h, 1) exited non-zero on 'DAHDI/1-1'
    -- Hungup 'DAHDI/1-1'

We think this may indicate the start of the error
Code: [Select]
AGI Tx >> 520-Invalid command syntax.  Proper usage follows:
AGI Tx >>  Usage: SET EXTENSION <new extension>
        Changes the extension for continuation upon exiting the application.
Followed by
Code: [Select]
-- Sent into invalid extension 's' in context 'extensions' on DAHDI/1-1
Have tried remove and add extensions but no change. The looping now appears to have stopped at least. The extensions.conf file still looks like the original from the previous version.

Thanks
Regards

Gordon............

Offline SARK devs

  • ****
  • 2,806
    • http://sarkpbx.com
Re: Upgrade to DAHDI and sail 2.3.1
« Reply #4 on: April 09, 2009, 10:40:08 PM »
looks like bug has crept in Gordon.

I'll have them try to replicate it tomorrow

Best

S

Offline SARK devs

  • ****
  • 2,806
    • http://sarkpbx.com
Re: Upgrade to DAHDI and sail 2.3.1
« Reply #5 on: April 09, 2009, 10:49:38 PM »
I've just looked at this and found the greenie. 

Somehow, that build has been regressed to an earlier SVN release number.  Please accept my apologies, these things do sometimes happen when you are pushing hard at targets and deliveries. :oops: 

All being well, we'll do a rebuild tomorrow for you.

Best

S

 

(Not Solved) Re: Upgrade to DAHDI and sail 2.3.1
« Reply #6 on: April 10, 2009, 12:46:16 AM »
Could not find a solution so we have wound the system back to
asterisk-1.4.21.1-65.el4
asterisk-addons-1.4.7-21.el4
asterisk-core-sounds-en-g729-1.4.11-53
zaptel-1.4.12.1-54.99.el4
zaptel-kmdl-2.6.9-78.0.13.ELsmp-1.4.12.1-54.99.el4
sail-2.2.1-745

Initially had the same error after the wind back until we removed the dahdi trunks and reset the zap ones back to the menus.

Looks like the problem was between the Dahdi interfaces and the Sail AGI function not returning the extension.

Code: [Select]
AGI Tx >> 200 result=1 ()
AGI Rx << EXEC Background silence/1
    -- AGI Script Executing Application: (Background) Options: (silence/1)
    -- <Zap/1-1> Playing 'silence/1' (language 'en')
AGI Tx >> 200 result=0
AGI Rx << EXEC Wait 1
    -- AGI Script Executing Application: (Wait) Options: (1)
AGI Tx >> 200 result=0
AGI Rx << STREAM FILE usergreeting3001 "34" 0
    -- Playing 'usergreeting3001' (escape_digits=34) (sample_offset 0)

Hope this helps someone else.
Regards

Gordon............

Re: Upgrade to DAHDI and sail 2.3.1
« Reply #7 on: April 10, 2009, 12:48:59 AM »
Hi Jeff
Cross posted I had not seen your reply. Thank you.
I will give it a try when it comes out now that I know a way of going back to operational state.
Happy Easter. :smile:
Regards

Gordon............