Zaptel and zapata to match T1/RobbedBit telco

Hello,

Our provider is configuring the trunks we order as follow:

B8ZS
ESF
Glare Yield = off
ANIDNIS* ….DNIS = 10 digits
Inbound signalling = E&M immediate
outbound signaling = Wink Start

Fine for coding and framing, but what more do I need regarding the E&M immediate and the Wink start ?
I’m anticipating our upcoming iPBX, by trying to prepare as much things as I can.

Thanks !

Vincent.

zaptel.conf:
span=1,1,0,esf,b8zs
e&m=1-24

zapata.conf:
signalling=featd
channel => 1-24

This should work. May have to put “immediate=yes” in there too.

Hi !

I tried this, as well as many combinations but no luck so far.
I’m ending with:

Jan 19 15:54:50 VERBOSE[19987] logger.c:     -- Executing Dial("SIP/2707-008871e0", "ZAP/g4/2645|300|r") in new stack
Jan 19 15:54:50 DEBUG[19987] chan_zap.c: Dialing '2645'
Jan 19 15:54:50 DEBUG[19987] chan_zap.c: Deferring dialing...
Jan 19 15:54:50 DEBUG[19942] channel.c: Avoiding initial deadlock for 'Zap/125-1'
Jan 19 15:54:50 VERBOSE[19987] logger.c:     -- Called g4/2645
Jan 19 15:54:51 DEBUG[19987] chan_zap.c: Exception on 132, channel 125
Jan 19 15:54:51 DEBUG[19987] chan_zap.c: Got event Ring/Answered(2) on channel 125 (index 0)
Jan 19 15:54:51 DEBUG[19942] channel.c: Avoiding initial deadlock for 'Zap/125-1'
Jan 19 15:54:51 VERBOSE[19987] logger.c:     -- Zap/125-1 answered SIP/2707-008871e0
Jan 19 15:54:51 DEBUG[19987] chan_zap.c: Exception on 132, channel 125
Jan 19 15:54:51 DEBUG[19987] chan_zap.c: Got event On hook(1) on channel 125 (index 0)
Jan 19 15:54:51 DEBUG[19987] chan_zap.c: disabled echo cancellation on channel 125
Jan 19 15:54:51 DEBUG[19987] channel.c: Didn't get a frame from channel: Zap/125-1
Jan 19 15:54:51 DEBUG[19987] channel.c: Bridge stops bridging channels SIP/2707-008871e0 and Zap/125-1
Jan 19 15:54:51 DEBUG[19987] chan_zap.c: Hangup: channel: 125 index = 0, normal = 132, callwait = -1, thirdcall = -1

It looks like inbound and outbound signaling is different. What should I put to match outbound signaling ?

Here is for info my zaptel.conf:

[code]# Span 1: TE4/1/1 "T4XXP (PCI) Card 1 Span 1"
span=1,1,1,ccs,hdb3
bchan=1-15,17-31
dchan=16

Span 2: TE4/1/2 “T4XXP (PCI) Card 1 Span 2”

span=2,2,1,ccs,hdb3
bchan=32-46,48-62
dchan=47

Span 3: TE4/1/3 “T4XXP (PCI) Card 1 Span 3”

span=3,3,1,ccs,hdb3
bchan=63-77,79-93
dchan=78

Span 4: TE4/1/4 “T4XXP (PCI) Card 1 Span 4”

span=4,4,1,ccs,hdb3
bchan=94-108,110-124
dchan=109

Span 5: TE4/0/1 “T4XXP (PCI) Card 0 Span 1”

span=5,0,1,esf,b8zs
e&m=125-148
#clear=125-148

Span 6: TE4/0/2 “T4XXP (PCI) Card 0 Span 2”

span=6,0,1,ccs,hdb3
bchan=149-163,165-179
dchan=164

Span 7: TE4/0/3 “T4XXP (PCI) Card 0 Span 3”

span=7,0,1,ccs,hdb3
bchan=180-194,196-210
dchan=195

Span 8: TE4/0/4 “T4XXP (PCI) Card 0 Span 4”

span=8,0,1,esf,b8zs
e&m=211-234

Global data

loadzone = us
defaultzone = us[/code]

and the relevant zapata.conf section :

[quote]group=4
switchtype=national

;signalling=e911
;signalling=featdmf_ta
;signalling=featb
;signalling=featd
signalling = em_w
;signalling=em

prewink=50
preflash=50
wink=150
flash=750
start=1500
rxwink=300
rxflash=300
debounce=600

immediate=yes

;outsignalling=em_w
;outsignalling=featd

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0

channel=>125-147
[/quote]

Everything looks good in asterisk:

*CLI> zap show status Description Alarms IRQ bpviol CRC4 T4XXP (PCI) Card 1 Span 1 OK 0 0 0 T4XXP (PCI) Card 1 Span 2 RED 0 0 0 T4XXP (PCI) Card 1 Span 3 RED 0 0 0 T4XXP (PCI) Card 1 Span 4 RED 0 0 0 T4XXP (PCI) Card 0 Span 1 OK 0 0 0 T4XXP (PCI) Card 0 Span 2 RED 0 0 0 T4XXP (PCI) Card 0 Span 3 RED 0 0 0 T4XXP (PCI) Card 0 Span 4 RED 0 0 0
What debug options are available ? Is ther an equivalent to pri intense debug for e&m channels ?

Thanks.

On that outbound call, the far end hungup as per this message:
Jan 19 15:54:51 DEBUG[19987] chan_zap.c: Got event On hook(1) on channel 125 (index 0)

Try changing your configuration to:
zaptel.conf:
span=1,1,0,esf,b8zs
e&m=1-24

zapata.conf:
signalling=featd
group=1
channel => 1-12
signalling=em_w
group=2
channel => 13-24

Then dial out on group 2 so it uses e&m with wink.

Hello again !

That’s fast exchanges ! Thanks.

I tried what you advised. I also switched the complete group to e&m:

[code]; Span 5: TE4/0/1 "T4XXP (PCI) Card 0 Span 1"
group=4
switchtype=national

signalling = em_w

prewink=50
preflash=50
wink=150
flash=750
start=1500
rxwink=300
rxflash=300
debounce=600

immediate=no

usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes

channel=>125-148
[/code]

Tried several immediate settings also… same results unfortuantely
Getting puzzled…

You can always call Digium support. 256-428-6161

Hello again,

I have sent a mail to digium.

Here is some more info on the behavior we would liek to reproduce:

-asterisk should set the signaling bits (off-hook) for a call to the device
-The device winks back (50 to 100ms)
-Device goes off hook

Asterisk to yield to glare

This should be R2 signaling mode.

Any clues on what I should tweak ?

Thanks.