NEC -Allowing 3rd party sip to register to PBX via to BX500 SBC

NEC -Allowing 3rd party sip to register to PBX via to BX500 SBC



NEC -Allowing  3rd party sip to register to PBX via to BX500 SBC


 you are using the BX500 for remote ST500 users and you have loaded the scripts 


In this scenario we are also using TCP for the  ST 500 connection In this case we are using TCP 58299 (instead of default 5070) for our north bound interface (this is port opened in the firewall)

Our southbound port is the standard 5070 to the phone system (Standard sip extension in 84-20-01)


A screenshot of a computerDescription automatically generated


When using the script  the default setting is for the northbound interface only accept user agents that match ST500 or ST400 only ( this means that the BX will only accepts the ST 500 registration invite only )ALL other attempts at registration by other products will be rejected 

This can be found in SETUP/SIGNALLING&MEDIA/SBC/CLASSIFICATION/

A screenshot of a computerDescription automatically generated


Each 3rd party device as part of there registration attempts announces who they are 

In this case MicroSIP

A screenshot of a computer codeDescription automatically generated


In this case 3CXPhone softphone 


In this case Yealink


A close up of a textDescription automatically generated


What we want to achieve is to allow this user agent to register on the BX 


SETUP/SIGNALLING&MEDIA/SBC/Classification – select one of the Classifications – it doesn’t matter which one as we are going to add it to both anyway 


Add a new rule 

For Micro Sip 

Name  :  User Agent Match to ST4XX , ST500 and MicroSIP

Condition : header.user-agent contains 'ST500' or header.user-agent contains 'ST450' or header.user-agent contains 'MicroSIP'


3Cx

Name  :  User Agent Match to ST4XX , ST500 and 3CXPhone

Condition : header.user-agent contains 'ST500' or header.user-agent contains 'ST450' or header.user-agent contains '3CXPhone'


Yealink


Name  :  User Agent Match to ST4XX , ST500 and Yealink

Condition : header.user-agent contains 'ST500' or header.user-agent contains 'ST450' or header.user-agent contains 'Yealink'


Or combination of the above 


Name  :  User Agent Match to ST4XX , ST500 Yealink and MircoSIP

Condition : header.user-agent contains 'ST500' or header.user-agent contains 'ST450' or header.user-agent contains ' Yealink' or header.user-agent contains 'MicroSIP' or header.user-agent contains '3CXPhone'








Now save 


Got to the InternalSTusers and add the newly created rule to that one 

A screenshot of a computerDescription automatically generated


So both these are now set to the new rule 



Then apply


Then save 

A blue and white rectangle with a black arrowDescription automatically generated










    • Related Articles

    • NEC -BX500-setup

      SBC – BX500 Installation Guide This is an article to set up a NEC BX500 to accept ST500 Apps to a NEC SL2100 / SV9100. The BX500 is placed on the same LAN segment such as: -NAT translation -Allowing only SIP packets with Message Header advertising ...
    • NEC-Telstra SIP Connect Non-IPVPN SIP over Internet

      Telstra Enterprise SIP Trunks Pre-requisite: SIP ALG disabled on the customers router Hardware / License required: SV9100: Quantity Description SV9100 CPU 1 System GPZ-IPLE 1 VoIP Media card to convert RTP packets BE114065-CP20 Per SIP trunk SV9100 ...
    • NEC SL2100 Telstra Business SIP

      NEC SL2100 Telstra Business SIP TIP: North bound issues, try setting registration from the OneAccess unit to the carrier using Secure SIP in the customer portal, this will hide any SIP traffic from SIP ALG in routers:
    • NEC SIP trunks - Aussie broadband

      How to add Aussie broadband SIP trunks to NEC SL/2100/SV9100 Remote Pre-requisite: SIP ALG disabled on the customers router Check SIP trunk credentials using a soft phone app, this will save a lot of time. Hardware / License required: SV9100: ...
    • NEC-SIP trunks - NETSIP

      NETSIP- SIP Trunks Pre-requisite: SIP ALG disabled on the customers router Method: NETSIP servers use one of many IP addresses, you register to one, however calls may come from another , causing the call to get blocked by your on site router. UDP ...