[cisco-voip] Call Recording / SPAN remote site traffic
Jeff Anderson
ciscoplumber at gmail.com
Tue Feb 19 13:35:29 EST 2008
I have a client who is trying to monitor voice calls using a software
package called witness. The witness product monitors traffic using a monitor
session
configured as follows:
monitor session 1 source vlan 100 rx
monitor session 1 destination remote vlan 500
monitor session 2 destination interface Fa0/6
monitor session 2 source remote vlan 500
Vlan 100 is the voice vlan.
The customer has two sites:
Minneapolis, MN
Phoenix, AZ
The witness server is located on a 3560 switch port fa0/6 in minneapolis.
The Minneapolis
PSTN gateway is plugged into the same 3560 port fa0/48. This is a trunk
port. The Phoenix
location is connected via an MPLS link on a router is connected to port
gi0/3 on the same
3560.
Currently the following scenarios work:
Example:
Minneapolis IP Phone to Minneapolis IP Phone
Minneapolis IP Phone to Minneapolis PSTN User
Phoenix IP Phone to Minneapolis IP Phone User
What I need to get working is:
Phoenix IP Phone to Minneapolis PSTN User
I currently think the Routers dot1Q trunk ports are not being monitored. I
think the only
reason the phoenix calls can be captured in minneapolis on an ip phone is
because the ip
phone in minneapolis is being monitored.
When a call is placed from one router dot1q trunk to different router dot1q
trunk it what
is failing.
The Minneapolis PSTN GW is configured with:
int fa0/0.100 in the 100 vlan - 172.16.100.1
The Minneapolis MPLS to Phoenix GW is configured with:
int fa0/0.100 in the 100 vlan - 172.16.100.2
The minneapolis PSTN gateway has its MGCP media and control traffic bound to
int
fa0/0.100.
Minneapolis voice network: 172.16.100.x/24
Phoenix voice network: 172.16.90.x/24
Does anyone know of a way to configure the monitor session to capture
traffic from the pheonix location?
Thanks,
Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080219/044fa306/attachment.html
More information about the cisco-voip
mailing list