cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2710
Views
7
Helpful
15
Replies

CTS video through Cube to 9971 doesn't work well

gilbert spoor
Level 1
Level 1

Hi,

I am running a Lab with two CUCM8.6.2 environments and a router acting as CUBE in between.

In one environment I have a video SIP phone (Cisco E20) and a cts-1100 running software 1.9.

in the other environment I have an E20 and a Cisco 9971 video enabled phone.

a cisco 2921 router is configured for the CUBE functionality.

I can call between the two environments without any problem using the E20's audio and video gets relayed by the cube.

But when calling between the CTS-1100 and the E20 or the 9971 in the other environmkent doesn't work well, the E20 doesn't receive video or audio and remains in an answering state, while the CTS receives audio and video from the e20 through the cube (so one way media)

when the CTS calls the E20 that is registered to the same callmanager audio and video work fine.

does anyone know what I'm doing wrong?

Below the config of the router:

version 15.0

service timestamps debug datetime msec

service timestamps log datetime msec

service password-encryption

!

hostname Router

!

boot-start-marker

boot-end-marker

ip source-route

ip cef

!

vlan ifdescr detail

multilink bundle-name authenticated

!

voice-card 0

dspfarm

dsp services dspfarm

!

voice service voip

rtp-ssrc multiplex

address-hiding

allow-connections sip to sip

redirect ip2ip

fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback none

sip

bind control source-interface Loopback0

bind media source-interface Loopback0

session transport tcp

rel1xx disable

header-passing sip-sip

midcall-signaling passthru

g729 annexb-all

pass-thru content sdp

!

voice class codec 1

codec preference 1 aacld

codec preference 2 g711alaw

codec preference 3 g711ulaw

codec preference 4 g722-64

codec preference 5 g728

!

!

!

!

hw-module pvdm 0/0

!

interface Loopback0

ip address 10.0.0.1 255.255.255.255

!

interface GigabitEthernet0/0

ip address 192.168.222.10 255.255.255.0

duplex auto

speed auto

!

interface GigabitEthernet0/1

ip address 10.1.1.254 255.255.255.0

duplex auto

speed auto

!

interface GigabitEthernet0/2

ip address 10.2.2.254 255.255.255.0

duplex auto

speed auto

!

ip forward-protocol nd

!

no ip http server

ip http secure-server

!

ip route 192.168.255.0 255.255.255.0 192.168.222.254

!

control-plane

!

!

codec profile 1 aacld

!

codec profile 2 h264

!

codec profile 3 h263+

!

!

codec profile 4 h263

!

!

dial-peer voice 1 voip

description cucm1

destination-pattern 1...

rtp payload-type cisco-codec-video-h264 112

session protocol sipv2

session target ipv4:10.1.1.1

voice-class codec 1

dtmf-relay rtp-nte

!

dial-peer voice 2 voip

description cucm2

destination-pattern 3...

rtp payload-type cisco-codec-video-h264 112

session protocol sipv2

session target ipv4:10.2.2.1

voice-class codec 1

dtmf-relay rtp-nte

!

!

sip-ua

no remote-party-id

retry invite 2

!

!

!

gatekeeper

shutdown

!

!

15 Replies 15

Yep - pretty sure that CTS units use 10.x.x.x for the connection to the presentation codec and camera etc, unless you are using 10.x.x.x on your LAN in which case it uses something else (192.x.x.x?)

Good find, glad you got it sorted out... I never would have thought of that!