asterisk users - Aug 2009 - POTS supervision with DAHDI in 1.4 releases

Greetings,

               This may be a dumb question, but here goes.  When I was on
1.4.21.2 using Zaptel, I had (at least as far as I could tell) access to
line supervision on my POTS lines using a TDM400P/TDM410P.   Since upgrading
to the DAHDI branches of 1.4 (SVN and 1.4.26.1), I've only been able to
duplicate the success of the 1.4.21 functionality once.   To test what I'm
talking about, copy this call.file to your  /var/spool/asterisk/outgoing,
changing 5551212 to the number you want to call - 

Channel: DAHDI/1/ww5551212

CallerID: SIP/104

MaxRetries: 1

WaitTime: 60

retryTime: 5

Application: background

Data: demo-instruct

 

In my shop, I lose about 10-15 seconds of the message waiting on a TELCO
connection (if there is no answer, Asterisk just plays the message and hangs
up).    I'd be happy to do this with AMI instead of a call file, but if
Asterisk doesn't know if the line has actually been answered, it makes no
difference.

 

Thanks in advance for any suggestions, helpful or otherwise.

 

Danny Nicholas

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090827/50b93541/attachment.htm

Danny Nicholas wrote:
>                This may be a dumb question, but here goes.  When I was
> on 1.4.21.2 using Zaptel, I had (at least as far as I could tell) access
> to line supervision on my POTS lines using a TDM400P/TDM410P.   Since
> upgrading to the DAHDI branches of 1.4 (SVN and 1.4.26.1), I?ve only
> been able to duplicate the success of the 1.4.21 functionality once. 
There were no significant functional changes in the transition from
Zaptel to DAHDI, except for feature additions in DAHDI. While it is
certainly possible that chan_dahdi has had changes that are affecting
this behavior for you, it should not matter whether you build against
Zaptel or DAHDI.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
skype: kpfleming | jabber: kpfleming at digium.com
Check us out at www.digium.com & www.asterisk.org

On Thu, Aug 27, 2009 at 10:14:25AM -0500, Danny Nicholas
wrote:
> Greetings,
> 
>                This may be a dumb question, but here goes.  When I was on
> 1.4.21.2 using Zaptel, I had (at least as far as I could tell) access to
> line supervision on my POTS lines using a TDM400P/TDM410P.   Since
upgrading
> to the DAHDI branches of 1.4 (SVN and 1.4.26.1), I've only been able to
> duplicate the success of the 1.4.21 functionality once.   To test what
I'm
> talking about, copy this call.file to your  /var/spool/asterisk/outgoing,
> changing 5551212 to the number you want to call - 
> 
> Channel: DAHDI/1/ww5551212
> 
> CallerID: SIP/104
> 
> MaxRetries: 1
> 
> WaitTime: 60
> 
> retryTime: 5
> 
> Application: background
> 
> Data: demo-instruct
> 
>  
> 
> In my shop, I lose about 10-15 seconds of the message waiting on a TELCO
> connection (if there is no answer, Asterisk just plays the message and
hangs
> up).    I'd be happy to do this with AMI instead of a call file, but if
> Asterisk doesn't know if the line has actually been answered, it makes
no
> difference.
Has this actually ever worked?

Do you use the same zapata.conf / chan_dahdi.conf ? Do you have
'answeronpolarityswitch = yes' ?

To avoid confusion, consider making one a symlink to the other for the
time of testing.

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir