Unified Communications

 View Only
  • 1.  UDP Port range in IP-network-region & SBC

    Posted 11-19-2019 05:24 PM

    Hi all,

    When we first set up our CM 6.3 a few years back, we set up a small, physical SBC at the same time. (Now it's virtualized SBC/EMS.) Reviewing my notes, it looks like we used ports 35000-36000 for RTP/RTCP SRTP/STRCP connection between the SBC and CM/SM. No big deal, worked fine.

    In the mean time, we've grown our Avaya footprint and set up multiple new G450 & G430 gateways in a few other buildings. When I check the ip-network-regions that correspond to those new buildings, the UDP Port Min/Max fields are set with 2048-3329. Swell, it all works great.

    However, when I look at my original ip-network-region, I have an entry of 35000-36000 in the UDP Port Min/Max. Everything is still working fine, EXCEPT I can't make any changes in the ip-network-region because it tells me "Region is used by a g450 media gateway; UDP port range must be 1280 or greater."

    I'm thinking I should change those UDP port values to the default 2048-3329 (a 1282 port range), but I don't want to mess up anything in my SBC. What do you all think?

    Thank you as always!

    Chip



  • 2.  RE: UDP Port range in IP-network-region & SBC

    Posted 11-22-2019 09:37 AM
    Chip,

    The port numbers don't need to match on either side.  Traffic coming TO the SBC will be in the 35000 - 36000 range, and the traffic coming TO the MGs will be in the 2048-3329 range.  The default range for the SBCE is 35000 - 40000.  These are essentially just arbitrary numbers, but are important if there are any firewalls between the devices (you would need to open up the firewall for those specific UDP ranges for traffic to work right).  The other thing to note is that your range needs to be big enough to handle the amount of traffic you are expecting from that device.  35000 - 36000 allows for appx 500 simultaneous voice conversations (could be as much as 1,000, but you need to account for call recording, conference calls, etc to deduct from that number). 


    -Nick

    ------------------------------
    Nick Kwiatkowski
    Director of Design and Engineering
    Michigan State University
    ------------------------------



  • 3.  RE: UDP Port range in IP-network-region & SBC

    Posted 11-22-2019 12:07 PM
    "35000 - 36000 allows for appx 500 simultaneous voice conversations" sorry for the dumb question but does one conversation use up one port?  Is it a one to one ratio?

    ------------------------------
    Paul J
    telecom engineer
    Sage Software
    ------------------------------



  • 4.  RE: UDP Port range in IP-network-region & SBC

    Posted 11-23-2019 07:14 PM
    Hello Paul,

    Each conversation would have two streams of audio, hence each conversation uses 2 ports on each side 

    Thanks and best regards,
    Samy Nashaat R Mansour
    +61455991951





  • 5.  RE: UDP Port range in IP-network-region & SBC

    Posted 11-25-2019 04:06 PM
    So Nick, if you came across this in one of your IP-network-regions, and all your other IP-network-regions were 2048-3329, would you consider this an error, and change it? Again, everything is working OK, but I can't change the name of this IP-network-region because CM considers the current port entries invalid.




  • 6.  RE: UDP Port range in IP-network-region & SBC

    Posted 11-25-2019 04:07 PM
    @Nick Kwiatkowski ​​


  • 7.  RE: UDP Port range in IP-network-region & SBC

    Posted 11-25-2019 05:16 PM
    There should be no need to change it if everything is working well.  Only reason to really pay attention to it is if you are going through a firewall to get to either your endpoints or adjuncts.  The firewall would care for the range, but the rest shouldn't really matter.   They are just numbers to a computer and really don't mean much.

    ------------------------------
    Nick Kwiatkowski
    Michigan State University
    ------------------------------



  • 8.  RE: UDP Port range in IP-network-region & SBC

    Posted 12-05-2019 06:24 PM
    Yeah, I wouldn't sweat it except I wanted to change the name of the ip-network-region. I changed it earlier today and no issues. Thanks for the feedback.