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. I love your sig file BTW. Peter M. > There should NOT be ringing voltage on a DID trunk--from either end. DIDs do > not use ringing voltage to indicate a call, they simply go off-hook, and > send the digits. > > E&M was invented for analog, and thus is it totally usable for analogue tie > trunks. Problem there (aside from the fact that it's an ancient technology) > is whether you're using Type I, II, III, IV or V Tie trunks (which are all a > bit different, up to and including the number of wires). I am almost certain > that no one has made an open-source analogue tie trunk card, and even closed > source/licensed cards (such as Dialogic) might be tough to find. > > 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. > > Oh, and with respect to Aliant, I suspect that they a) are not actually > giving you a DID trunk, and b) don't know exactly what it is they're sending > you, since they've used the catch-all "technically impossible" line on ya > ;-) > > -- > Jim Van Meggelen > [EMAIL PROTECTED] > http://www.oreillynet.com/pub/au/2177 > > "A child is the ultimate startup, and I have three. > This makes me rich." > Guy Kawasaki > -- > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] > > Sent: February 8, 2006 9:40 AM > > To: [email protected] > > Subject: RE: [on-asterisk] DID lines > > > > Ouch. This is getting ominous. I see what you mean. The DID > > lines would be a form of FXS line. > > > > I thought I saw mention of a conversion box somewhere. Maybe > > I'm thinking of the one for the proprietary phones though. > > There must be a solution to this, other than PRI I mean. The > > weird thing is that there is ring voltage when the call comes > > in on the DID trunk. Since we are supplying the voltage to > > the line, I guess I have to assume that the ring is coming > > from our equipment. This definitely got me started on the > > wrong tangent for the project so I'm not even sure how the > > DID is supposed to work > > > > Thanks for the input though. I'll be wracking the old brain > > today. E&M Wink start only applies to T1s right? > > > > Regards, > > Peter M. > > ******************************************************** 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! *****************************************************************
