RE: [Asterisk-Users] WM Wink timings for Nortel

2005-02-19 Thread Dennis Walker
I had a simular problem receiveing EM 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:[EMAIL PROTECTED]
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] WM Wink timings for Nortel

Rich Adamson wrote:

 My guess is the asterisk implementation for EM 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 EM emulation, and even higher probability the code can
 not source an EM 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 EM 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

___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-19 Thread Keith O'Brien








 EM is analogue, not digital...



Not true. You can have EM 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 EM 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 isnt 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_note09186a00800e2560.shtml








___
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] WM Wink timings for Nortel

2005-02-18 Thread Eric Wieling
Does anyone know the default EM 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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Brian McSpadden
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 [EMAIL PROTECTED] wrote:
 Does anyone know the default EM 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

___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Rich Adamson
 Does anyone know the default EM 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 EM 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).


___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Eric Wieling
Correct.  Incoming DID calls on the EM/Wink channels fail about 1/2 
to 1/3 of the time.

Brian McSpadden wrote:
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 [EMAIL PROTECTED] wrote:
Does anyone know the default EM 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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Eric Wieling
Rich Adamson wrote:
Does anyone know the default EM 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 EM 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).
The Digium Tx00P and TE*xxxP support EM Wink.
___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Andrew Kohlsmith
On February 18, 2005 12:32 pm, Rich Adamson wrote:
 I'm confused. Digium cards do not support EM 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).

Uh... my zapata and zaptel.conf exmaple files both show EM signaling options.  
I'm no telephony expert but I though that EM signaling was just buried in the 
RBS bits like any other CAS T1 signaling.

-A.
___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Brancaleoni Matteo
Hi,

Il giorno ven, 18-02-2005 alle 12:44 -0600, Eric Wieling ha scritto:
 The Digium Tx00P and TE*xxxP support EM Wink

EM is analogue, not digital...
digium cards support it over digital, like they supports fxs/fxo
to a channel bank . same from EM
The interface described here is analogue, afaik.

Matteo.
-- 

___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Eric Wieling
Brancaleoni Matteo wrote:
Hi,
Il giorno ven, 18-02-2005 alle 12:44 -0600, Eric Wieling ha scritto:
The Digium Tx00P and TE*xxxP support EM Wink

EM is analogue, not digital...
digium cards support it over digital, like they supports fxs/fxo
to a channel bank . same from EM
The interface described here is analogue, afaik.
Well it's coming on a T-1.
___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Richard Lyman
Eric Wieling wrote:
Rich Adamson wrote:
Does anyone know the default EM 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 EM 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).

The Digium Tx00P and TE*xxxP support EM Wink.
___
i've not tested the TE4xxP yet, but the T400P does EM Immediate 
start also.

___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Rich Adamson
 On February 18, 2005 12:32 pm, Rich Adamson wrote:
  I'm confused. Digium cards do not support EM 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).
 
 Uh... my zapata and zaptel.conf exmaple files both show EM signaling 
 options.  
 I'm no telephony expert but I though that EM signaling was just buried in 
 the 
 RBS bits like any other CAS T1 signaling.

When I responded to Eric's original post, it sounded like he was trying
to interface to an older pbx trunk interface (physical interface).
Those physical EM interfaces were as described above (each had either
four or six wires).

What the original post didn't say was the interface to the non-asterisk
pbx was a T1, and one (or more) of the channels were configured for EM
signaling. Completely different then a physical EM interface. (Someone
else had asked about a physical interface not more then a couple of
weeks ago, so the mind was oriented along those lines.)


___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Eric Wieling
Rich Adamson wrote:
On February 18, 2005 12:32 pm, Rich Adamson wrote:
I'm confused. Digium cards do not support EM 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).
Uh... my zapata and zaptel.conf exmaple files both show EM signaling options.  
I'm no telephony expert but I though that EM signaling was just buried in the 
RBS bits like any other CAS T1 signaling.

When I responded to Eric's original post, it sounded like he was trying
to interface to an older pbx trunk interface (physical interface).
Those physical EM interfaces were as described above (each had either
four or six wires).
What the original post didn't say was the interface to the non-asterisk
pbx was a T1, and one (or more) of the channels were configured for EM
signaling. Completely different then a physical EM interface. (Someone
else had asked about a physical interface not more then a couple of
weeks ago, so the mind was oriented along those lines.)
The original setup was:
CLEC CT1 - Channel Bank - (analog) - Nortel PBX.
Current setup is:
CLEC CT1 - Astrisk - CT1 - Channel Bank (analog) - Nortel PBX.
The Nortel does not have T-1 interfaces in it and the company is 
unwilling to buy a T-1 card for the Nortel.

Only 4 channels of the T-1 are EM Wink (they are for DIDs), the rest 
of the channels are various other things.  For the voice channels that 
we care about we terminate the channels into Asterisk.  For channels 
we don't care about we use the Zappel DACS stuff to just patch the 
channels thru.

Channels 9 - 12 are the EM Wink channels.  This is what we see:
Failure #1:
-- Starting simple switch on 'Zap/9-1'
Feb 18 16:13:25 WARNING[1965]: chan_zap.c:4723 ss_thread: getdtmf on 
channel 9: Operation now in progress
-- Hungup 'Zap/9-1'
-- Starting simple switch on 'Zap/10-1'
Feb 18 16:13:29 WARNING[1966]: chan_zap.c:4723 ss_thread: getdtmf on 
channel 10: Operation now in progress
-- Hungup 'Zap/10-1'

Failure #2
-- Starting simple switch on 'Zap/9-1'
Feb 18 16:13:25 WARNING[1965]: chan_zap.c:4723 ss_thread: getdtmf on 
channel 9: Operation now in progress
-- Hungup 'Zap/9-1'
-- Starting simple switch on 'Zap/10-1'
-- Executing NoOp(Zap/10-1, EXTEN=189) in new stack
-- Executing Dial(Zap/10-1, Zap/G3/189||g) in new stack
-- Called G3/189

In Failure #2 the calls still go thru, as you can see.
As you can see when a call suceeds I do not see the getdtmf WARNING 
message.

We have no problems sending calls to the channel bank, only getting 
them from the CLEC.  Since the CLEC used to be directly connected to 
the channel bank and then to the Nortel I want to get the wink timings 
for the nortel to see if making Asterisk match the Nortel settings 
make any difference.

--Eric
___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Rich Adamson
 I'm confused. Digium cards do not support EM 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).
 
 Uh... my zapata and zaptel.conf exmaple files both show EM signaling 
 options.  
 I'm no telephony expert but I though that EM signaling was just buried in 
 the 
 RBS bits like any other CAS T1 signaling.
  
  
  When I responded to Eric's original post, it sounded like he was trying
  to interface to an older pbx trunk interface (physical interface).
  Those physical EM interfaces were as described above (each had either
  four or six wires).
  
  What the original post didn't say was the interface to the non-asterisk
  pbx was a T1, and one (or more) of the channels were configured for EM
  signaling. Completely different then a physical EM interface. (Someone
  else had asked about a physical interface not more then a couple of
  weeks ago, so the mind was oriented along those lines.)
 
 The original setup was:
 
 CLEC CT1 - Channel Bank - (analog) - Nortel PBX.
 
 Current setup is:
 
 CLEC CT1 - Astrisk - CT1 - Channel Bank (analog) - Nortel PBX.
 
 The Nortel does not have T-1 interfaces in it and the company is 
 unwilling to buy a T-1 card for the Nortel.
 
 Only 4 channels of the T-1 are EM Wink (they are for DIDs), the rest 
 of the channels are various other things.  For the voice channels that 
 we care about we terminate the channels into Asterisk.  For channels 
 we don't care about we use the Zappel DACS stuff to just patch the 
 channels thru.
 
 Channels 9 - 12 are the EM Wink channels.  This is what we see:
 
 Failure #1:
 
 -- Starting simple switch on 'Zap/9-1'
 Feb 18 16:13:25 WARNING[1965]: chan_zap.c:4723 ss_thread: getdtmf on 
 channel 9: Operation now in progress
 -- Hungup 'Zap/9-1'
 -- Starting simple switch on 'Zap/10-1'
 Feb 18 16:13:29 WARNING[1966]: chan_zap.c:4723 ss_thread: getdtmf on 
 channel 10: Operation now in progress
 -- Hungup 'Zap/10-1'
 
 Failure #2
 -- Starting simple switch on 'Zap/9-1'
 Feb 18 16:13:25 WARNING[1965]: chan_zap.c:4723 ss_thread: getdtmf on 
 channel 9: Operation now in progress
 -- Hungup 'Zap/9-1'
 -- Starting simple switch on 'Zap/10-1'
 -- Executing NoOp(Zap/10-1, EXTEN=189) in new stack
 -- Executing Dial(Zap/10-1, Zap/G3/189||g) in new stack
 -- Called G3/189
 
 In Failure #2 the calls still go thru, as you can see.
 
 As you can see when a call suceeds I do not see the getdtmf WARNING 
 message.
 
 We have no problems sending calls to the channel bank, only getting 
 them from the CLEC.  Since the CLEC used to be directly connected to 
 the channel bank and then to the Nortel I want to get the wink timings 
 for the nortel to see if making Asterisk match the Nortel settings 
 make any difference.

Since you're really dealing with signaling bits embedded in the T1
stream, my original comments relative to the physical interface obviously
don't apply.

In the old EM physical interfaces, the E lead represented signaling
coming from the world (sort of E = everyone) to you, and the M lead
was you signaling to the world (sort of M = me). The two leads were
used to solve loop signaling issues, handle answer supervision, dial
pulse signaling, trunk startup, etc. The audio path was either two-wire
(eg, pbx interface) or four-wire (eg, LD circuits). I don't recall
any config options (from my telephony engineering days) relative to
wink duration, or any other timing adjustments.

My guess is the asterisk implementation for EM 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 EM emulation, and even higher probability the code can 
not source an EM 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.

Rich



___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Eric Wieling
Rich Adamson wrote:
My guess is the asterisk implementation for EM 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 EM emulation, and even higher probability the code can 
not source an EM 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 EM 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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Steve Underwood
Hi Eric,
Eric Wieling wrote:
Does anyone know the default EM 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
___
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


Re: [Asterisk-Users] WM Wink timings for Nortel

2005-02-18 Thread Eric Wieling
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?
___
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