Asterisk 1.0.3 TDM400P/TE410P
Using originate() call progress "Events"
normal progression on completed call
================ Event: Newstate State: Ringing
Event: NewState State: up ================
On "pri Zap" channels call progress events will wait @ "State:Ringing" until call FAILS via timeout if number dialed is disco'd, out of service, etc. and produce a progression of .....
================ Event: Newstate State: Ringing
(long boring wait)
Event: Hangup Cause: 0 ================
The only exception is if dialed number is busy, then will instantly go from ringing to...
================ Event: Newstate State: Ringing
Event: Hangup Cause: 17 ================
So on pri Zap channels it seems there are only three causes that get issued on hangups ....
0 (not defined) 16 (normal clearing) 17 (user busy)
On "analog PSTN Zap channels" every call goes directly from "State: ringing" to "State: up" regardless of call completion.
Which allows calls to be transfered instantly and user can then disposition call accordingly.
Our development system is using TDM400P and production system using a TE410P
Am I missing something? or is Asterisk not reconizing the status on the pri Zap channel, or is it, and just not issuing event causes for them?
Does anyone know if work has been continued on this, to pass proper cause codes and not wait for call "FAIL" in 1.0.x or cvs?
Or is there anyway to get around this so calls procceed without waiting for a FAIL/timeout, much like PSTN Zap channels do?
We need this, to the extent we may have to install multiple analog lines and shed our "smarter" pri line.
Suggestions?
_______________________________________________ Asterisk-Users mailing list Asterisk-Users@lists.digium.com http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users