VoIP Mailing List Archives

[Guest]

Hi all,

I'm trying to insert a Rhino Ceros box equipped with a Rhino R2T1
dual-T1 card and running the latest version of Trixbox (2.4.2) between
the central office and a Nortel Option 11. The switch at the CO is a
DMS100. Basically, I'm taking the T1, connecting it to port 0 on the
R2T1 card, and then connecting port 1 to the Nortel. (Actually a CSU and
then the Nortel) We're running PRI over T1... Channels 1-23 are B and
channel 24 is D.

So I configured the system ahead of time with line encoding, line
length, switchtype, timing source, etc. The timing source on port 0 in
Zaptel.conf is '1' so I get timing from the CO and it is '0' on port 1
so I send timing to the Nortel. When I hooked it up over the weekend,
the spans came up as expected with no errors or anything.

Calls between the Asterisk box and the CO work like a charm. The CO
doesn't know it's talking to a different box and I get everything I
need, call ID, DID, etc with no problems at all. But the calls between
the Asterisk box and the Nortel will not go through. I enabled debug on
that span and placed calls both ways. When I call from the Nortel to the
Asterisk box, the PRI debug shows the call failed with cause code 100.
Based on what I can find, this looks like the Nortel is mad about the
formatting of something in the messages. When I reverse that and call
from the Asterisk box to the Nortel, those calls fail with a cause code
of 54. Best I can tell that means 'incoming call barred' but how could
it be barred? The Asterisk box should look like the DMS100 to the
Nortel. I duplicated the calling information I was seeing from the CO
when I tried to call the Nortel plus I tried a couple of variants... no
dice. Am I missing something here?

I don't understand how I can be talking to a real DMS100 on one T1 and
it works perfect but when I act like a DMS100 on the other T1, the
Nortel is getting mad. Can anyone offer some ideas? Maybe a
clarification on these cause codes? My depth of knowledge in this area
isn't that deep... a wading pool at best... so I'm hoping one of you
guys that has worked with this stuff a long time might be able to give
me some direction.

I'm posting below Zaptel, Zapata, and a CLI dump of a call from the
Nortel into the Asterisk system with pri debug span turned on.

TIA!
Jason
# Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#

# It must be in the module loading order


# Span 2: R2T1/0/1 "R2T1 (PCI) Card 0 Span 1"
span=2,1,0,esf,b8zs
# termtype: cpe
bchan=1-23
dchan=24

# Span 3: R2T1/0/2 "R2T1 (PCI) Card 0 Span 2"
span=3,0,0,esf,b8zs
# termtype: net
bchan=25-47
dchan=48

# Span 4: Rhino RCB8FXX/1 "Rhino RCB8FXX/1"
fxsks=49
fxsks=50
fxoks=51
fxoks=52
# ??: 53 ---/1/4
# ??: 54 ---/1/5
# ??: 55 ---/1/6
# ??: 56 ---/1/7

# Global data

loadzone = us
defaultzone = us

------------------------------------------------------------------------
------------------------------------------------------------------------

; Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is
intended
; to be #include-d by /etc/zapata.conf that will include the global
settings
;

; Span 2: R2T1/0/1 "R2T1 (PCI) Card 0 Span 1"
group=0
context=from-trunk
switchtype = dms100
signalling = pri_cpe
channel => 1-23

; Span 3: R2T1/0/2 "R2T1 (PCI) Card 0 Span 2"
group=1
context=from-trunk
switchtype = dms100
signalling = pri_net
channel => 25-47

; Span 4: Rhino RCB8FXX/1 "Rhino RCB8FXX/1"
;;; line="49 FXO/1/0"
signalling=fxs_ks
callerid=asreceived
group=3
context=from-pstn
channel => 49
context=default

;;; line="50 FXO/1/1"
signalling=fxs_ks
callerid=asreceived
group=3
context=from-pstn
channel => 50
context=default

;;; line="51 FXS/1/2"
signalling=fxo_ks
callerid="Channel 51" <6051>
mailbox=6051
group=5
context=from-internal
channel => 51
callerid=
mailbox=
group=
context=default

;;; line="52 FXS/1/3"
signalling=fxo_ks
callerid="Channel 52" <6052>
mailbox=6052
group=5
context=from-internal
channel => 52
callerid=
mailbox=
group=
context=default

; ??: 53 ---/1/4
; ??: 54 ---/1/5
; ??: 55 ---/1/6
; ??: 56 ---/1/7

------------------------------------------------------------------------
------------------------------------------------------------------------

< Protocol Discriminator: Q.931 ( len=39
< Call Ref: len= 1 (reference 21/0x15) (Originator)
< Message type: SETUP (5)
< [04 03 80 90 a2]
< Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer
capability: Speech (0)
< Ext: 1 Trans mode/rate: 64kbps,
circuit-mode (16)
< Ext: 1 User information layer 1: u-Law
(34)
< [18 04 e9 80 83 15]
< Channel ID (len= 6) [ Ext: 1 IntID: Explicit PRI Spare: 0
Exclusive Dchan: 0
< ChanSel: Reserved
< Ext: 1 DS1 Identifier: 0
< Ext: 1 Coding: 0 Number Specified Channel
Type: 3
< Ext: 0 Channel: 21 ]
< [6c 0c 21 80 36 31 34 38 38 38 32 33 34 34]
< Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
< Presentation: Presentation permitted, user
number not screened (0) 'xxxxxxxxxx' ]
< [70 08 a1 33 33 32 39 31 37 37]
< Called Number (len=10) [ Ext: 1 TON: National Number (2) NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
'xxxxxxx' ]
-- Making new call for cr 21
-- Processing Q.931 Call Setup
-- Processing IE 4 (cs0, Bearer Capability)
-- Processing IE 24 (cs0, Channel Identification)
-- Processing IE 108 (cs0, Calling Party Number)
-- Processing IE 112 (cs0, Called Party Number)
q931.c:3298 q931_receive: call 21 on channel 21 enters state 6 (Call
Present)
q931.c:2571 q931_call_proceeding: call 21 on channel 21 enters state 9
(Incoming Call Proceeding)

[stotaro at totarotechn...]

On Mon, Mar 3, 2008 at 2:19 PM, Gleim, Jason <jgleim at ats-ohio.com> wrote: