Hi,
I have a very basic lab setup for media forking to our apps from a CUBE. CUCM with phones and CUBE as gateway with route pattern set to cube for another set of phones connected to a CME. Route patterns and media forking is working, but it is not swapping the caller ID properly (media-index="0", and media-index="1").
The docs say that whichever (in/out bound) dial peer the forking profile is set to determines the perceived direction of the call, but if I cann both directions, the indexes never change. If the CUBEs dialpeer toward the CME has the recorder profile set on it, the CME phone is always index 0, and vica-versa. Not sure where to go from here.
CUBEs config ::
voice service voip
ip address trusted list
ipv4 192.168.15.18 255.255.255.255
ipv4 192.168.9.254 255.255.255.255
ipv4 192.168.9.253 255.255.255.255
ipv4 192.168.15.25 255.255.255.255
address-hiding
mode border-element
allow-connections sip to sip
media profile recorder 10000
media-recording 20 30
!
media class 3
recorder profile 10000
!
media service
dial-peer voice 20 voip
description Dial-Peer -- 15.18
destination-pattern 7778
session protocol sipv2
session target ipv4:192.168.15.19 --> (our server)
session transport tcp
!
dial-peer voice 1 voip
description To CUCM -- 9.14
destination-pattern 5...
session protocol sipv2
session target ipv4:192.168.9.14 --> CUCM 10.5 with 5034 DN
codec g711ulaw
no vad
!
dial-peer voice 2 voip
description In from CME(s)
destination-pattern 100.
session protocol sipv2
session target ipv4:192.168.9.254 --> CME 10.5 with DN 1000
media-class 3
codec g711ulaw
no vad
CME Config ::
voice service voip
allow-connections sip to sip
sip
dial-peer voice 10 voip
description to CUBE -- 9.252
destination-pattern 5...
session protocol sipv2
session target ipv4:192.168.9.252 --> CUBE
codec g711ulaw
no vad
###
With the cube's dial-peers this way, DN 1000 is always stream0, with the recording profile moved to dial-peer 1, then 5034 is always stream0 (no matter which direction the call is made from).
Any ideas? Thanks!
-Greg Oliver
