Examples
The table below
describes the significant fields shown in the examples. Each line of output
under "VoIP RTP active connections" shows information for one call leg. A phone
call normally consists of two call legs, one connected to the calling party and
one connected to the called party. The router joins (or bridges) the two call
legs to make a call. The
show
voip
rtp
connections command shows the RTP information for
H.323 and Session Initiation Protocol (SIP) calls only; it does not directly
show the POTS call legs. The information for the IP phone can be seen using the
show
ephone
offhook command.
The following sample output shows an incoming H.323 call that is being directed to an IP phone attached to a Cisco Unified
Communications Manager Express (Unified CME) system.
Router# show voip rtp connections
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP
1 21 22 16996 18174 10.4.204.37 10.4.204.24
Found 1 active RTP connections
The following
sample output shows the same call as in the previous example, but using the
detail
keyword with the command. The sample output shows the called number (1509) and
calling number (8108) on both call legs (21 and 22); the called and calling
numbers are the same on both legs for a simple A-to-B call. Leg 21 is the H.323
segment of the and leg 22 is the POTS segment that goes to the IP phone.
Router#
show voip rtp connections detail
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP
1 21 22 16996 18174 10.4.204.37 10.4.204.24
callId 21 (dir=1):called=1509 calling=8108 redirect=
dest callId 22:called=1509 calling=8108 redirect=
1 context 64FB3358 xmitFunc 6032E8B4
Found 1 active RTP connections
The following
example shows the call from the previous example being transferred by extension
1509 to extension 1514. Notice that the dstCallId changed from 22 to 24, but
the original call leg (21) for the transferred party is still present. This
implies that H.450.2 capability was disabled for this particular call, because
if H.450.2 was being used for the transfer, the transfer would have caused the
incoming H.323 call leg to be replaced with a new call.
Router# show voip rtp connections
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP
1 21 24 16996 18174 10.4.204.37 10.4.204.24
Found 1 active RTP connections
The following
example shows the detailed output for the same transfer as shown in the
previous example. The original incoming call leg is still present (21) and
still has the original called and calling numbers. The transferred call leg
(24) shows 1509 (the transferring party) as the calling party and 1514 (the
transfer destination) as the called party.
Router# show voip rtp connections detail
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP
1 21 24 16996 18174 10.4.204.37 10.4.204.24
callId 21 (dir=1):called=1509 calling=8108 redirect=
dest callId 24:called=1514 calling=1509 redirect=
1 context 6466E810 xmitFunc 6032E8B4
Found 1 active RTP connections
The following
sample output shows a cross-linked call with two H.323 call legs. The first
line of output shows that the CallID for the first call leg is 7 and that this
call leg is associated with another call leg that has a destination CallId of
8. The next line shows that the CallID for the leg is 8 and that it is
associated with another call leg that has a destination CallId of 7. This
cross-linkage between CallIds 7 and 8 shows that the first call leg is related
to the second call leg (and vice versa). From this you can infer that the two
call legs are actually part of the same phone call.
In an active
system you can expect many lines of output that you would have to sort through
to see which ones have this cross-linkage relationship. The lines showing two
related call legs are not necessarily listed in adjacent order.
Router# show voip rtp connections
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP
1 7 8 16586 22346 172.27.82.2 172.29.82.2
2 8 7 17010 16590 172.27.82.2 192.168.1.29
Found 2 active RTP connections
The following
example shows RTP information with IPv6 local and remote addresses:
Router# show voip rtp connections
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP
1 11 9 17424 18282 2001:DB8:C18:1:218:FEFF:FE71:2AB6 2001:DB8:C18:1:218:FEFF:FE71:2AB6
2 12 10 18282 17424 2001:DB8:C18:1:218:FEFF:FE71:2AB6 2001:DB8:C18:1:218:FEFF:FE71:2AB6
Found 2 active RTP connections
The following example shows RTP information with VRF details:
Router# show voip rtp connections
VoIP RTP Port Usage Information:
Max Ports Available: 23001, Ports Reserved: 101, Ports in Use: 2
Min Max Ports Ports Ports
Media-Address Range Port Port Available Reserved In-use
------------------------------------------------------------------------------
Global Media Pool 8000 48198 19999 101 2
------------------------------------------------------------------------------
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF
1 1 2 25000 16390 10.0.0.1 10.0.0.2 NO VRF1
2 2 1 25002 16398 11.0.0.1 11.0.0.2 NO VRF2
SRTP Rollover Counter (ROC) information is displayed in the “SSRC:ROC” format and is updated based on Remote IP address and
Port.
The following example shows SRTP ROC information for an SRTP call:
Router#show voip rtp connections detail
VoIP RTP Port Usage Information:
Max Ports Available: 59794, Ports Reserved: 206, Ports in Use: 2
Port range configured
Min Max Ports Ports Ports
Media-Address Range Port Port Available Reserved In-use
------------------------------------------------------------------------------
Global Media Pool 5500 65498 29897 103 2
IP Address Based Media Pool
------------------------------------------------------------------------------
8.39.15.21 8.39.15.21 5500 65498 29897 103 0
Port-Range 10000 20000
------------------------------------------------------------------------------
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF
1 323 324 5508 9256 10.64.86.90 10.65.105.60 NO NA
callId 323 (dir=1): called=6010 calling=7776 redirect= loopback=NO confID=3 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 324: called=6010 calling=7776 redirect= , confID:3
, vrf = NA
1 context 0x7F8FD8A428D0 xmitFunc 0x5605693121F0
2 324 323 5510 31826 10.64.86.90 10.64.88.52 NO NA
callId 324 (dir=2): called=6010 calling=7776 redirect= loopback=NO confID=3 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 323: called=6010 calling=7776 redirect= , confID:3
, vrf = NA
1 context 0x7F8FD8B11698 xmitFunc 0x5605693121F0
SRTP information for endpoints:
==========================================================
remote ip = 10.64.88.52, remote port=31826
RX SRTP ROC Context (SSRC:ROC): 0xBF85C508:0x1
TX SRTP ROC Context (SSRC:ROC): 0x1E4E1915:0x1
----------------------------------------------------------
Found 2 active RTP connections
In the above example, 0xBF85C508 is the Synchronization Source (SSRC) and 0x1 is the ROC. RX SRTP ROC Context is the crypto SRTP context for all the received streams for a media session. TX SRTP ROC Context is the crypto SRTP context for all the transmitted streams for a media session.
ROC increases after every RTP sequence number (maximum of 65535) roll over.
Router#show voip rtp connections detail
VoIP RTP Port Usage Information:
Max Ports Available: 59794, Ports Reserved: 206, Ports in Use: 2
Port range configured
Min Max Ports Ports Ports
Media-Address Range Port Port Available Reserved In-use
------------------------------------------------------------------------------
Global Media Pool 5500 65498 29897 103 2
IP Address Based Media Pool
------------------------------------------------------------------------------
8.39.15.21 8.39.15.21 5500 65498 29897 103 0
Port-Range 10000 20000
------------------------------------------------------------------------------
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF
1 323 324 5508 9256 10.64.86.90 10.65.105.60 NO NA
callId 323 (dir=1): called=6010 calling=7776 redirect= loopback=NO confID=3 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 324: called=6010 calling=7776 redirect= , confID:3
, vrf = NA
1 context 0x7F8FD8A428D0 xmitFunc 0x5605693121F0
2 324 323 5510 31826 10.64.86.90 10.64.88.52 NO NA
callId 324 (dir=2): called=6010 calling=7776 redirect= loopback=NO confID=3 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 323: called=6010 calling=7776 redirect= , confID:3
, vrf = NA
1 context 0x7F8FD8B11698 xmitFunc 0x5605693121F0
SRTP information for endpoints:
==========================================================
remote ip = 10.64.88.52, remote port=31826
RX SRTP ROC Context (SSRC:ROC): 0xBF85C508:0x2
TX SRTP ROC Context (SSRC:ROC): 0x1E4E1915:0x2
----------------------------------------------------------
Found 2 active RTP connections
In the above example, 0xBF85C508 is the Synchronization Source (SSRC) and 0x2 is the ROC.
Router#show voip rtp connections detail
VoIP RTP Port Usage Information:
Max Ports Available: 59794, Ports Reserved: 206, Ports in Use: 2
Port range configured
Min Max Ports Ports Ports
Media-Address Range Port Port Available Reserved In-use
------------------------------------------------------------------------------
Global Media Pool 5500 65498 29897 103 2
IP Address Based Media Pool
------------------------------------------------------------------------------
8.39.15.21 8.39.15.21 5500 65498 29897 103 0
Port-Range 10000 20000
------------------------------------------------------------------------------
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF
1 323 324 5508 9256 10.64.86.90 10.65.105.60 NO NA
callId 323 (dir=1): called=6010 calling=7776 redirect= loopback=NO confID=3 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 324: called=6010 calling=7776 redirect= , confID:3
, vrf = NA
1 context 0x7F8FD8A428D0 xmitFunc 0x5605693121F0
2 324 323 5510 31826 10.64.86.90 10.64.88.52 NO NA
callId 324 (dir=2): called=6010 calling=7776 redirect= loopback=NO confID=3 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 323: called=6010 calling=7776 redirect= , confID:3
, vrf = NA
1 context 0x7F8FD8B11698 xmitFunc 0x5605693121F0
SRTP information for endpoints:
==========================================================
remote ip = 10.64.88.52, remote port=31826
RX SRTP ROC Context (SSRC:ROC): 0xBF85C508:0x1 0xF487C8FF:0x1 0xE127C8FF:0x1 0xC987C8FF:0x1 0xD567C8FF:0x1
TX SRTP ROC Context (SSRC:ROC): 0x1E4E1915:0x1 0xF487C8FF:0x1 0xE127C8FF:0x1 0xC987C8FF:0x1 0xD567C8FF:0x1
----------------------------------------------------------
Found 2 active RTP connections
The above example shows ROC context on per SSRC basis when there are multiple SSRCs involved in a single media session (for
example, during a video call).
In a High Availability scenario, the ROC updates are checkpointed and preserved across switchovers. An active router lists
all the SSRCs that have received the ROC updates in the reverse chronological order. In the below example, 0xE502F046:0x2 has received ROC update most recently and 0x94A522FC:0x1 has received ROC update prior to it, and so on. If there are more than 5 SSRCs, then only the first five SSRCs (those which
have received the ROC updates most recently) are considered for checkpointing.
The following example shows output from active router:
Device#show voip rtp connections detail
VoIP RTP Port Usage Information:
Max Ports Available: 59794, Ports Reserved: 206, Ports in Use: 2
Port range configured
Min Max Ports Ports Ports
Media-Address Range Port Port Available Reserved In-use
------------------------------------------------------------------------------
Global Media Pool 5500 65498 29897 103 2
IP Address Based Media Pool
------------------------------------------------------------------------------
8.39.15.21 8.39.15.21 5500 65498 29897 103 0
Port-Range 10000 20000
------------------------------------------------------------------------------
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF
1 3 4 5500 29330 10.64.86.90 10.64.88.11 NO NA
callId 3 (dir=0): called=6010 calling=7010 redirect= loopback=NO confID=1 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 4: called=6010 calling=7010 redirect= , confID:1
, vrf = NA
1 context 0x7F378AC01E38 xmitFunc 0x55CD6A2182C0
2 4 3 5502 17580 10.64.86.90 10.64.88.52 NO NA
callId 4 (dir=0): called=6010 calling=7010 redirect= loopback=NO confID=1 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 3: called=6010 calling=7010 redirect= , confID:1
, vrf = NA
1 context 0x7F37D1CE7A38 xmitFunc 0x55CD6A2182C0
SRTP information for endpoints:
==========================================================
remote ip = 10.64.88.52, remote port=17580
RX SRTP ROC Context (SSRC:ROC): 0xE502F046:0x2 0x94A522FC:0x1 0x79C19EC:0x1 0x8453A05E:0x8 0xE27329A2:0x1 0xE08E9236:0x4 0xD8A97DA8:0x1 0xDCD0D1C7:0x1
TX SRTP ROC Context (SSRC:ROC): 0xD22D83EE:0x2 0x8C9EFB1C:0x1 0x90A2D00C:0x1 0xD9C0D844:0x8 0x54F9FA7D:0x1 0xDCA9E096:0x4 0x6D539A3B:0x1 0x5067FDE8:0x1
----------------------------------------------------------
Found 2 active RTP connections
The following example shows output from standby router:
Device#show voip rtp connections detail
VoIP RTP Port Usage Information:
Max Ports Available: 59794, Ports Reserved: 206, Ports in Use: 2
Port range configured
Min Max Ports Ports Ports
Media-Address Range Port Port Available Reserved In-use
------------------------------------------------------------------------------
Global Media Pool 5500 65498 29897 103 2
IP Address Based Media Pool
------------------------------------------------------------------------------
8.39.15.21 8.39.15.21 5500 65498 29897 103 0
Port-Range 10000 20000
------------------------------------------------------------------------------
VoIP RTP active connections :
No. CallId dstCallId LocalRTP RmtRTP LocalIP RemoteIP MPSS VRF
1 3 4 5500 29330 10.64.86.90 10.64.88.11 NO NA
callId 3 (dir=0): called=6010 calling=7010 redirect= loopback=NO confID=1 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 4: called=6010 calling=7010 redirect= , confID:1
, vrf = NA
2 4 3 5502 17580 10.64.86.90 10.64.88.52 NO NA
callId 4 (dir=0): called=6010 calling=7010 redirect= loopback=NO confID=1 mode=3 rtp(tx:0/rx:0) rtcp(tx:0/rx:0) MPSS NO VRF NA peer callId 3: called=6010 calling=7010 redirect= , confID:1
, vrf = NA
SRTP information for endpoints:
==========================================================
remote ip = 10.64.88.52, remote port=17580
RX SRTP ROC Context (SSRC:ROC): 0xE502F046:0x2 0x94A522FC:0x1 0x79C19EC:0x1 0x8453A05E:0x8 0xE27329A2:0x1
TX SRTP ROC Context (SSRC:ROC): 0xD22D83EE:0x2 0x8C9EFB1C:0x1 0x90A2D00C:0x1 0xD9C0D844:0x8 0x54F9FA7D:0x1
----------------------------------------------------------
Found 2 active RTP connections
Table 6. show voip rtp connections
Field Descriptions
Field
|
Description
|
No.
|
Identifier of an RTP connection in this output.
|
CallId
|
Internal
call identifier of a telephony call leg (RTP connection).
|
dstCallId
|
Internal
call identifier of a VoIP call leg.
|
LocalRTP
|
RTP port
of the media stream for the local entity.
|
RmtRTP
|
RTP port
of the media stream for the remote entity.
|
LocalIP
|
IPv4 or
IPv6 address of the media stream for the local entity.
|
RemoteIP
|
IPv4 or
IPv6 address of the media stream for the remote entity.
|
dir
|
0
indicates an outgoing call. 1 indicates an incoming call.
|
called
|
Extension
that received the call.
|
calling
|
Extension
that made the call.
|
redirect
|
Original
called number if the incoming call was forwarded.
|
context
|
Internal
memory address for the control block associated with the call.
|
xmitFunc
|
Internal
memory address for the transmit function to which incoming RTP packets (on the
H.323 and SIP side) are sent; the address for the function that delivers the
packets to the ephone.
|
VRF
|
Virtual Routing and Forwarding (VRF) associated with the call.
|
SSRC:Index
|
SRTP Rollover Counter information.
|
RX SRTP ROC Context
|
The crypto SRTP context for all the received streams for a media session.
|
TX SRTP ROC Context
|
The crypto SRTP context for all the transmitted streams for a media session.
|