Actually this is only the case with analog Zap channels and
loopstart/groundstart T-1 Zap channels. E&M Wink and PRI Zap channels
do not have this problem because the line can tell Asterisk when the far
end answers.
[EMAIL PROTECTED] wrote:
Hello Yusuf,
This is a normal use of zap channels : it is not possible to see if the call
is realy answered, and Asterisk say yes as soon as the call is placed.
That's all...
Best Regards,
Francois BERGERET,
France.
-----Message d'origine-----
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Yusuf
Envoyé : mercredi 3 mai 2006 23:08
À : [email protected]
Objet : [Asterisk-Users] dialing FXO gives wrong billsec
Hi all,
I came across a new(to me that is) issue. I want to know from others what
they have done to resolve this. I have a 4 port digium card with FXO's, and
connected to each FXO is a premicell. When I dial the premicell, after
about two seconds is says 'ZAP/1 answered', then it takes a few more seconds
for the call to hit the cellular network, before the cellphone starts to
ring. However, asterisk sees the 'ZAP/1 answered' as the cell phone being
answered, so my billsecs in the cdr's are off by ten seconds or so, and all
the cdr's are 'ANSWERED', even though the cell phone was not answered.
my dial string looks like so: (all calls come in to inbound)
[inbound]
exten => _X.,1,Dial(ZAP/1)
I have a standard zaptel and zapata, Asterisk 1.2.6
thanks,
yusuf
--
Now accepting new clients in Birmingham, Atlanta, Huntsville,
Chattanooga, and Montgomery.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
