[cisco-voip] CUBE setup to Centurylink SIP Trunk

[NateCCIE]

Yeah the customer gets to choose. The nice part about IP TF/LD is you don’t pay for sessions or trunks, and it’s a BYOB solution, but there is no local calling or DID service.

I am guessing you changed the IPs of the SBC, I believe 6.0.0.0/8 is DOD?  I would guess that if it’s broadsoft and not requiring registration it’s a Level3 platform.

I have heard that internally they are moving to all Level3 backend systems for ordering, etc.
Sent from my iPhone

> On Sep 12, 2018, at 8:44 PM, Anthony Holloway <avholloway+cisco-voip at gmail.com> wrote:
> 
> I can confirm that I am talking to broadsoft, since I get a an error in CUBE about the SDP attribute bsoft not being recognized.
> 
> Nate, is there a choice for the customer signing up for new service, or is it dictated by something out of their control?
> 
> 
> 
>> On Wed, Sep 12, 2018 at 8:54 PM NateCCIE <nateccie at gmail.com> wrote:
>> 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> on behalf of Jason Aarons (Americas) <jason.aarons at dimensiondata.com>
>> Sent: Wednesday, September 12, 2018 8:37 PM
>> To: cisco-voip (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:
>> "http://www.dimensiondata.com/emaildisclaimer"
>> 
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180912/2d2e70ef/attachment.html>