Zhone IMACS Software FAQ
1. What are some of the causes of disconnect with voice mail systems?
Most issues coming from voice mail systems come from a failure to disconnect when the far end caller (the person leaving the message) hangs up. This can be an issue with any loop start line. To help prevent this issue, the FXS card can be set to lp-fd (loop forward disconnect). This feature will forward a disconnect signal toward the 2 wire side (analog side) of the FXS card. This will only occur if the switch at the other end of the T1 is set to forward the disconnect. This perimeter will vary from switch to switch, but should be at least 650 ms in duration.
Some PBX's and many Key systems will not detect a calling party disconnect, and will only disconnect when the called party disconnects. As you can see, when the called party is a voicemail or IVR system, this can be a problem, as they don't know when to hang up. The internal voicemail or IVR solution to the issue is to begin an internal disconnect process, usually with a lack of activity or sounds (voice or dtmf Keys) starting a process that will eventually drop the call. This does take time, and will tie up a trunk for 30 to 60 seconds depending on when and how silent the line becomes. Clicking and popping will be detected as voice energy, and many CO switches click and pop when the far end hangs up. Other ways Voice Mail or IVR systems disconnect is if they detect dial or howler tones, but again these ways of disconnecting will cause a longer disconnect interval.
Ground start lines are always the best when it comes to disconnecting, but they do cost more: for example, most key systems won't use them and most PBX's require a different module, which does add more expense. If you do use Ground start lines, be sure to ground the Vn+ on the DC connector of the IMAC's system to the same ground bus as the PBX to ensure proper grounding.
2. How do I view bus assignment status on older host versions of IMACS equipment?
Log on with GOD password. Go to the WAN menu Type "Z".
3. How do I troubleshoot RIP on the PM-IOR Card?
Simply telnet or terminal into the PM-IOR Card and type:
|
add filter rip
|
(hit enter)
|
|
set filter rip 1 permit udp src eq 520
|
(hit enter)
|
|
set console
|
(hit enter)
|
|
ptrace rip
|
(hit enter)
|
|
When done troubleshooting RIP type:
|
ptrace
|
(hit enter)
|
|
reset console
|
(hit enter)
|
|
4. Can I troubleshoot PPP on the PM-IOR Card?
Yes, simply terminal or telnet into the PM-IOR card and type:
|
set console
|
(hit enter)
|
|
set debug 0x51
|
(hit enter)
|
|
The PPP negotiation will be displayed to the terminal. When done logging data type:
|
set debug off
|
(hit enter)
|
|
reset console
|
(hit enter)
|
|
5. What does "On-Hook" mean?
"On-Hook" is an old telephone term, referring to the telephone handset set in its cradle, where the circuit is open. If using loop start signaling and the phone is on-hook then the signaling pattern of the AB bits will be "01" indicating an idle condition.
6. What does "Off-Hook" mean?
"Off-Hook" refers to the state of the telephone handset being removed from the cradle to place or receive a phone call. When the telephone goes off-hook, the subscriber loop is closed, and electrically signals back to the CO that the line is ready for use.
7. How do I look at the signaling bits on the FXS Card?
From the Main Menu arrow down to the FXS Card, and hit enter. Highlight the FXS Port in question and type 't' for test. You will see something like this:
|
|
1
|
2
|
3
|
4
|
5
|
6
|
7
|
8
|
|
TEST
|
off
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
|
Tx ABCD
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
|
Rx ABCD
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
|
T-R-CNTL
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
mon
|
|
TO USER
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
|
TO NTWK
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
|
Tx ABCD
|
0101
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
|
Rx ABCD
|
1111
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
|
T-R-CNTL
|
RbTg
|
RbTo
|
RbTo
|
RbTo
|
RbTo
|
RbTo
|
RbTo
|
RbTo
|
|
T-R-STAT
|
off
|
off
|
off
|
off
|
off
|
off
|
off
|
off
|
|
MODE
|
fxs
|
fxs
|
fxs
|
fxs
|
fxs
|
fxs
|
fxs
|
fxs
|
|
TYPE
|
loop
|
loop
|
loop
|
loop
|
loop
|
loop
|
loop
|
loop
|
|
STATUS
|
idle
|
noWAN
|
noWAN
|
noWAN
|
noWAN
|
noWAN
|
noWAN
|
noWAN
|
In this example we are looking at the signaling bits on Port 1. So, look at Column 1 and look at rows 7 and 8 'Tx ABCD' and 'Rx ABCD'. These indicate the ABCD bits; hit 'r' to refresh the screen to look at the signaling bits.
8. What type of encoding does the IMACS BRI Cards 826070, 826170 and 826270 use?
2B1Q, which is an encoding mechanism defined with 4 possible voltages (+3, +1, -1, -3). Each pulse represents two bits of information, named a quaternary.
|
Voltage
|
Bits
|
|
+3
|
10
|
|
+1
|
11
|
|
-1
|
01
|
|
-3
|
00
|
|
9. What is crosstalk?
Crosstalk occurs when signaling from one pair of wires interferes with signaling on another pair. The pairs effected are usually bound together in the same sheath. This occurs because as current flows through wire, an electromagnetic field is created; the stronger the frequency, the stronger the effect. Wire pairs are twisted, so that the opposing fields can cancel each other out. If the pairs are not tightly twisted, then this condition is most likely to occur. The first place to check if your installation is experiencing crosstalk is to check the cabling and verify that the pairs are all tightly twisted.
10. How do I initiate a DTE loopback on the HSU Card?
To initiate a loopback towards the DTE, you will need to arrow down from the Main Menu on the IMACS chassis to the HSU card (hit enter), then select the HSU port that will be used for the loopback. You can see below that in HSU Port #1, that LOCAL LB (Local Loopback) is set towards the DTE (in this case a Cisco 2500 series router connected to HSU Port #1). By default the LOCAL LB parameter is set to OFF, so to initiate the loopback arrow down to the parameter, hit enter, and select DTE, then hit enter again, then hit 's' to save the changes.
|
|
HSU Port
#1
|
HSU Port
#2
|
|
STATE
|
actv
|
stdby
|
|
WAN/SRV
|
w1-1
|
w1-1
|
|
MODE
|
dce
|
dce
|
|
TS
|
table
|
table
|
|
RATE
|
64k
|
56k
|
|
Tx CLOCK
|
int
|
int
|
|
Tx CLOCK PLRTY
|
norm
|
norm
|
|
DATA PLRTY
|
norm
|
norm
|
|
CTS
|
norm
|
norm
|
|
CTS DELAY
|
0
|
0
|
|
LOCAL LB
|
dte
|
OFF
|
|
LB GEN MODE
|
dds
|
dds
|
|
LB GEN
|
off
|
off
|
|
LB DET
|
w/to
|
w/to
|
|
ISDN CONN
|
no
|
no
|
|
Here you can see the Cisco output when the HSU Port is set to loopback towards the DTE device (the Cisco). The first line of output shows you that the Cisco detects the loop condition. In the case below, the Cisco is configured for Frame Relay encapsulation. You can actually see the Frame Relay LMI enquiries sent are being looped back from the HSU port to the Cisco serial interface and the 'LMI enq recvd' counter increments. Otherwise, if the DTE loopback was not turned on and the frame relay circuit had not been turned up, you would not see the 'LMI Enq Recvd' counter increment. The output below is from the 'show int serial0' command:
Serial0 is up, line protocol is down (looped)
Hardware is HD64570
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation FRAME-RELAY IETF, loopback not set, keepalive set (10 sec)
LMI enq sent 23, LMI stat recvd 0, LMI upd recvd 0, DTE LMI down
LMI enq recvd 23, LMI stat sent 0, LMI upd sent 0
LMI DLCI 0 LMI type is ANSI Annex D frame relay DTE
Broadcast queue 0/64, broadcasts sent/dropped 0/0,interface broadcasts 0
Last input 0:00:06, output 0:00:06, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
3 packets input, 42 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
24 packets output, 344 bytes, 0 underruns
0 output errors, 0 collisions, 9 interface resets, 0 restarts
0 output buffer failures, 0 output buffers swapped out 0 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
11. How do I configure a PPP connection to a Cisco router using a PM-IOR IMACS Card?
This is a quick sample configuration that supplies the most common configuration and debug commands for this scenario. For complete commands and debugging, you will need to consult the manuals. This configuration assumes numbered interface routing running RIP. Future FAQs will contain unnumbered examples.
PM-IOR Card configuration:
|
Display
|
Commands
|
|
Command>
|
set ether0 add 1.1.1.1
|
|
Command>
|
set ether0 netmask 255.255.255.0
|
|
Command>
|
set w1 network hardwire
|
|
Command>
|
set w1 address 2.2.2.1
|
|
Command>
|
set w1 netmask 255.255.255.0
|
|
Command>
|
set w1 modem on
|
|
Command>
|
set w1 protocol ppp
|
|
Command>
|
set w1 rip on
|
|
Command>
|
set mtu 1500
|
|
Command>
|
save all
|
|
Command>
|
reset w1
|
|
12. What data rate can the Office Channel Unit-Dataport (OCU-DP) support on a WAN card?
The data from this port will be directed to a WAN port (the options are w1-1 to w4-2). The Rate setting identifies the highest data transmission rate for the current port. Values are 2.4, 4.8, 9.6, 19.2, 56k, 64k, and SW56k (Switched 56 kbps).
13. What data rate can the Office Channel Unit-Dataport (OCU-DP) support on a SERVER Card?
If serv is chosen, the data will be directed to a port on a Resource card (the options are P1, P2 and P3. P1 is FRS in slot P1, P2 is FRS in slot P2 and P3 is FRS in slot P3. After selecting card, select logical port). The only available rates available when routed to a server are 56K and 64K.
14. How to get T1 error messages?
There are two different levels of T1 errors. The severe error message (red alarm, yellow alarm, blue alarm, and no signaling) is shown on the right upper corner of the configuration window. T1 performance statistics (such as unavailable seconds and bipolar violation error seconds) is under WAN card Perf.
15. Why can't I perform cross connects in IMACS?
IMACS has two different CPU types: BCON and XCON. BCON (880060) does not support cross connect. XCON (8801, 8802, and 8803) support cross connects.
|
