Verifying the VoIP Configuration
To verify the VoIP configuration, perform the following tasks:
- Verifying the VoIP Interface
- Verifying the Media Gateway Controller List
- Verifying Bandwidth Available for VoIP Traffic
Verifying the VoIP Interface
Purpose
Verify that the VoIP interface is correctly configured.
Action
From the CLI, enter the show interfaces extensive command.
Sample Output
user@host> show interfaces vp-3/0/0
extensivePhysical interface: vp-3/0/0, Enabled, Physical link is Up
Interface index: 141, SNMP ifIndex: 21, Generation: 142
Type: VP-AV, Link-level type: VP-AV, MTU: 1518, Speed: 10mbps
Device flags : Present Running
Link type : Full-Duplex
Link flags : None
Physical info : Unspecified
CoS queues : 8 supported, 8 maximum usable queues
Last flapped : 2006-09-29 09:28:32 UTC (4d 18:35 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes : 8886912 0 bps
Output bytes : 6624354 0 bps
Input packets: 90760 0 pps
Output packets: 65099 0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards: 0,
Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 8 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 best-effort 65099 65099 0
1 expedited-fo 0 0 0
2 assured-forw 0 0 0
3 network-cont 0 0 0
Packet Forwarding Engine configuration:
Destination slot: 2
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 9500000 95 0 low none
3 network-control 5 500000 5 0 low none
Logical interface vp-3/0/0.0 (Index 71) (SNMP ifIndex 47) (Generation 137)
Flags: Point-To-Point SNMP-Traps Encapsulation: VP-AV
Protocol inet, MTU: 1500, Generation: 142, Route table: 0
Flags: None
Filters: Input: pcap, Output: pcap
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.10.10.2, Local: 10.10.10.1, Broadcast: Unspecified,
Generation: 144Meaning
The output shows a summary of interface information. Verify the following information:
- The physical interface is Enabled. If the interface
is shown as Disabled, do either of the following:
- In the CLI configuration editor, delete the disable statement at the [edit interfaces interface-name] level of the configuration hierarchy.
- In the J-Web configuration editor, clear the Disable check box on the Interfaces>interface-name page.
- The physical link is Up. A link state of Down indicates that the interface is disabled. Do one of the
following:
- In the CLI configuration editor, delete the disable statement at the [edit interfaces interface-name] level of the configuration hierarchy.
- In the J-Web configuration editor, clear the Disable check box on the Interfaces>interface-name page.
- The Last Flapped time is an expected value. The Last Flapped time indicates the last time the physical interface became unavailable and then available again. Unexpected flapping indicates likely link-layer errors.
- The traffic statistics reflect expected input and output rates. Verify that the number of inbound and outbound bytes and packets matches expected throughput for the physical interface. To clear the statistics and see only new changes, use the clear interfaces statistics interface-name command.
Related Topics
For a complete description of show interfaces output, see the Junos Interfaces Command Reference.
Verifying the Media Gateway Controller List
Purpose
Verify that the Media Gateway Controller (MGC) list is correctly configured and that the MGCs are reachable over the network.
Action
From the operational mode in the CLI, enter show tgm fpc slot-number media-gateway-controller.
Sample Output
user@host> show tgm fpc 2 media-gateway-controllerMedia gateway controller(s): 173.26.232.77
10.10.10.30
10.10.10.40
Meaning
The output shows the configured MGC list. Verify the following:
- The IP addresses and the order of the IP addresses in the MGC list are correct. The first MGC on the list is the primary MGC. The TGM550 searches for the primary MGC first. If it cannot connect to the primary MGC or loses its connection to the primary MGC, it attempts to connect to the next MGC in the list, and so on.
- Use the Junos OS CLI ping command or the J-Web ping host tool (Troubleshoot>Ping Host) to verify that the configured MGCs can be reached over the network.
Related Topics
For a complete description of show tgm fpc output, see the Junos Interfaces Command Reference.
Verifying Bandwidth Available for VoIP Traffic
Purpose
Verify that the dynamic call admission control (CAC) configuration supports sufficient bandwidth for VoIP traffic.
Action
From the operational mode in the CLI, enter show tgm dynamic-call-admission-control.
Sample Output
user@host> show tgm dynamic-call-admission-controlReported bearer bandwidth limit: 3000 Kbps
Interface State Activation Bearer bandwidth
priority limit (Kbps)
ge-0/0/3.0 up 200 3000
t1-6/0/0.0 up 150 1000
br-1/0/3.0 up 50 128Meaning
The output shows the dynamic CAC configuration. Verify the following information:
- The activation priority and bearer bandwidth limit (BBL) configured on individual interfaces are correct.
- The Reported bearer bandwidth limit field displays the bandwidth available for VoIP traffic. Ensure that the bandwidth is sufficient for VoIP traffic.
Related Topics
For a complete description of show tgm dynamic-call-admission-control output, see the Junos Interfaces Command Reference.
Hide Navigation Pane
Show Navigation Pane
Download
SHA1