Sorry for my very delayed response. To answer a few questions: 1. Right, the *ANI*DNIS* is not working correctly. When the telco sends it, we are always missing the beginning of it. I almost always get a 7 digit ani, but sometimes it is 8 or 6.
2. The phone company assured me several times that we are not set up for feature group d. I tried anyway and it had the same affect. "Got a non-Feature Group D input on channel 77. Assuming E&M Wink instead".. Pretty smart. 3. I've also triad featb featdmf and featdmf_ta. All of which were the same or much works. Featb atcually crashed my polycom phone when I tried to dial into the pbx. :) 4. I didn't try 5ess as were are not using a pri. After this whole ordeal, where contemplating having all our t1's switched to pri. That would really be a bad thing, but its a pretty drastic measure. 5. The callerid issue is partially solved. I handled it with CALLERID=$DID. The main phone system runs a perl script to parse, and handle the rest of it. Which actually I like this better, because I don't have to setup extensions for every DNIS.. I have about 50 of them. We are still having the same signaling issue with both XO and GBX. Heres the problem I'm getting in asterisk. 1. A wink issue "Nov 19 05:35:06 DEBUG[12565] chan_zap.c: Got wink in weird state 4 on channel 92" 2. Calls that drop randomly Nov 19 12:29:51 DEBUG[15370] channel.c: Avoiding initial deadlock for 'SIP/1026-b7901568' Nov 19 12:31:02 DEBUG[22546] channel.c: Didn't get a frame from channel: SIP/1026-b7901568 Nov 19 12:31:02 DEBUG[22546] channel.c: Bridge stops bridging channels SIP/1026-b7901568 and Zap/1-1 3. Two phone companies that say I'm sending too many winks went the seizure, and a Digium rep who says it should just work. I am shot... Surely I can't be the only person who has this problem. Is there anyone else not using PRI, who had issues like this.?? Dan Jon Weisman wrote: > Dan, > > What happen w/ this? Did you figure it out? I've setup w/ XO using ESF/B8ZS, > and 5ESS for the switchtype, worked great and got the ANI as well. I dont > think you can get ANI on E&M Wink trunks, how about feature group d? > > -Jon > > > ----- Original Message ----- > From: "Dan Casey" <[EMAIL PROTECTED]> > To: <asterisk-users@lists.digium.com> > Sent: Friday, November 02, 2007 9:47 AM > Subject: [asterisk-users] Route an incoming call by ANI*DNIS > > > >> does anyone know how to route a call coming in with ANI*DNIS* >> >> Oct 31 12:47:41 VERBOSE[30056] logger.c: -- Executing >> Set("Zap/49-1", "DID=1231234*4812*") in new stack >> >> >> >> I tried making a route for _.*4812* but that matched everything rather >> then just the dnis i wanted.. any ideas? >> >> I would preferably like pass the callerid along to my extensions, but >> for now the important thing is routing. >> >> >> Thanks >> >> _______________________________________________ >> --Bandwidth and Colocation Provided by http://www.api-digital.com-- >> >> asterisk-users mailing list >> To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> >> > > > > _______________________________________________ > --Bandwidth and Colocation Provided by http://www.api-digital.com-- > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users