[cisco-voip] CUBE setup to Centurylink SIP Trunk

[NateCCIE]

I don't see any reason to include the media address in the trusted list.
That would be like including all IP phones in the trusted list.

 

A lot of the time I only route specific IPs to the outside next hop, as a
security measure.  If they didn't indicate where the media was coming from,
it would be easy to miss that and get one way audio.

 

And centurylink has many SIP plaforms, the registration one with
multi-tennant configs for dual registration is the Broadsoft platform, the
sonos platform isn't adding new customers, and then there is the IP
TollFree/LD, that one is still current and doesn't require registration.
There also are at least two Level3 platforms that are now "centurylink"

 

Thanks,

-Nate

 

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Ryan Huff
Sent: Wednesday, September 12, 2018 7:31 PM
To: Jason Aarons (Americas) <jason.aarons at dimensiondata.com>; cisco-voip
(cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] CUBE setup to Centurylink SIP Trunk

 

Target the signaling address in your dial peers, the media address will be
advertised in the SDP. Make sure to include both in your IP Trusted List ACL
(under the voice service voip configuration) as well as any CUCM signaling
nodes that are not directly targeted by a dial-peer (but I typically add all
the nodes in regardless, just as a measure of safety).

 

Thanks,

 

Ryan

  _____  

From: cisco-voip <cisco-voip-bounces at puck.nether.net
<mailto:cisco-voip-bounces at puck.nether.net> > on behalf of Jason Aarons
(Americas) <jason.aarons at dimensiondata.com
<mailto:jason.aarons at dimensiondata.com> >
Sent: Wednesday, September 12, 2018 8:37 PM
To: cisco-voip (cisco-voip at puck.nether.net
<mailto:cisco-voip at puck.nether.net> )
Subject: [cisco-voip] CUBE setup to Centurylink SIP Trunk 

 

 

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:
 
<https://eur04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.dimens
iondata.com%2FGlobal%2FPolicies%2FPages%2FEmail-Disclaimer.aspx&data=02%7C01
%7C%7Cce21fa3547064a9bd8a008d619112c06%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C
1%7C0%7C636723958879576925&sdata=2PDRGixdvFatDGAD1sCQrYgXUKSWNBa3LSzCbk7wYJQ
%3D&reserved=0> "http://www.dimensiondata.com/emaildisclaimer" 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180912/ed7e38fe/attachment.html>