Unified Communications

 View Only

  • 1.  SIP trunks with Twilio

    Posted 02-27-2018 11:34 AM

    Anyone using Twilio for SIP services with Avaya SBCs? What has been your experience with them as a carrier?



  • 2.  RE: SIP trunks with Twilio

    Posted 02-27-2018 11:41 AM

    We haven't used them for SIP services, but we have used them for some Remote DID and texting capabilities and as far I know, we have never had any issues with them or their services. 



    In Reply to Dustin Fails:

    Anyone using Twilio for SIP services with Avaya SBCs? What has been your experience with them as a carrier?



  • 3.  RE: SIP trunks with Twilio

    Posted 03-02-2021 08:41 PM
    Wanted to bring this back up...   I am trying to connect me SM to Twilio.  I am doing the paper exercise, before I build anything...
    I know Twilio and SM need to contact each other, via the internet. which means FW from SM to twilio.com (in general).
    I will need the Twilio Cert for TLS, I built the Twilio Elastic SIP Trunk. I created the ACL for my SM but had to create a login, which is confusing but I could not get the trunk built without it. I cannot get anyone at Twilio to confirm if I really need the login or not.
    The one thing I cannot figure out, is how to get SM to respond to the Proxy Auth Request from Twilio... or if it will.

    thoughts??

    ------------------------------
    Alan Williford
    Voice Technician
    Liberty Mutual
    ------------------------------

    Original Message


  • 4.  RE: SIP trunks with Twilio

    Posted 03-02-2021 08:58 PM
    What you will really need in the mix is a Session Border Controller.  

    We've deployed Twilio as a backup, outbound trunking solution for our campus.  We also point some of our inbound 800 numbers into our system via Twilio trunks.

    Pretty much, you create a trunk from ASM to your SBC, then your SBC to Twilio.  The SBC will help normalize some things that Twilio expects to be there (like the proper domain, etc.).  The SBC can also do authentication to the Twilio trunks (although, that is not required, since you can authenticate by IP address).  ASM has no ability to do outbound authentication or registration of trunks.  It's simply a SIP router and can't do those functions -- that is really the job of an SBC.  Additionally, it's super easy to load outbound and inbound certificates on the SBC so things actually are secure across the internet.

    BTW, you should always put an SBC between anything on the internet and your ASMs.  ASMs are great devices, but they have a very limited ability to prevent attacks, bad actors, repeated login attempts, etc.  An SBC is a voice firewall and will help keep things more sane.

    -Nick

    ------------------------------
    Nick Kwiatkowski
    Director of Design and Engineering
    Michigan State University
    East Lansing MI
    ------------------------------

    Original Message


  • 5.  RE: SIP trunks with Twilio

    Posted 03-02-2021 09:41 PM
    Thanks Nick! 
    I have SBC connection to Twilio working. Now that I have direct access to Twilio via our Colo, I want to explore if I can connect to them via SM and not use my SBC.
    My pain point is the number of connections in my SBC... Telco, Skype, MS Teams, AWS and now Twilio... one wrong move and the world will come crashing down.
    Yes, I could split them each, onto a dedicated SBC but now I've multiple points of admin, including SM. Then I have more licenses and maintenance cost to deal with.
    Unless I am missing something, my last hurdle is getting past the authentication issue. 

    I have reached out to Twilio on why I need the ACL and have to Authenticate. The ACL should suffice.

    Just wondering if anyone else has solved the Proxy Auth issue...


    Alan

    ------------------------------
    Alan Williford
    Liberty Mutual
    ------------------------------

    Original Message


  • 6.  RE: SIP trunks with Twilio

    Posted 03-03-2021 07:42 AM

    Also, remember that your ASMs will only work with the signaling, not media.  Media would be coming from your Media Servers/Gateways/MedPros/Crossfires/Phones.  The firewall would need to NAT those properly and update the SIP (SDP) packets with the RTP information accordingly. 

    If you are worried about the traffic going through your SBCs (and assuming they are Avaya SBCs), you can build additional stacks of SBCs for dedicated purposes, and still connect them up to the same EMS for central administration.  I don't think there is a licensing required to stand up a new stack (check with your BP or Avaya on that statement), only the hardware.  I've got three different stacks in my setup for this purpose.

    As far as getting the ASMs to actually do registrations, I know there was some talk about getting it to work with the new RegEx adaptations that were made available in 8.1.0.  Now, I don't know how that would actually work -- since I'm assuming the authentication would need to be challenged and responses to those challenges would change.  

    But looking at our implementation, we simply use ACLs in the Twilio interface to point to our SBCs...  You shouldn't need to worry about authentication unless you enable it from their interface.



    ------------------------------
    Nick Kwiatkowski
    Director of Design and Engineering
    Michigan State University
    East Lansing MI
    ------------------------------

    Original Message


  • 7.  RE: SIP trunks with Twilio

    Posted 03-03-2021 08:55 PM
    Thanks Nick.  I'll let you know if I get this working.  It cannot hurt to try...

    ------------------------------
    Alan Williford
    Liberty Mutual
    ------------------------------

    Original Message