Does anyone know the default E&M Wink timings for Nortel DID ports? The default settings on Asterisk are: ; prewink: Pre-wink time (default 50ms) ; preflash: Pre-flash time (default 50ms) ; wink: Wink time (default 150ms) ; flash: Flash time (default 750ms) ; start: Start time (default 1500ms) ; rxwink: Receiver wink time (default 300ms) ; rxflash: Receiver flashtime (default 1250ms) ; debounce: Debounce timing (default 600ms)
I assume the defaults do not work? I've successfully used the defaults with Avaya and Mitel switches with no problems. On Fri, 18 Feb 2005 10:04:09 -0600, Eric Wieling <eric@fnords.org> wrote:> Does anyone know the default E&M Wink timings for Nortel DID ports? > > The default settings on Asterisk are: > > ; prewink: Pre-wink time (default 50ms) > ; preflash: Pre-flash time (default 50ms) > ; wink: Wink time (default 150ms) > ; flash: Flash time (default 750ms) > ; start: Start time (default 1500ms) > ; rxwink: Receiver wink time (default 300ms) > ; rxflash: Receiver flashtime (default 1250ms) > ; debounce: Debounce timing (default 600ms) > > _______________________________________________ > 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 >
> Does anyone know the default E&M Wink timings for Nortel DID ports? > > The default settings on Asterisk are: > > ; prewink: Pre-wink time (default 50ms) > ; preflash: Pre-flash time (default 50ms) > ; wink: Wink time (default 150ms) > ; flash: Flash time (default 750ms) > ; start: Start time (default 1500ms) > ; rxwink: Receiver wink time (default 300ms) > ; rxflash: Receiver flashtime (default 1250ms) > ; debounce: Debounce timing (default 600ms)I'm confused. Digium cards do not support E&M trunks, which are older interfaces that include either a two-wire or four-wire audio "plus" two additional wires called the "E" and the "M" leads. So, Wink timing is irrelevant (unless I'm misunderstanding your question).
Hi Eric, Eric Wieling wrote:> Does anyone know the default E&M Wink timings for Nortel DID ports? > > The default settings on Asterisk are: > > ; prewink: Pre-wink time (default 50ms) > ; preflash: Pre-flash time (default 50ms) > ; wink: Wink time (default 150ms) > ; flash: Flash time (default 750ms) > ; start: Start time (default 1500ms) > ; rxwink: Receiver wink time (default 300ms) > ; rxflash: Receiver flashtime (default 1250ms) > ; debounce: Debounce timing (default 600ms)I had trouble with wink start (or delayed dial, or various other names for the same thing) a long time ago. I think the switch was an AXE. The spec said as soon as the seize came in I could start the wink. This turned out not to be true. I needed to wait a while, or the PSTN switch could fail to see the wink at all, even if I made it very long. From checking some old code it looks like finally I waited 100ms after the seize before winking. Of course, you have a different switch so the timings might be different, but extending the per-wink a bit seems work a try. Also, 140ms or 150ms is usually the minimum specified wink. It could be something is a bit borderline and a slightly longer wink is needed for reliability. Much longer winks are usually harmless. Another thing might be worth checking, although it seems silly at first sight. Some people pulse wink from 0->1->0, and some from 1->0->1. It seems like nothing should work if this is the wrong way around, but I have seen things half work when this is wrong. Regards, Steve
Steve Underwood wrote:> I had trouble with wink start (or delayed dial, or various other names > for the same thing) a long time ago. I think the switch was an AXE. The > spec said as soon as the seize came in I could start the wink. This > turned out not to be true. I needed to wait a while, or the PSTN switch > could fail to see the wink at all, even if I made it very long. From > checking some old code it looks like finally I waited 100ms after the > seize before winking. Of course, you have a different switch so the > timings might be different, but extending the per-wink a bit seems work > a try. Also, 140ms or 150ms is usually the minimum specified wink. It > could be something is a bit borderline and a slightly longer wink is > needed for reliability. Much longer winks are usually harmless. > > Another thing might be worth checking, although it seems silly at first > sight. Some people pulse wink from 0->1->0, and some from 1->0->1. It > seems like nothing should work if this is the wrong way around, but I > have seen things half work when this is wrong.What specific Asterisk options would I use to change these settings in Asterisk?
I had a simular problem receiveing E&M Wink dtmf signals from a MITEL sx200 digital. I had a 10% or so problem with astrisk line timing out before all the digits were dialed. I tried all the time outs and even messed with the timing of my MITEL switch. It turned out that the problems was solved by setting the emdigitwait variable in zapata.conf. I set mine to emdigitwait=600 and have had 0% dialing timeouts. This is a fairly new variable setting I think after 1.0.3. Before this it was a constant you would have to modify in chan_zap.c . If you google for asterisk emdigitwait you'll track down more information. ---------- From: Eric Wieling[SMTP:eric@fnords.org] Reply To: Asterisk Users Mailing List - Non-Commercial Discussion Sent: Friday, February 18, 2005 6:54 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] W&M Wink timings for Nortel Rich Adamson wrote:> My guess is the asterisk implementation for E&M signaling is probably > "one" end of that interface, watching the signaling bits and translating > those into something * can use to terminate the call. However, I'll > be the first to admit I'm not a programmer and probably wouldn't > recognize the code even if I seen it. Highly unlikely it is a > fully-baked E&M emulation, and even higher probability the code can > not source an E&M call. > > Do you know if the incoming DID digits are actually dtmf, or is it > possible the digits are dial pulse on the E lead? (I'd have to guess > dial pulse from the looks of those messages.) > > Since I have not personally heard of anyone actually using it, I'd have > to guess that resolving the problem will boil down to writing debug > code into asterisk, and then writing code that supports your needs. > Or, change the interface from asterisk to the Nortel to some other > trunking arrangement.Calls are working SOME of the time. The CLEC is sending DTMF, I've confirmed that. We can source E&M Wink calls, we cannot receive them reliability from the CLEC. I'll be playing with the various timing options this evening. _______________________________________________ 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
E&M is analogue, not digital... Not true. You can have E&M signaling on a T1 CAS interface. Likewise T1 CAS interfaces can also be setup for FXS and FXO signaling. This is just how the robbed bits communicate. With E&M wink before a remote switch sends a call to a local switch it send a very 0/1 transition on the A bit. When the local switch sees the wink it is supposed to respond with its own "wink" back at the originating switch. Then and only then is the call sent over and DTMF is sent inband. On T1s this wink parameter is tunable and you should be able to set the wink pulse width and timing. I suspect that the Digium card either isn't answering the wink or is sending it with the incorrect timing or pulse width. The best way to troubleshoot this is to place a T1 analyzer on the line such as Fireberd. They can be rented for a day from Electrorent. Also, you may want to see if you can setup the T1 span for immediate-start. This would mitigate any wink problems. For more info on how T1s work with voice see: http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a0080 0e2560.shtml -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050219/1a71845a/attachment.htm