All circuits are busy & CallerID
Submitted by paulr on Tue, 06/27/2006 - 9:26am.
So, I'm very happy that my X100P is now seen. Apparently due to the latest updates --Thanks!
I can call in, it answers, takes a message. Good.
What is the trick for outgoing? I have the same trunk setup for outgoing but when I try to dial out from a soft phone it just tells me that "All circuits are busy" and won't do it.
I also can't get CallerID to display. The card manufacturer says it supports it and my analog phones and another PC receive and decode the CallerID but I just get 'unknown' on TrixBox.
I'll start digging for those answers...but if somone knows them please let me know...Thanks!!!
 
Re: All circuits are busy & CallerID
Fri, 06/23/2006 - 12:31am
Okay, I think I have the outgoing resolved. I had to change the Zap Identifier back to g0. I got creative and named it Qwest so it would make more sense when it is in the list with ViaTalk. etc.
The "(trunk name)" made me think I could give it one in the settings.
Now, caller ID is set to yes...so I just need to figure out how to get it to come through correctly.
 
Re: All circuits are busy & CallerID
Tue, 06/27/2006 - 8:58am
I have been wrestling with similar CallerID problems with a digium 100 card, in the UK.
I have found this guide...
http://www.lusyn.com/resources/asterisk/usehist.htm
And although my linux skills are lacking (like i usually avoid Linux), i have got the asterisk souce, and rebuilt it with the patch's applies. (I had already got and built the zaptel drivers, with this patch to make it work under trixbox 1.0).
This was alot of effort, and in the end, pointless. I still have no caller ID information.
Does anyone have Caller ID working in the UK??
 
Re: All circuits are busy & CallerID
Tue, 06/27/2006 - 9:26am
Yes.
But to get it delivered reliably I've moved to using ATA's like the Linksys (Sipura) SPA3000's
Alan
 
Member Since:
2006-06-10