asterisk users - Aug 2005 - PRI dropped calls w/ asterisk dropped betweenpstn & norstar

> -----Original Message-----
> From: asterisk-users-bounces@lists.digium.com
> [mailto:asterisk-users-bounces@lists.digium.com]On Behalf Of Gary Reuter
> Sent: Thursday, August 11, 2005 12:59 PM
> To: asterisk-users@lists.digium.com
> Subject: Re: [Asterisk-Users] PRI dropped calls w/ asterisk dropped
> betweenpstn & norstar
> 
> 
> I poured over my logs most of the morning.  I'm fairly convinced at
> this point the disconnect is coming from the Norstar 10 seconds after
> the call was initiated.  This points to the 'T310' timer, similar
to
> what is described here:
> http://www.cisco.com/en/US/tech/tk652/tk701/technologies_tech_
> note09186a0080094487.shtml
> for the Cisco CallManager.
> When comparing the log from a successful call to a failed call, I
> noticed Asterisk was not passing back call-progress from the PSTN-span
> to the PBX-span.
http://bugs.digium.com/view.php?id=4468 may have what you're looking for. If
not, it sounds like a very similar problem. Likely you can work around it by
issuing an Answer() to the Norstar before dialing out. That will satisfy the
Norstars ISDN timers. Also, try enabling extended results on the Norstar - you
should see a 'recov time exp' error message displayed on the originating
set.

Hope that helps.

Kris Boutilier
Information Services Coordinator
Sunshine Coast Regional District

On 8/11/05, Kris Boutilier <Kris.Boutilier@scrd.bc.ca>
wrote:
> 
> http://bugs.digium.com/view.php?id=4468 may have what you're looking
for. If not, it sounds like a very similar problem. Likely you can work around
it by issuing an Answer() to the Norstar before dialing out. That will satisfy
the Norstars ISDN timers. Also, try enabling extended results on the Norstar -
you should see a 'recov time exp' error message displayed on the
originating set.
> 
> Hope that helps.
> 
It does sound very familiar.
I stuck an Answer before the Dial in the context for calls coming out
of the Norstar, and can no longer reproduce the problem.  Quick
once-over of the pri debug logs shows the connections took longer than
10 seconds.
Thanks for the help!