bill black
2005-Apr-25 16:55 UTC
[Asterisk-Users] T1 E&M wink issues - bad int'l dial-outandoccasional dropped calls
OK. The latest debug from Qwest is that our 'Nature of Address' field is not being set properly for international calls. He said that this is something specified by our switch but could not give details and it is not simply keying 011. With E&M wink, what else is there besides for DTMF? How do we specifiy a Nature of Address field with E&M wink? Thanks, Bill jltaylor wrote:>OK, so you are either D4/ami or B8ZS/esf, and you're doing E&M wink. >And, you have a T1 cable from the Cisco to the Asterisk. >And, the Cisco is set for channelized T1, 8 channels using RBI. >In your zapata.conf you have chosen: signalling=em_w. > >Can you get someone at Qwest to watch while your dial? >If they know what trunk you are on then they can capture it. > >Have you turned SIP or IAX2 debug on and examined any messages while >dialing? > >So do you have to setup the dial string: 00001NXXNXXXXXX ? > >Have you asked Qwest if they support any other type of signaling (Feature >Group?). > >I had a problem with ISDN BRI going to a Terminal Adapter and splitting to >to analog lines. >Lines would "hang" off hook. >Calls would drop. >I changed to two analog business lines and the problems stopped. >I think that we were not getting proper CPC. > > > > >-----Original Message----- >From: asterisk-users-bounces@lists.digium.com >[mailto:asterisk-users-bounces@lists.digium.com]On Behalf Of bill black >Sent: Sunday, April 24, 2005 3:00 PM >To: asterisk-users@lists.digium.com >Subject: Re: [Asterisk-Users] T1 E&M wink issues - bad int'l >dial-outandoccasional dropped calls > > >Customer has integrated access arrangement with 16 channels of data/8 >for voice that is split via customer cisco equipment. No local dialing, >LD and incoming 800 service only via the t1. Qwest provides both the >local loop and LD/800 service but it is provided via re-seller PNG. > >We have verified clock integrity via cisco logs that show no frame slips >(cisco uses CO as a reference and we use the cisco as a reference.) > >No reference to Feature Group A (or D for that matter) is on our paperwork. > >It is nearly a rural location so I'm guessing we are connected via an >End Office but can check this. > >Bill > >jltaylor wrote: > > > >>What kind of service did you subscribe to (what do they call it on your >>bill)? >>Retail business trunks? >>Feature Group A? >>Can you dial "local" numbers or is this all long distance? >>Is Qwest the LEC or a long distance provider for this service? >>Are you connected to an End Office or a Tandem? >> >>These all may give me a hit as to what is going on. >>James >> >>-----Original Message----- >>From: asterisk-users-bounces@lists.digium.com >>[mailto:asterisk-users-bounces@lists.digium.com]On Behalf Of bill black >>Sent: Sunday, April 24, 2005 10:45 AM >>To: asterisk-users@lists.digium.com >>Subject: [Asterisk-Users] T1 E&M wink issues - bad int'l dial-out >>andoccasional dropped calls >> >> >>Anyone have any ideas here? >> >>We are using 8 channels of E&M Wink with a T100P for outgoing LD and >>incoming tollfree numbers and are apparently connected to a Nortel >>DMS-250 at the CO. We are receiving ANI & DNIS just fine and can >>dial-out domestically with DTMF but have two issues that are still >>unresolved: >> >>1) We cannot dial-out internationally with an 011 prefix (or any other >>prefix that we can think of). Qwest claims (1) they never get >>international calls and (2) domestic calls are routed to their LD >>service as 00001NXXNXXXXXX instead of 1NXXNXXXXXX. Is some form of >>prefix/suffix needed for DTMF dialing over an E&M wink channel? (e.g. >>something like the *ANI*DNIS* for incoming.) 011 clearly doesn't work as >>a prefix and Qwest's response has invariably been 'there is something >>wrong with your PBX' :( Curiously if we follow an >>011+international-number with a * we get a recording that we have not >>entered sufficient digits to complete the call whereas without the * we >>just get a congestion beep from the far end. >> >>2) Once or twice a day the customer is getting calls dropped. The log >>shows the following: >> >>Apr 21 13:15:51 VERBOSE[22664]: -- Hungup 'Zap/7-1' >>Apr 21 13:15:52 VERBOSE[22664]: -- Starting simple switch on >>'Zap/7-1' Apr 21 13:15:53 WARNING[22664]: getdtmf on channel 7: >>Operation now in progress >>Apr 21 13:15:53 VERBOSE[22664]: -- Hungup 'Zap/7-1' >> >>It appears that we see the line go back on-hook, hangup but then see it go >>off-hook again and treat it as another incoming call that never gets a DTMF >>input when in fact the call has just been dropped. We've verified that we >>are not sharing interrupts, we are on run level 3 etc. zttest shows (so >> >> >far) > > >>a minimum of 99.987%. Can anyone think of what might be causing this or >>what we could ask Qwest regarding possible diagnostics? >> >>3) Finally, what level of dropped calls is generally considered acceptable? >>Like the dead-pixel issue with LCDs this is pretty subjective but is there >>an industry number that is typical? (We are presently at ~1% due to this >>issue.) >> >>Thanks to all for any shared wisdom. Bill >> >> >> >> >> >>_______________________________________________ >>Asterisk-Users mailing list >>Asterisk-Users@lists.digium.com >>http://lists.digium.com/mailman/listinfo/asterisk-users >>To UNSUBSCRIBE or update options visit: >> http://lists.digium.com/mailman/listinfo/asterisk-users >> >> >> >> >> >> > >_______________________________________________ >Asterisk-Users mailing list >Asterisk-Users@lists.digium.com >http://lists.digium.com/mailman/listinfo/asterisk-users >To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > > >