[cisco-voip] One Way Video 9971-9971 thru CUBE 15.1M

[Jason Aarons (AM)]

Wireshark via Span to PC on back of 9971 shows remote H264 packet coming into phone, but if I go to 9971’s Web Page and click on Stream 2 (H264) the Recv Packets is 0.  So  the 9971 is dropping the incoming H264 packets and showing Black on the screen.

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (AM)
Sent: Thursday, April 17, 2014 7:59 PM
To: cisco-voip (cisco-voip at puck.nether.net)
Subject: [cisco-voip] One Way Video 9971-9971 thru CUBE 15.1M


I have two CUCM 9.1 clusters with a CUBE in the middle.

I’m getting one-way video.  Using media flow-around.

Should I get two-way video with CUBE 15.1 ? show call active video brief

I see both sides 9971 sending h.264 to the CUBE but only receiving it in one direction.  Seems the CUBE 15.1M is the problem.  If I do a direct trunk bypassing the CUBE I get two-way video.


2811#show call active video compact
<callID>  A/O FAX T<sec> Codec       type        Peer Address       IP R<ip>:<udp>
Total call-legs: 2
        67 ANS     T159   H264        VOIP-VIDEO  P+14082022002    10.102.64.57:17800
        68 ORG     T159   H264        VOIP-VIDEO  P0114412525123     10.26.1.249:217



R1#show run | sec voice
voice service voip
media flow-around
address-hiding
allow-connections sip to sip
sip
  bind control source-interface GigabitEthernet0/0.202
  bind media source-interface GigabitEthernet0/0.202
!
voice class codec 1
codec preference 1 g729r8
codec preference 2 g711ulaw
!
dial-peer voice 25 voip
description **Incoming call from ClusterA**
session protocol sipv2
session target ipv4:10.10.64.11
incoming called-number 01132.
dtmf-relay rtp-nte
!
dial-peer voice 35 voip
description **Outgoing call to ClusterB**
destination-pattern 01144T
session protocol sipv2
session target ipv4:157.26.1.250
voice-class codec 1
dtmf-relay rtp-nte
R1#


itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140417/a4a27fdd/attachment.html>