technology, networking and IP telephony
Posts tagged VOIP
DHCP Parse Error
23June 15, 2008
by Michael McNamara in VoiceOverIP
It would seem a great many people are running into this error so I thought I would post a quick article that would help all those looking for a solution to their problem. The Nortel i2002/i2004 (any Nortel IP phone) will return the error “DHCP parse error” if the DHCP server returns DHCP option 128 with an invalid format.
In one of my first blog posts entitled “DHCP Options (VoIP)” I outlined the DHCP options and the format that the phone expected. Kenneth quickly pointed out that I had fat-fingered the example DHCP string omitting the semicolon between the values for the primary Call Server (S1) and the secondary Call Server (S2). (I’ve since fixed the original post)
Here’s the format the DHCP option code 128 which the IP phones expects to be returned from the DHCP server when the IP phone is configured for “Full DHCP”;
Nortel-i2004-A,iii.iii.iii.iii:ppppp,aaa,rrr;iii.iii.iii.iii:ppppp,aaa,rrr.
Where the following values are;
- “Nortel-i2004-A” = Option #128 begins with this string for all Nortel IP phones
- “iii.iii.iii.iii” = the IP Address of the Call Server (S1 or S2)
- “ppppp” = port number for the Call Server
- “aaa” = the Action for the Server
- “rrr” = the Retry Count for the Server
The IP Address must be separated from the port number by a colon (:). The parameters for the Primary (S1) and the Secondary (S2) Call Servers are separated by a semicolon (;). The string must end a period (.).
If you are using an ISC DHCP server (this is generally included with any of the Linux distributions) you can refer to my article entitled “ISC DHCP Server (Nortel VoIP)” for information on how to setup and configure the ISC DHCP server to work with Nortel IP Telephony.
Cheers!
Update: Wednesday January 28, 2009
I just came across a “DHCP Parse Error” that actually had nothing to-do with the DHCP string. We had a phone that was using the same DHCP template as 9 other i2002 phones but it was displaying “DHCP Parse Error” when it booted up (this only surfaced after we upgraded to 0604DCG). The phone was actually configured incorrectly. It was suppose to be configured for a Voice VLAN and configured to get the Voice VLAN via LLDP-MED. The LLDP-MED option had been left set at “0″ (disabled) so the phone was trying to make a DHCP request looking for Option 191 while the DHCP server was only configured to return Option 128 as detailed above. It only took a few minutes to fix but I can see how someone could spend hours stuck on this.
Cheers!
Succession Signaling Server – Tips Part 2
1May 28, 2008
by Michael McNamara in VoiceOverIP
In the first part of this two post series I gave you a small sample of some CLI diagnostic commands that are available in the Succession Signaling Server v4.5. In this post I’m going to get a little more detailed and focus on some very specific commands used for troubleshooting voice quality in a VoIP network.
For the purpose of this post we’ll assume that we’re using and i2004 (Phase 2) phone. These commands are available on i2002,i2004, and i2007 (Phase 2 phones only). And also available on the 1120e/1140e and 1150e (they might be available on the i2050 softphone).
With the phone online you can remotely command the phone to perform a number of basic network troubleshooting commands as well as retrieve detailed network statistics. From the CLI interface of the Succession Signaling Server you can issue the following commands;
rPing <TN | IP>, <dest>[,<count>]
This command will instruct the phone to ping an IP address.
oam> rPing 10.1.198.50, 10.1.240.40, 5 27/05/2008 18:16:34 LOG0006 VTM:rPing Report from set (10.1.198.50) 64 bytes packets received from IP 10.1.240.40 27/05/2008 18:16:34 LOG0006 VTM:rPing Report from set (10.1.198.50) ICMP sequence is 0 27/05/2008 18:16:34 LOG0006 VTM:rPing Report from set (10.1.198.50) round trip time in ms: 20 27/05/2008 18:16:35 LOG0006 VTM:rPing Report from set (10.1.198.50) 64 bytes packets received from IP 10.1.240.40 27/05/2008 18:16:35 LOG0006 VTM:rPing Report from set (10.1.198.50) ICMP sequence is 1 27/05/2008 18:16:35 LOG0006 VTM:rPing Report from set (10.1.198.50) round trip time in ms: 20 27/05/2008 18:16:36 LOG0006 VTM:rPing Report from set (10.1.198.50) 64 bytes packets received from IP 10.1.240.40 27/05/2008 18:16:36 LOG0006 VTM:rPing Report from set (10.1.198.50) ICMP sequence is 2 27/05/2008 18:16:36 LOG0006 VTM:rPing Report from set (10.1.198.50) round trip time in ms: 20 27/05/2008 18:16:37 LOG0006 VTM:rPing Report from set (10.1.198.50) 64 bytes packets received from IP 10.1.240.40 27/05/2008 18:16:37 LOG0006 VTM:rPing Report from set (10.1.198.50) ICMP sequence is 3 27/05/2008 18:16:37 LOG0006 VTM:rPing Report from set (10.1.198.50) round trip time in ms: 20 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) 64 bytes packets received from IP 10.1.240.40 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) ICMP sequence is 4 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) round trip time in ms: 20 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) 64 bytes packets received from IP 10.1.240.40 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) 5 packets transmitted 5 packets received, 0 packets lost 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) minimum round trip time in ms: 20 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) average round trip time in ms: 20 27/05/2008 18:16:38 LOG0006 VTM:rPing Report from set (10.1.198.50) maximum round trip time in ms: 20 oam>
rPingStop <TN | IP>
This command will instruct the phone to stop pinging.
rTraceRoute <TN | IP>, <dest>, <count>
This command will instruct the phone to trace the route of the destination address.
oam> rTraceRoute 10.1.198.50, 10.1.240.40, 3
27/05/2008 18:22:56 LOG0006 VTM: rTraceRoute Report from set (10.1.198.50):
1 -- 10.1.198.1: 0ms 0ms 0ms
27/05/2008 18:22:56 LOG0006 VTM: rTraceRoute Report from set (10.1.198.50):
2 -- 10.1.144.40: 20ms 20ms 20ms
27/05/2008 18:22:56 LOG0006 VTM: rTraceRoute Report from set (10.1.198.50):
3 -- 10.1.144.8: 20ms 20ms 20ms
27/05/2008 18:22:56 LOG0006 VTM: rTraceRoute Report from set (10.1.198.50):
rTraceRoute completed !
oam>rTraceRouteStop <TN | IP>
This command will instruct the phone to stop the trace route.
RUDPStatShow <TN |IP>[, <clear>]
This command will display the RUDP statistics from the phone.
oam> RUDPStatShow 10.1.198.50 27/05/2008 18:27:19 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Message Sent: 451 27/05/2008 18:27:19 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Message Received: 153149 27/05/2008 18:27:19 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Retries: 1 27/05/2008 18:27:19 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Resets: 0 27/05/2008 18:27:19 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Uptime of Current TPS Registration: 0days 4hours 19minutes 8seconds
You can also append a value of 1 to the previous query to clear the statistics;
oam> RUDPStatShow 10.1.198.50, 1 RUDPStatShow: clear statistics after RUDPStatShow 27/05/2008 18:29:04 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Message Sent: 0 27/05/2008 18:29:04 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Message Received: 0 27/05/2008 18:29:04 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Retries: 0 27/05/2008 18:29:04 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Number of Resets: 0 27/05/2008 18:29:04 LOG0006 VTM:RUDPStatShow Report from set (10.1.198.50) Uptime of Current TPS Registration: 0days 4hours 20minutes 53seconds
eStatShow <TN | IP> [, <clear]
This command will display the Ethernet statistics from the phone.
oam> eStatShow 10.1.198.50 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) Duplex Mode: 1 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) Auto Negotiate Protocol Received: 0x3 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) Interface Speed: 1 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) LAN Priority Bit: 0 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) VLAN ID: 1 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) Packet Collision Peg Count: 0 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) CRC Error Peg Count: 0 27/05/2008 18:30:55 LOG0006 VTM:eStatShow Report from set (10.1.198.50) Frame Error Peg Count: 0
As with the RUDPStatShow command you append a value of 1 to the query to clear the Ethernet statistics. I’ll skip the example but the command would be “eStatShow 10.1.198.50, 1″.
isetInfoShow <TN | IP>
This command will display the phone configuration and server information.
oam> isetInfoShow 10.1.198.50 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report (DHCPConfig) from Set (10.1.198.50) Terminal Type: i2002 Ph2 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report (DHCPConfig) from Set (10.1.198.50) Firmware Version: 0604DBG 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report (DHCPConfig) from Set (10.1.198.50) Hardware ID: 18-001765ffe0fc-6602 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) Firmware ID: 0x02 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) Manufacture Code: 0x001765 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) Color Code: 0x66 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) PEC Code: NTDU91AA 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) DHCP Server IP: 10.1.198.10 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) VLAN Priority: 6 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) VLAN ID: 14 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) Set IP Address: 10.1.198.50 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) Set Subnet Mask: 255.255.255.0 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) Set IP Gateway Address: 10.1.198.1 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report from Set (10.1.198.50) Boot Mode: 47 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Server 1 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Server IP = 10.1.240.40 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Port Number = 4100 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Action = 1 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Retry = 5 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Server 2 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Server IP = 10.1.240.40 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Port Number = 4100 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Action = 1 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Retry = 5 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Server 3 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Server IP = 0.0.0.0 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Port Number = 0 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Action = 1 27/05/2008 18:36:34 LOG0006 VTM:isetInfoShow Report(Server Info) from Set (10.1.198.50) Retry = 0
RTPStatShow <TN | IP>
This command will display network metrics and QoS values.
NOTE: You’ll need to be in PDT to execute this command from the CLI interface of the Succession Signaling Server. In order to enter PDT simply hold down the <CTRL> while typing the letters “PDT”.
pdt> RTPStatShow 10.1.198.50 27/05/2008 18:42:10 LOG0006 shell: RTPStatShow: IP 10.1.198.50 is not an active set, displays the statistics from previous call 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Far End IP address: 10.1.240.45 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Far End Port: 5224 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Packet Sent: 57 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Packet Received: 0 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Packet Received out of order : 0 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Pkt Loss: 0% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Average Jitter: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Latency: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Listening R: 93 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Vocoder Type: 0 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Avg Net Loss Rate: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Avg Discard Rate: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Avg Burst Density: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Avg Burst Length: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Gap Density: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Gap Length: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Avg End System Delay: 5ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Avg Noise Level: 0dBm 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Avg Signal Power: 0dBm 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Round Trip Time Avg: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Local Round Trip Time Avg High: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Listening R: 0 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Avg Net Loss Rate: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Avg Discard Rate: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Avg Burst Density: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Avg Burst Length: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Gap Density: 0.00% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Gap Length: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Avg End System Delay: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Avg Noise Level: 0dBm 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Avg Signal Power: 0dBm 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Round Trip Time Avg: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Round Trip Time Avg High: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Packet Loss: 0% 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Average Jitter: 0ms 27/05/2008 18:42:10 LOG0006 VTM:RTPStatShow Report (RTCP-XR) from Set (10.1.198.50) Remote Latency: 0ms
Well by now you’re probably asking yourself what does all this mean. Well hopefully you aren’t completely lost. The first few commands are used to test basic connectivity, rPing and rTraceRoute. You would use these commands to make sure that an IP phone could communicate with a VGMC (Voice Gateway Media Card) or perhaps even another IP phone. Once you know you have basic network connectivity then you might need to look at some of the network statistics. Perhaps there is an auto-negotiation issue or perhaps there is too much packet loss leading too poor voice quality.
Note: did you know that you can perform pings an trace routes from the phone itself? After the phone has successfully booted and is connecting to the Nortel Call Server just press the “Services” key twice and select “Network Diagnostic Tools”.
Cheers!
Succession Signaling Server – Tips Part 1
1May 13, 2008
by Michael McNamara in VoiceOverIP
I thought I would share some of the more useful CLI commands that be found in the Nortel Succession 4.5 Signaling Server. You can access the CLI interface by TELNETing into the Signaling Server. You can also issue may of these commands from Element Manager, the web based GUI.
isetShow – display all IP phones connected (registered) to this signaling server.
oam> isetShow
Set Information
IP Address NAT Model Name Type RegType State Up Time Set-TN Regd-TN HWID FWVsn UNIStimVsn SrcPort DstPort
------------------ ---- -------------------------------- ---------- ------- ------------ -------------- ------------ ------------ -------------------- ------- ---------- ------- -------
10.1.1.146 IP Phone 1150E IPACD Regular online 7 10:00:30 152-00-00-09 152-00-00-09 18-001bbaf1cf58-66 C4L 2.9 5100 5000
10.1.1.123 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 10:00:30 152-00-00-26 152-00-00-26 18-000ae4754301-66 DBG 2.9 5100 5000
10.1.1.124 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 10:00:20 152-00-00-18 152-00-00-18 18-000ae4753f65-66 DBG 2.9 5100 5000
10.1.1.122 IP Phone 1140E i2004 Ph2 Regular online 7 10:00:14 152-00-00-05 152-00-00-05 18-001365ff6c03-66 C4L 2.9 5100 5000
10.1.1.111 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 10:00:12 152-00-00-04 152-00-00-04 18-000ae4753fc9-66 DBG 2.9 5100 5000
10.1.1.118 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 10:00:04 152-00-00-20 152-00-00-20 18-000ae4753fba-66 DBG 2.9 5100 5000
10.1.1.133 IP Phone 2007 Phase 2 i2004 Ph2 Regular online 7 09:59:41 152-00-01-02 152-00-01-02 18-000ae4769cc1-66 C4J 2.9 5100 5000
10.1.1.119 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 09:59:40 152-00-00-27 152-00-00-27 18-000ae4754009-66 DBG 2.9 5100 5000
10.1.1.112 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 09:59:36 152-00-00-19 152-00-00-19 18-000ae4753fe6-66 DBG 2.9 5100 5000
10.1.1.120 IP Phone 1140E i2004 Ph2 Regular online 7 09:59:26 152-00-00-01 152-00-00-01 18-001365ff5e4f-66 C4L 2.9 5100 5000
10.1.1.121 IP Phone 1140E i2004 Ph2 Regular online 7 09:59:18 152-00-00-02 152-00-00-02 18-001365ff717a-66 C4L 2.9 5100 5000
10.1.1.130 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 09:57:18 152-00-00-08 152-00-00-08 18-000ae47544d3-66 DBG 2.9 5100 5000
10.1.1.127 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 09:57:13 152-00-00-21 152-00-00-21 18-000ae4753fc5-66 DBG 2.9 5100 5000
10.1.1.106 IP Phone 2002 Phase 2 i2002 Ph2 Regular online 7 09:57:13 152-00-01-13 152-00-01-13 18-001bbaf40445-66 DBG 2.9 5100 5000
10.1.1.131 IP Phone 2004 Phase 2 i2004 Ph2 Regular online 7 09:56:58 152-00-00-24 152-00-00-24 18-000ae4754088-66 DBG 2.9 5100 5000
10.1.1.107 IP Phone 2002 Phase 2 i2002 Ph2 Regular online 7 09:56:42 152-00-01-14 152-00-01-14 18-001bbaf4a628-66 DBG 2.9 5100 5000
10.1.1.117 IP Phone 1140E i2004 Ph2 Regular online 7 09:54:48 152-00-00-00 152-00-00-00 18-001365ff6d7e-66 C4L 2.9 5100 5000
10.1.1.100 IP Phone 1140E i2004 Ph2 Regular online 7 09:54:45 152-00-01-16 152-00-01-16 18-001365ff1a9c-66 C4L 2.9 5100 5000
10.1.1.151 IP Phone 1150E IPACD Regular busy 7 02:14:56 152-00-00-30 152-00-00-30 18-001bbaf1cf96-66 C4L 2.9 5100 5000
10.1.2.119 Nortel WLAN 2211 Handset i2004 Regular online 1 08:33:34 152-00-00-12 152-00-00-12 30-00907a0284f8-66 071 2.9 5100 5000
10.1.5.58 IP Phone 2007 Phase 2 i2004 Ph2 Regular online 0 10:24:58 152-00-00-10 152-00-00-10 18-000ae4769cc8-66 C4J 2.9 5100 5000
10.1.1.154 IP Phone 1150E IPACD Regular online 0 04:14:49 152-00-01-28 152-00-01-28 18-001bbaf1cfd2-66 C4L 2.9 5100 5000
Total sets = 22
oam>electShow – display all registered and unregistered components.
oam> electShow Node ID : 1 Node Master : Yes Up Time : 7 days, 10 hours, 9 mins, 47 secs TN : 000 00 00 00 Host Type : ISP 1100 TLAN IP Addr : 10.1.140.20 ELAN IP Addr : 10.1.139.20 Election Duration : 15 Wait for Result time : 35 Master Broadcast period : 30 ===== master tps ===== Host Type TN TLAN IP Addr ISP 1100 000 00 00 00 10.1.140.20 Next timeout : 16 sec AutoAnnounce : 1 Timer duration : 60 (Next timeout in 3 sec) ====== all tps ====== Num TN Host Type ELAN MAC TLAN IP Addr ELAN IP Addr Up Time NumOfSets TimeOut 001 000 00 00 00 ISP 1100 00:02:b3:f6:52:0a 10.1.140.20 10.1.139.20 007 10:09:47 27 0 002 000 00 00 00 ISP 1100 00:02:b3:f6:50:9c 10.1.140.21 10.1.139.21 125 22:37:09 25 0 003 052 00 01 00 SMC 00:20:d8:d0:d9:a1 10.1.140.43 10.1.139.43 125 22:07:13 0 0 004 036 00 12 00 SMC 00:20:d8:d0:d0:fb 10.1.140.42 10.1.139.42 125 22:17:13 0 0 005 008 00 12 00 SMC 00:20:d8:d0:fc:83 10.1.140.45 10.1.139.45 125 22:15:12 0 1 006 016 00 04 00 SMC 00:20:d8:d1:12:63 10.1.140.41 10.1.139.41 125 22:15:13 0 0 007 052 00 07 00 SMC 00:20:d8:d0:dc:4d 10.1.140.44 10.1.139.44 004 13:43:53 0 1 ====== All cards in node configuration are registered ======
vtrkShow – display the virtual trunk status and available channels
oam> vtrkShow --------------------------- VTRK Summary --------------------------- VTRK status : Active Protocol : H323 D-Channel : 30 Customer : 0 Channels Idle : 146 Channels Busy : 11 Channels Mbsy : 0 Channels Pend : 0 Channels Dsbl : 0 Channels Ukwn : 0 Channels Total: 157 Chid ranges : 1 to 157 VTRK State = Active --------------------------- VTRK Status = Enabled ---------------------------
umsPolicyShow – display the available firmware for each phone model
oam> umsPolicyShow Total policies = 1 Name Upgrade Protocol Retries --------------- ----------- -------- ------- DEFAULT ANY UFTP -1 Available firmware: FW ID FWVsn Model Policy Name File name ----- ----- -------------------------------- --------------- -------------- 0x00 B76 IP Phone 2004 Phase 0/1 DEFAULT /u/fw/x00.fw 0x00 B76 IP Phone 2002 Phase 1 DEFAULT /u/fw/x01.fw 0x02 DBG IP Phone 2004 Phase 2 DEFAULT /u/fw/x02.fw 0x02 DBG IP Phone 2002 Phase 2 DEFAULT /u/fw/x02.fw 0x02 DBG IP Phone 2001 Phase 2 DEFAULT /u/fw/x02.fw 0x10 S58 IP Audio Conference Phone 2033 DEFAULT /u/fw/x10.fw 0x21 C4J IP Phone 2007 Phase 2 DEFAULT /u/fw/x21.fw 0x24 C39 IP Phone 1120E DEFAULT /u/fw/x24.fw 0x25 C4L IP Phone 1140E DEFAULT /u/fw/x25.fw 0x27 C4L IP Phone 1150E DEFAULT /u/fw/x27.fw Total firmware = 8
While I won’t go into every single command I will highlight a few additional commands;
ping – very useful for troubleshooting basic connectivity
routeShow – display the routing table including ELAN and TLAN
In a future post I hope to cover the remote iset diagnostic commands that are available for the IP phones.
Cheers!
