I overlooked ya Dave. I think we're going to concentrate on ISDN right now but perhaps number 3 below wasn't even thought of. I have an inquiry in for that. I suspect that their equipment can't do it but you never know. We need to look at ISDN regardless it seems.
I don't think Asterisk would ever be able to handle wink start. The true DID cards are scarce now and likely aren't generic enough to work with *. Your basic sequence looks right though, if its loop start. So if ISDN normally does DNIS, they should be able to program it send us the four digits of the virtual number, right? Interesting.... Peter M. > Hi Peter, > > If I understand correctly, this is the sequence of events: > 1) Aliant sends you ringing > 2) Your system should answer > 3) Aliant sends you DTMF tones indicating the DID (like ISDN DNIS) > 4) You collect the digits and route the call playing ring tone back to the > caller > > If that's correct then it sounds like you just need an autoattendant script > without the recordings. > Answer the call and setup an extension for each set of DID digits that you > could receive. > > Your message says you're trying to get away from this wink-start -> > tone-burst situation you've > got now. Is that because asterisk can't handle it or for another reason? If > asterisk can handle > the wink-start, then it seems like you might have a pretty simple solution by > just letting asterisk > capture the tones. > > Correct me if I've misunderstood something. > > Dave > > > On 2/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote: > Thanks Jim. You can see how weird the situation is then. What we're > trying > to do is fairly basic I think. Instead of our ancient PBX answering the > wink > start line and receiving the DID digits as a tone burst, we want the same > thing coming into a loop start FXO card instead, only ring voltage from > the > CO indicating an incoming call first. They got that working after two > trips to > the design dept. Apparently this falls down where they are unable to > program the virtual phone number to be transferred in place of the CID > info. > * is answering the call though. So close and yet so far away. > > I found this article when seem to indicate that ISDN is a substitute so > I'm > waiting on an assessment of that option.Now I just need to find a > multiport > ISDN card. > > http://kbase.gfi.com/showarticle.asp?id=KBID001349 > > > We would go to a PRI but the cost is prohibitive for the level of > messaging > services we are doing right now.Maybe when we look at the call centre > side, we will have PRI.Reality is we will probably need to support some > hardwired lines for a few clients, but the DID line problem seems to be > another kind of beast. > > Next time I get a call from Aliant tech support, I think I'll ask if its > "Al" > calling.That anonymous caller business is stupid. > > Peter M. > > > What is your application? If we know what you're trying to integrate, > we > > might be better able to brainstorm it with you. Analogue is generally a > bad > > idea when you need complex signalling, and the costs add up fast. > > > > -- > > Jim Van Meggelen > > [EMAIL PROTECTED] > > http://www.oreillynet.com/pub/au/2177 > > > > " > ******************************************************** Peter MacFarlane, ACP Network Administration & Programming Target Call Center/ Message Centre P.E.I. ***************************************************************** OpenBSD's PF Firewall: Now available with CARP Failover. Nothing to do with fish, but everything to do with security! *****************************************************************
