Unified Communications

 View Only
Expand all | Collapse all

SBCE Registration Request - SIP Carrier/Provider

  • 1.  SBCE Registration Request - SIP Carrier/Provider

    Posted 09-09-2020 02:13 PM
    Avaya SBC 7.2

    I am trying to get SIP service working with a new SIP carrier and not having success.

    The new carrier route has been built in the SBCE and the route is open on the router/firewall.

    The carrier says that my SBC must register with their SBC before calls can be placed. They expect to receive a registration request that includes the PBX object (number) and credentials from my SBC.

    Anyone heard of this and know how to send a registration request from the Avaya SBCE? I do not see it.


    Thanks

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------


  • 2.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-09-2020 05:14 PM
    Who is your SIP Provider?
    Did you look on Avaya Devconnect for an Integration document?

    ------------------------------
    Brian Byrne
    Telecommunications Administrator
    Bellevue University
    ------------------------------



  • 3.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-09-2020 11:29 PM
    Hi,
    We have several SBCs conected to our ITSP via SIP trunks. Most of time when I troubleshoot with them they use the term my SBC is not registered to their sip server and when I inquired more on this they replied, by registration they mean is to see my SBCs mac address for security reasons and when they dont see it, it's a disconnect situation.

    From SBC configuration side, SIP options method is enabled for health check and Authentication is enabled with the credentials provided by ITSP.

    SBCs never register to ITSP , as per my knowledge.

    Check for Devconnect Application notes by your providers name on Avaya site for more details.







  • 4.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 08:18 AM
    You mentioned Authentication is enabled with credentials. Where is that enabled in the SBCE? 
    The carrier said we need to send credentials. But, I have no idea where to input that so it can be sent.

    Thanks

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 5.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 09:02 AM
    In SBCE, Global Profiles >>Server configuration>>Authentication.





  • 6.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 09:24 AM
    Thanks. I will give that a shot.

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 7.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 08:16 AM
    Granite is the carrier. 

    I did look for a DevConnect document, but did not see one.

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 8.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 06:38 AM
    It's actually not a normal setup for trunks to be registering.  I've seen it before, but it's not too common.

    They did introduce the ability for the ASBCE to do registering trunks in version 8.0, I believe.  The option is available in the Server Config settings.

    You could, technically do it with a SIGMA script, attaching it to an outgoing OPTIONS message, but it would be long and complex.  I wouldn't recommend going that route.  You might want to consider doing the upgrade to get the feature.

    -Nick

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



  • 9.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 08:19 AM
    I believe you that it's not common; I've never seen it. Unfortunately, we are running 7.2 SBC. 

    I am not familiar with a SIGMA script.

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 10.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 09:28 AM
    SIGMA scripts are scripts that can be written to interact with each SIP packet as they come in/leave the SBC.  They can be found under the "Signal Manipulation Scripts" section of the web-ui based configuration.  

    You can find some sample scripts in the help section of the EMS.  Like I said, they are pretty complex to do.  If you don't know much about the language, you may want to engage your business partner or APS.

    -Nick

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



  • 11.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 09:42 AM

    Ted,
    Over the years I have looked at nearly all of the DevConnect documents for the SBCE that involve Aura Session Manager (ASM). (I ignore IP Office).  I would estimate that 15% to 20% involve having the SBCE register to the ITSP's proxy.  The ability has existed in software versions dating back to when the SBCE was a Sipera product (at least back to version 4).

    Arslan correctly identified the place to administer the login credentials is under Global Profiles >>(ITSP) Server configuration >>Authentication.

    I don't think that you could use a SigMa script to perform the authentication. But if you could, as Nick observed it would be a very challenging script to write.  If you want more insight into SigMa scripting, you might want to download my "Super SigMa Scripting" from the following URL:
    https://www.convergeone.com/avaya-super-sigma-scripting

    Don't worry about identifying yourself to be able to download the document--we do nothing with the information. 



    ------------------------------
    John Waber
    Senior Technical Instructor
    ConvergeOne- Center of Excellence
    ------------------------------



  • 12.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 09:51 AM
    Thanks John. I appreciate the feedback. I will definitely try to set the authentication in the SBC. 
    I have never had to register the SBC with a carrier, mainly because, I think, the circuits over which SIP traffic passes are dedicated. 

    The carrier expects to see the PBX object (number) and credentials from my SBC. I don't know how to send the PBX object information if it is not sent with the OPTIONS messages. 

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 13.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 10:33 AM

    Ted,
    Your SBCE would use a SIP REGISTER request to deliver the credentials to the ITSP.  

    Open the SBCE Administration guide appropriate for your version.  Perform a search for the word "realm" and stop at the instance in the "Authentication Window" section.  That should help get you started.  (BTW: "Realm" and "SIP Domain" are essentially the same thing.)  



    ------------------------------
    John Waber
    Senior Technical Instructor
    ConvergeOne- Center of Excellence
    ------------------------------



  • 14.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 11:36 AM
    I have enabled authentication and added the credentials supplied by the carrier. (The Authentication section in my SBC version (7.2.1) only has username, realm, and password. I left realm blank.)
    I placed a call and it failed again - busy signal and "500 Server Internal Error". Is there a way to verify that the credentials are being sent? I don't see it in traceSBC.

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 15.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 12:38 PM
    Another interesting thing that I don't understand and would love feedback:

    When I place the call (after adding the authentication) and do a packet capture, on OPTIONS messages are being sent. There are no invite, trying, session progress messages.

    Any ideas why that is?

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 16.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 12:59 PM
    OPTIONS messages are essentially heartbeat messages (or, at least that is how they are usually used).  If the server responds with anything, they are marked as "alive".

    You can see the config for the heartbeat OPTIONS messages in the server config, under heartbeat.

    (OPTIONS messages can carry other payloads, but in the Avaya world, they are primarily used for heartbeats...  by spec, they are supposed to send messages to query what services a SIP server supports).

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



  • 17.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 03:06 PM
    That's good information. 

    I'm just wondering why only OPTIONS messages are being sent and not the others in the SIP ladder.

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 18.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 01:10 PM
    Hi,
    Have you provisioned your SBC with basic configuration (server confg,Routing, Server Flows)
     
    what is server status under status ?
    You will get 401 unauthorized error for incorrect credentials, 500 is server error which  indicates server problem of the sender of this message.





  • 19.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 03:15 PM
    Yes, the following settings have been configured for the carrier:
    Server Interworking
    Server Configuration
    Network Management > A1 and B1 interfaces
    Media and Signaling Interfaces
    Server Flows

    When I look at traceSBC, it appears to route the call properly. And, I've verified that the network is allowing traffic. But, the carrier is saying they are only seeing/receiving OPTIONS messages. 

    The Server Status for that carrier shows down. But, I'm assuming that is because (1) it's running over the Internet and not a dedicated circuit, or (2) because it hasn't "registered." 

    What problem could there be from the "sender of the this message"?

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 20.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 08:00 PM
    Hello Ted,

    Normally for the SBC to register to the carrier, it depends on the version

    for Version 8.x check the below link, page 51

    for an earlier version, you simply need to change the heartbeat message to 'REGISTER" instead of "OPTIONS'

    check page 59 of the below document

    The SBC will then send a register message which would be challenged by 401 unauthorized from the carrier, SBC will then resend this same REGISTER message with authentication information embedded within.

    Let me know if you need any more info please or if this didn't work with you
    thanks

    Samy Nashaat  |  Lead Convergence Engineer
     
    CCNA
    Level 40, 140 William Street, Melbourne 3000
    M: +61455991951 |
    E: samy.nashaat@ccna.com.au | www.ccna.com.au  
    CCNA on LinkedIn

     "The problem is where it is not where you want it to be"








  • 21.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 09:27 PM
    Alright. That's a new one - changing the heartbeat method to REGISTER. Good information. Thanks!

    I changed the Heartbeat method to REGISTER, although I am not sure what the FROM and TO URI should be. Is that something the carrier would provide to me? In the form of an email address - like <phone_number>@carrier_address.com? What's in there now is ping@tophide.com. Not sure what that is. 

    A traceSBC now shows the REGISTER request going out, but a return response says "501 Not Implemented."

    ------------------------------
    Ted Hargiss
    Manager
    Landstar
    ------------------------------



  • 22.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 09:35 PM
    What is the server type under Server configuration, for SIP provider, it should be Trunk server and not Call server.






  • 23.  RE: SBCE Registration Request - SIP Carrier/Provider

    Posted 09-10-2020 10:03 PM
    Edited by Arslan Ali 09-10-2020 10:21 PM
    For Registration configuration window :
    1. Refresh interval = This value should be chosen in consultation with Granite.
    2. From URI and To URI entries for REGISTER messages, this information should be provided by Granite.
    In general they are built in following format :
    • Pilot number@IPAdress.
    • Where IPAddress = Granite's SIP Proxy IP address.
    • Pilot Number of DID block of the SIP trunk.
      After correcting all these settings if you don't get response to your INVITE .You may need to remove unused / extra headers using Sigma Script. Most providers have fixed maximum SIP packet size limitations, what it means is, if SIP message size exceeds the limit it wont even reach to provider and you will never see a response back on SBCE.

      You need to consult Granite asking which headers are unwanted for them.
      Many such examples are documented in Devconnect's SIP Trunking application notes.

      Good Luck.

      This post/ scenario taught me something new that SBCE can send Register messages to ITSP.
      This is good to know.





    • 24.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-10-2020 10:40 PM
      Yes, it is set to Trunk server.

      ------------------------------
      Ted Hargiss
      Manager
      Landstar
      ------------------------------



    • 25.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-11-2020 11:11 AM
      Well, the good news is that the carrier is now receiving the REGISTER request from my SBC.
      The bad news is that they don't like one thing they see.

      In the Message Header's FROM field (captured from a trace), the address is <phone_number>@<my_internal_IP_address>. The carrier said that it should be the phone number and their domain name (what they've provided) like what is in the TO field. Essentially, the REGISTER request needs to reflect the phone number and their domain name in both the FROM and TO fields.



      In the SBC>Server Configuration>Heartbeat section, the FROM and TO fields have the same thing - the phone number and the carrier's domain name (what they've provided). I don't know where else the FROM field can be changed so that when sent, it shows the carriers domain name. Any ideas?




      ------------------------------
      Ted Hargiss
      Manager
      Landstar
      ------------------------------



    • 26.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-11-2020 01:11 PM
      Try in topology hiding form.






    • 27.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-11-2020 01:14 PM

      Ted,
      The SBCE's Topology Hiding feature modifies the domain portion of the SIP URI.  Because almost all vendors want the domain to be expressed as an IP Address, the SBCE's default ("auto") option performs that change. It does a simple Network Address Translation (NAT) to swap the address between an internal IP address and an external Public address.

      Avaya wants the domain portion of the address to be a "name", such as training.com.  So the Topo Hiding section for traffic destined for ASM is usually set to "overwrite" to the domain name. 

      I believe that the Topo Hiding feature is what is changing the domain-name in your REGISTER request to an IP address.

      While the Topo Hiding feature allows you to pick which headers are modified, it does not also allow you to be selective about which requests get that treatment.

      Technically, the TO and FROM headers are "cosmetic" and have no effect on the routing of the message. So overwriting the IPs with domain-names in the outgoing message might work.  This would be in used in the Topo Hiding configuration going towards your ITSP.  Do not change any other outbound headers; only the TO and FROM. Good Luck.



      ------------------------------
      John Waber
      Senior Technical Instructor
      ConvergeOne- Center of Excellence
      ------------------------------



    • 28.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-11-2020 04:28 PM
      Again, more new, good information. I really appreciate all the feedback. 

      I modified the topology hiding and overwrote the FROM value with what the carrier wants to see. That definitely made a difference in the REGISTER request. 

      After the change, as Arslan mentioned, the first request returned a 401 Unauthorized. Then, a 200 OK came back. Excellent!

      Making progress...

      The next hurdle is making a call. After seeing the 200 OK, I placed a call. It didn't return a busy immediately; it was dead air for several seconds, then busy. I'll work with the carrier on that one and report back here. 

      Thank you all for your help.

      ------------------------------
      Ted Hargiss
      Manager
      Landstar
      ------------------------------



    • 29.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-15-2020 09:30 AM
      I was hoping to be able to report success with this, but unfortunately, no.

      The good news is that the SBC was able to register with the carrier and inbound DID calls were successful.
      However, outbound calls were not. (There are routes that send calls to the carrier.)
      A traceSBC shows that there was no response from the carrier to INVITE messages.



      I sent the .pcap file to the carrier and they came back with the following:

      The short answer is that these Invites for outbound call setup are not reaching Granite. The outbound SIP Invite messages in this capture are very large (about 1723 byte payload) and so the local network device is fragmenting them in to two segments. With wireshark we can see the size/length of the fragments (1514+295; 1514+277, etc).
      the invite is actually being fragmented leaving the customer network. Can you see if the customer is able to reduce the size of the outbound invite to 1500 bytes?

      Is this something that can be controlled/modified by the SBC?

      ------------------------------
      Ted Hargiss
      Manager
      Landstar
      ------------------------------



    • 30.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-15-2020 09:48 AM
      Hi Ted,
      This what I mentioned in earlier messages, it can be done by Sigma script. 





    • 31.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-15-2020 09:52 AM
      Ted,
      I assume you are using UDP to transport the SIP message to the ITSP.  One limitation of UDP is that if all the information does not fit into a single packet, it does not get delivered.  The Maximum Transmission Unit (MTU) of Ethernet is 1,500 Bytes, and a typical  SIP message starts around 1,200 Bytes.  It sounds like yours are 1,723 Bytes.  This is a very common problem with SIP trunks to the PSTN..

      The solution is to remove SIP headers that have no value in the PSTN.  In general, those are any SIP headers that begin with AV- or  with P-  (with one exception: NEVER remove P-Asserted-Identity).

      If you download the document I referenced earlier (Super SigMa Scripting), there is an example which illustrates how to remove unwanted headers by using a script.

      ------------------------------
      John Waber
      Senior Technical Instructor
      ConvergeOne- Center of Excellence
      ------------------------------



    • 32.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-15-2020 10:03 AM
      Great! Thanks Arslan and John. I will look over the document. 

      I have not dealt with sigma scripts before. But, I'll give it a shot.

      ------------------------------
      Ted Hargiss
      Manager
      Landstar
      ------------------------------



    • 33.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 09-25-2020 10:01 AM
      Hi Ted,
      Curious to know the status on this topic, did you got this working finally?





    • 34.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 10-05-2020 12:30 PM
      Hey Arslan,

      I was able to get the service working. John's white paper on SigMa Scripts (mentioned earlier in this thread) helped out greatly. 
      By using his example, I created a new signal manipulation script and linked it to the server (service provider) and calls started flowing. 
      The script removes unused headers from outbound SIP messages, thereby reducing the MTU.

      ------------------------------
      Ted Hargiss
      Manager
      Landstar
      ------------------------------



    • 35.  RE: SBCE Registration Request - SIP Carrier/Provider

      Posted 12-29-2020 06:44 AM

      Hi Ted Hargiss,

      Apply below procedure to resolve your issue. Under server configuration profile for Trunk server, 

      Under Authentication window:
      • Select Enable Authentication
      • User Name: enter Authentication name for outbound proxy 1
      • Realm: value provide by SIP SP
      • Password and Confirm Password: enter Password provided by

      Under Heartbeat window:
      • Select Enable Heartbeat
      • Method: choose OPTIONS
      • Frequency: enter 600
      • From URI and To URI: enter SIP URI provided by SP 
      e.g. 0353950607@sipconn.test1.com

      Under Registration window:
      • Select Register with All Servers
      • Refresh Interval: enter 600
      • From URI and To URI: enter SIP URI provided by SP, e.g.,353950607@sipconn.test1.com

      Restart the SBCE application

      Validation: Under system status, you will be able to see trunk as registered.

      Hope this is helpful.

      Regards,

      Mangesh Kadam



      ------------------------------
      mangesh kadam
      Sr. Manager Projects
      CS Infocomm Pvt Ltd
      Mumbai
      ------------------------------