[cisco-voip] CUBE setup to Centurylink SIP Trunk

[Schlotterer, Tommy]

You are correct Jason, SDP will take care of the RTP traffic. They are just letting you know where the RTP traffic is coming from so you can adjust access lists.

Tommy



Sent from my Verizon, Samsung Galaxy smartphone



Tommy Schlotterer | Systems Engineer - Collaboration
Presidio (NASDAQ: PSDO) | presidio.com<http://presidio.com>
20 N Saint Clair 3rd Floor, Toledo, OH 43604
D: 419.214.1415 | C: 419.706.0259 | tschlotterer at presidio.com<mailto:tschlotterer at presidio.com>




-------- Original message --------
From: "Jason Aarons (Americas)" <jason.aarons at dimensiondata.com>
Date: 9/12/18 8:38 PM (GMT-05:00)
To: "cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net>
Subject: [cisco-voip] CUBE setup to Centurylink SIP Trunk

EXTERNAL EMAIL




I have a new CenturyLink SIP Service.  CenturyLink said it is new and doesn't match the Cisco guides.  (No more of the funky registrar and fixup headers via SIP profiles!)



In short in CUBE they want me to send calls to them per these settings;

SIP Signaling IP 6.6.156.245:5060

RTP IP 6.6.156.244

I'm just drawing a blank on how to setup CUBE to send SIP signaling requests to CenturyLink with different Signaling and RTP destination addresses.  Don't I just send session target ipv4:X.X.156.245:5060 and the SDP takes care of the RTP negotiation part?  Do I really care in my CUBE what their RTP address is?


-jason



This email and all contents are subject to the following disclaimer:
"http://www.dimensiondata.com/emaildisclaimer"<http://www.dimensiondata.com/Global/Policies/Pages/Email-Disclaimer.aspx>


This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180913/6588633d/attachment.html>