Debug and less logs by filtering

To debug an issue it is always easier to focus on our source and destination. No one likes to dig into a lot of unwanted text.
I found out this by an accident and had forgotten about that a few time. Solution is simple. I show only an example.

configuration as below

call filter match-list 1 voice
incoming calling-number 442248123

and enable debugging (example)

debug condition match-list 1 exact-match
debug ccsip calls

what you will see is

show debug
CCSIP SPI: SIP Call Statistics tracing is enabled (filter is ON)

Just short, simple and so useful. You will see in logs only what you need. To match by other values just see documentation.

Meridian 1 and VWIC2-2BRI integration

A few years ago I had tested integration between Nortel Meridian 1 PBX and Cisco CallManager 3.1 using router with voice card.

I found my notes from that implementation, as I remember discovery of that solution was pretty difficult.

1. Config on Cisco GW using H.323 was pretty standard so I skip that detail.

2. Meridian 1 PBX requires specific card – in that case it was 8 ISDN ports card – SILC NT6D70.

3. Another step it’s to configure Meridian 1 under LD27 as below:


REQ NEW
TYPE DSL
DSL 8 0 1 0
APPL BRIL
DES BRI
CUST 0
MODE NTFS
B1CT VCE DTA
B2CT VCE DTA
LDN NO
XLST 2
MTEI 8
MCAL 16
MTSP 8
LAPD 2
PRID 2
PDCA 3
FDN
EFD
HUNT
EHT
TGAR 0
NCOS 7
SCPW
SGRP 0
CAC_MFC 3
CLS UNR ICDD CDMD MRD UDI ABDD PGND

REQ NEW
TYPE TSP
DSL 8 0 1 0
USID 0
SUPL_SVC
DN 3992
CT VCE DTA
MCAL 4
CLIP YES
PRES YES
COLP NO
TRANS NO
FEAT HTD FND SFD CFTD MWD FBD HBTD CFXD DN03 DNDY
SSRV_ETSI
DN
DFDN 3992

4. At this moment ip phones should be reachable under e.x. 3992 extension. If needed change IDC as I remember under LD49.

5. Another step is to bind SILC ports to one trunk and attach to trunk (LD15, LD16) with a range of extensions 10 or 100.

Nortel Merdian 1 is almost an antique, but from time perspective comparing to other vendors PBX this one is outstanding, so it still may be helpful to use a solution as above.

Dial peer selection

Sometimes there is a need to configure more complicated configuration for incoming or outgouing calls. It’s good to remember what is an order of dial-peer’s selection by matching epcific elements. So it selects as below:

1. incoming called-address

2. answer-address

3. destination-pattern

4. voice-port

In the case of some issues start debug remembering that it is enough for gateway to match one of those elements.

From MSN to DDI

I really hate when customer plays unfair – doing big change in services without notice. It was this time with approximatelly 30 remote offices each with 2 bri interfaces.

In the half of them we met an issue. Conections wasn’t established properly. After searches solution was to reconfigure bri interfaces as below

isdn tei-negotiation first-call
isdn tei-negotiation power
isdn tei-negotiation powerup
isdn static-tei 0

Important: clear interface

update: difference may look like below

ISDN BRI0/3/0 interface
dsl 12, interface ISDN Switchtype = basic-net3
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 12 CCBs = 0
The Free Channel Mask: 0x80000003
ISDN BRI0/3/1 interface
dsl 13, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 13 CCBs = 0
The Free Channel Mask: 0x80000003
Total Allocated ISDN CCBs = 0


and example how doesn’t look like during a call

ISDN BRI0/2/1 interface
dsl 9, interface ISDN Switchtype = basic-net3
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
CCB:callid=8052, sapi=0, ces=1, B-chan=1, calltype=DATA, hdlctype=HDLC-TRUNK
Active dsl 9 CCBs = 1
The Free Channel Mask: 0x80000002
Total Allocated ISDN CCBs = 1