Cisco SIP Router - getting the loopback to be the SIP peer

amigan_99
amigan_99 used Ask the Experts™
on
I was trying to bring up a SIP over IPSec peering on a CIsco ISR4451-X. This is to complement and already existing
SIP router (CUBE I guess they call it). Anyhow I had a call not connecting and I ran debug ccsip call. One weird thing
I noticed is that the Source IP Media address 136.10.23.97 address on the external Gig 0/1 interface of the router.
The loopback is 136.10.23.98 and that's what I'm expecting to see for Source IP Address (Media). What determines
what interface/address gets used for Source IP Address (Media)? Thank you.

001812: Dec 17 2018 23:26:18.025 PST: //747/E74BC54D82EC/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream             : 1
Negotiated Codec         : g711ulaw
Negotiated Codec Bytes   : 160
Nego. Codec payload      : 0 (tx), 0 (rx)
Negotiated Dtmf-relay    : 6
Dtmf-relay Payload       : 101 (tx), 101 (rx)
Source IP Address (Media): 136.10.23.97        
Source IP Port    (Media): 17876
Destn  IP Address (Media): 216.25.35.21
Destn  IP Port    (Media): 55414
Orig Destn IP Address:Port (Media): [ - ]:0
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Sr. Voice Engineer
Commented:
Letting the router bind sip control and media is never a good idea. You're right that you should bind it yourself. Binding "control" controls what the source IP is for the actual SIP traffic on TCP or UDP 5060 and 5061. "Media" determines what the source IP is for the RTP traffic.

Device(config)# voice service voip
Device(conf-voi-serv)# sip
Device(conf-serv-sip)# bind control source-interface FastEthernet0/0
Device(conf-serv-sip)# exit
Device(config)# voice service voip
Device(conf-voi-serv)# sip
Device(conf-serv-sip)# bind media source-address ipv4 172.18.192.204
Device(conf-serv-sip)# exit

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-sip-bind.html

You may have to bind both sides, (TSP and the SIP trunk to CUCM). This is done at the dial-peer level.

dial-peer voice 2 voip
description SIP TRUNK OUTGOING  
huntstop
preference 1
destination-pattern 99T
session protocol sipv2
session target ipv4:172.X.X.X:5060
session transport udp
voice-class sip bind control source-interface Loopback1000
voice-class sip bind media source-interface Loopback1000
dtmf-relay rtp-nte
no dtmf-interworking
codec g711alaw
no vad
amigan_99Network Engineer

Author

Commented:
Oh excellent. That's it. Thanks so much.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial