[asterisk-bugs] [Asterisk 0009099]: Calls arriving into the dialplan from chan_zap with a zero length Called Number IE fail to goto 's' priority of assigned context

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Sep 6 15:30:36 CDT 2007


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9099 
====================================================================== 
Reported By:                kb1_kanobe2
Assigned To:                dwaynemh
====================================================================== 
Project:                    Asterisk
Issue ID:                   9099
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   minor
Priority:                   low
Status:                     assigned
Asterisk Version:            1.2.15 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        Yes 
Request Review:              
====================================================================== 
Date Submitted:             02-19-2007 01:29 CST
Last Modified:              09-06-2007 15:30 CDT
====================================================================== 
Summary:                    Calls arriving into the dialplan from chan_zap with
a zero length Called Number IE fail to goto 's' priority of assigned context
Description: 
When an ISDN call arrives with a zero length Called Number IE. Eg.:

< [70 01 a1]
< Called Number (len= 3) [ Ext: 1  TON: National Number (2)  NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1) '' ]

A simple context consisting of:

 [in-cs1000]
 exten => s,1,NoOp(s)
 exten => s,2,Answer()
 exten => s,3,Dial(zap/g2/0,30)            ; Handle OSA IE

 exten => _X.,1,NoOp(_X.)
 exten => _X.,2,Answer()
 exten => _X.,3,Dial(zap/g2/${EXTEN},30)   ; Pass the call through

Results in a behavior of:

  -- Extension '' in context 'in-cs1000' from '8856800' does not exist. 
Rejecting call on channel 0/18, span 1

However, a context of:

 [in-cs1000]
 exten => ,1,NoOp(This shouldn't be necessary)

 exten => s,1,NoOp(s)
 exten => s,2,Answer()
 exten => s,3,Dial(zap/g2/0,30)            ; Handle OSA IE

 exten => _X.,1,NoOp(_X.)
 exten => _X.,2,Answer()
 exten => _X.,3,Dial(zap/g2/${EXTEN},30)   ; Pass the call through

results in:

 -- Accepting call from '8856800' to '' on channel 0/16, span 1
 -- Executing NoOp("Zap/13-1", "s") in new stack
 -- Executing Answer("Zap/13-1", "") in new stack
 -- Executing Dial("Zap/13-1", "zap/g2/0|30") in new stack

Notice that the '' priority as defined was apparently never touched. 

The '' priority really ought to be the entrypoint if defined and 'i' if
it's not, however having a line that reads "exten => ,1,..." is also quite
counterintuitive... other than ISDN issues is there any logical reason not
to have the call jump straight into to the 's' context?

====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 09-06-07 15:30  
---------------------------------------------------------------------- 
Patch for 1.4 uploaded.  Please test to ensure that it fixes your issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
09-06-07 15:30  Corydon76      Note Added: 0070063                          
======================================================================




More information about the asterisk-bugs mailing list