Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

session target routing overrides routing table for RTP

I noticed something in practice that wanted to confirm with what theory says.

I have something like this:

dial-peer 1 voice voip

destination-pattern 1..

session target ipv4:10.0.0.1

session protocol sipv2

ip route 10.0.0.0 255.0.0.0 20.0.0.10

ip route 0.0.0.0 0.0.0.0 20.0.0.20

IP address 10.0.0.1 is a SIP proxy which establishes calls to different media gateways depending on the destination pattern.

In particular, for destination pattern 1.. calls are sent to a media gateway with IP 11.0.0.1.

I will have expected that RTP sent to 11.0.0.1 should be routed through 20.0.0.20 (the default route). However I noticed that it is sent to 20.0.0.10, this is, the next-hop used for routing h323 signaling to 10.0.0.1.

I think this is not a bug, but a feature. Most of the time, you will not know the IP addresses where your RTP will be terminated. You will only know the IP address of the call processing server. If, for QoS reasons, you need to have voice routed through a specific route, you will need to find out all possible RTP destinations, in order to configure static routes to all of them.

I discovered this empirically. Does anybody knows if this is documented by Cisco? I have not been able to find it.

Regards,

Rafa

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Gold

Re: session target routing overrides routing table for RTP

Hi Rafa,

Unless you configure "bind", the source address for both signaling and media is non-deterministics, or better say, local best address. See:

http://cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080087ea9.html

7 REPLIES
Hall of Fame Super Gold

Re: session target routing overrides routing table for RTP

Hi Rafa,

In the SIP message, the proxy will tell to the endpoints the remote IP address to send the RTP stream. This can be the same address as the proxy (called flow-through, or address hiding) or a different address (called flow-around).

A cisco router doing IP-to-IP call processing can be configured either way. If you are using another type of SIP proxy, consult documentation for your product.

Hope this helps, please rate post if it does!

New Member

Re: session target routing overrides routing table for RTP

Paolo,

Thanks for you answer. However, what I want to confirm is that the RTP will be routed through the same gateway as the signaling that setup the call, overriding the routing table.

Regards,

Rafa

Hall of Fame Super Gold

Re: session target routing overrides routing table for RTP

Hello,

What I was trying to tell you, is that it depends on the endpoints address (c= line in the body of the SIP INVITE message).

If the endpoint address is the same as proxy address, RTP will be sent to that address. If it some other address, RTP will be sent to that address.

In both cases the routing table is used to send RTP to the address, and is never "overriden".

Hope this make sense.

As a recognition to those providing answers, please rate useful posts using the scrollbox below!

New Member

Re: session target routing overrides routing table for RTP

Paolo, I agree with you. The routing table should not be overriden. However I was surprised when I noticed this behavior in a Cisco 5400. RTP is sent to a different gateway than the routing table says.

Hall of Fame Super Gold

Re: session target routing overrides routing table for RTP

Well I think you misinterpreted what you saw. In yuour case the gateway (endpoint) had a different address that the SIP proxy. This is perfectly normal. So the RTP packets were still routed by routing table, only to a different destination.

How you can say that they were going to a different route ?

New Member

Re: session target routing overrides routing table for RTP

Paolo,

Yes, you are absolutely right. I misinterpreted what I saw. I'm using Netflow to monitor traffic in my routers. My AS5400 has two different interfaces, say Fas0/0 and Fas0/1. The default route points to Fas 0/0 while the dial-peer's session target points to Fas0/1.

What I saw in my netflow monitor was that no matter the destination of the RTP, it was always coming from the same IP address (that of Fas0/1). Then, I wrongly concluded that all RTP was coming from the same interface of the AS5400. Actually, it was coming from different interfaces, depending on the destination address of the RTP.

So, now my observation is that RTP is sent with source IP address of the same interface though which signaling is sent. Is this correct?

Regards,

Rafa

Hall of Fame Super Gold

Re: session target routing overrides routing table for RTP

Hi Rafa,

Unless you configure "bind", the source address for both signaling and media is non-deterministics, or better say, local best address. See:

http://cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080087ea9.html

477
Views
0
Helpful
7
Replies