Configuration Note
16
Document #: LTRT-40386
Troubleshooting the MSBR
2.4
Capturing Voice on Logical Interfaces
The “debug capture voip interface” command provides the capability of monitoring specific
logical interfaces (e.g. VLANs).
The same concept is applied in the “debug capture voip interface” as in the “debug capture
data interface” command.
2.4.1 Monitoring VoIP Logical Interface Example
The following is an example of how to monitor a VoIP logical interface.
#
debug capture voip interface
vlan 1 proto ip host any
08:21:16.752244 00:90:8f:1e:5a:1c > 00:90:8f:1e:5a:1b, ethertype
IPv4 (0x0800), length 66: (tos 0x0, ttl 63, id 17099, offset 0,
flags [DF], proto: TCP (6), length: 52) 192.168.10.20.44498 >
192.168.100.101.80: F, cksum 0xb4e0 (correct),
275337040:275337040(0) ack 2499340571 win 229 <nop,nop,timestamp
27988585 105130724>
2.4.2 Monitoring VoIP Link interface from Data-CPU to VoIP CPU
Example
When monitoring the traffic from VoIP-CPU to Data-CPU using an internal link (e.g., vlan-
4001), the following command should be applied:
#
debug capture voip interface vlan 4001 proto ip host any
08:24:37.590252 00:90:8f:1e:5a:1b > 00:90:8f:1e:5a:1c, ethertype
IPv4 (0x0800), length 122: (tos 0x0, ttl 64, id 37498, offset 0,
flags [DF], proto: TCP (6), length: 108) 169.254.254.254.914 >
169.254.254.253.999: P 3010687982:3010688038(56) ack 3717629414
win 13120 <nop,nop,timestamp 105336564 105308817>
