Setting up VOS3000 LRN server configuration with SS_LRN_SERVER_IP and SS_LRN_SERVER_PORT is the foundational step for enabling number portability lookups in your VOS3000 softswitch. These two parameters define the IP address and TCP/UDP port of the external LRN (Local Routing Number) dip server that VOS3000 queries before routing US termination calls. Without a properly configured LRN server connection, your VOS3000 system cannot perform number portability lookups, and all US calls will route based on the dialed number’s original rate center rather than the actual serving carrier. Need assistance? Contact us on WhatsApp: +8801911119966.
The LRN dip server is an external service — typically provided by a specialized NPAC (Number Portability Administration Center) query aggregator — that receives a dialed number query and returns the Local Routing Number identifying the current serving carrier. VOS3000 acts as an LRN client, sending queries to this server and processing the responses to make routing and billing decisions. The SS_LRN_SERVER_IP and SS_LRN_SERVER_PORT parameters, documented in §4.3.5.2 of the softswitch parameters manual, define where VOS3000 sends these queries.
The two primary parameters for VOS3000 LRN server configuration are defined in the softswitch configuration file. These are global parameters that apply to all mapping gateways using Internal LRN query mode.
| Parameter | Description | Default / Range |
|---|---|---|
| SS_LRN_SERVER_IP | IP address of the external LRN dip server | Empty (must be configured) |
| SS_LRN_SERVER_PORT | TCP/UDP port of the LRN dip server | Empty (must be configured) |
| Configuration File | Softswitch parameters (mbx2008.conf) | /etc/vos3000/mbx2008.conf |
| Manual Section | VOS3000 softswitch parameters reference | §4.3.5.2 |
| Scope | Global (applies to all gateways using Internal LRN) | System-wide |
VOS3000 does not include a built-in LRN database. The NPAC databases that store number portability records are managed by third-party administrators (such as Neustar/Iconectiv in the US) and are accessed through dedicated LRN query services. VOS3000 must connect to an external LRN dip server that has subscriptions to these NPAC databases. The LRN server receives the dialed number query, performs the NPAC lookup on behalf of VOS3000, and returns the LRN result. This architecture separates the softswitch routing logic from the number portability data management.
| Component | Role | Managed By |
|---|---|---|
| VOS3000 Softswitch | Sends LRN query, processes response, routes call | VoIP Operator |
| LRN Dip Server | Receives query, looks up NPAC, returns LRN | LRN Service Provider |
| NPAC Database | Master number portability records | Iconectiv / Neustar |
| Serving Carrier Switch | Terminates the call to the subscriber | Termination Carrier |
Follow these steps to configure SS_LRN_SERVER_IP and SS_LRN_SERVER_PORT in your VOS3000 system. Before starting, obtain the LRN server IP address and port number from your LRN service provider. For configuration help, message us on WhatsApp: +8801911119966.
| Step | Action | Command or Detail |
|---|---|---|
| 1 | Backup configuration | cp /etc/vos3000/mbx2008.conf /etc/vos3000/mbx2008.conf.bak |
| 2 | Open configuration file | vi /etc/vos3000/mbx2008.conf |
| 3 | Set LRN server IP | SS_LRN_SERVER_IP=203.0.113.50 |
| 4 | Set LRN server port | SS_LRN_SERVER_PORT=8443 |
| 5 | Save and close | :wq in vi |
| 6 | Restart softswitch service | service vos3000 restart |
| 7 | Test LRN connectivity | Place test call to ported number, check CDR for LRN field |
When a call arrives at a mapping gateway with Internal LRN query mode enabled, VOS3000 initiates an LRN lookup to the configured server. The softswitch sends a query containing the dialed number to the SS_LRN_SERVER_IP on the SS_LRN_SERVER_PORT. The LRN server processes the query against the NPAC database and returns the LRN for that number. VOS3000 then uses the returned LRN for prefix matching in the rate table and for gateway routing decisions. The entire LRN dip typically adds 20-100 milliseconds to call setup time depending on network latency to the LRN server. For understanding the broader call flow, see our VOS3000 SIP call flow guide.
| Lookup Phase | Action | Typical Duration |
|---|---|---|
| Query Send | VOS3000 sends dialed number to LRN server | 1-5 ms (local) / 10-30 ms (remote) |
| Server Processing | LRN server queries NPAC database | 5-50 ms |
| Response Receive | VOS3000 receives LRN response | 1-5 ms (local) / 10-30 ms (remote) |
| Routing Decision | VOS3000 uses LRN for rate/gateway lookup | 1-5 ms |
For VOS3000 LRN server configuration to work reliably, the VOS3000 softswitch server must have network connectivity to the LRN dip server on the specified IP and port. Firewall rules must allow outbound connections from the VOS3000 server to SS_LRN_SERVER_IP on SS_LRN_SERVER_PORT. The LRN service provider will typically specify whether the connection uses TCP or UDP and whether TLS encryption is required. Network latency between VOS3000 and the LRN server should be minimized to avoid adding excessive delay to call setup. (VOS3000 LRN Server Configuration)
| Requirement | Specification | Notes |
|---|---|---|
| Network Access | Outbound TCP/UDP to LRN server | Firewall must allow specified port |
| Latency | Under 50ms round-trip recommended | Higher latency increases PDD |
| TLS Support | Depends on LRN provider | Some providers require encrypted connections |
| Service Availability | 99.99% uptime SLA recommended | LRN downtime impacts all US calls |
When VOS3000 LRN server configuration problems occur, the most common symptom is that LRN lookups fail or timeout, causing calls to fall back to dialed-number routing. For deeper troubleshooting, check our CDR billing discrepancy guide and call termination reasons reference.
| Problem | Likely Cause | Solution |
|---|---|---|
| Connection refused | Wrong IP or port in SS_LRN_SERVER_IP/PORT | Verify IP and port with LRN provider |
| Connection timeout | Firewall blocking or network issue | Check firewall rules, test with telnet |
| LRN queries return empty | LRN server subscription issue | Contact LRN service provider |
| High PDD after LRN enable | High latency to LRN server | Use closer LRN server or reduce timeout |
| Config not taking effect | Service not restarted after change | Restart vos3000 service |
SS_LRN_SERVER_IP is a VOS3000 softswitch parameter that specifies the IP address of the external LRN (Local Routing Number) dip server. When a mapping gateway is configured for Internal LRN query mode, VOS3000 uses this IP address to connect to the LRN server and send number portability queries. This parameter is defined in the softswitch configuration file (mbx2008.conf) under section §4.3.5.2 of the VOS3000 manual. It must be set to the IP address provided by your LRN service provider.
The port number for SS_LRN_SERVER_PORT depends on your LRN service provider’s configuration. Common ports include 8443 for HTTPS-based LRN queries, 5060 for SIP-based queries, or custom ports specified by the provider. You should use the exact port number provided by your LRN service provider. Never guess or use default ports without confirming with the provider, as incorrect port configuration will cause all LRN queries to fail. (VOS3000 LRN Server Configuration)
Yes, changes to SS_LRN_SERVER_IP and SS_LRN_SERVER_PORT require a restart of the VOS3000 softswitch service to take effect. These parameters are read during softswitch initialization and are not reloaded dynamically. Use the command service vos3000 restart after making changes to the configuration file. Always schedule restarts during low-traffic periods to minimize call disruption.
The standard SS_LRN_SERVER_IP parameter supports a single LRN server endpoint. For high-availability deployments, operators typically configure a load balancer or DNS round-robin in front of multiple LRN server instances, and point SS_LRN_SERVER_IP to the virtual IP of the load balancer. This provides redundancy at the infrastructure level without requiring VOS3000 to manage multiple LRN connections directly. Some advanced LRN service providers offer their own failover endpoints.
To verify the LRN server connection, first test network connectivity using telnet SS_LRN_SERVER_IP SS_LRN_SERVER_PORT from the VOS3000 server. If the connection succeeds, place a test call to a known ported US number and inspect the CDR record. A working LRN configuration will show the LRN value in the CDR alongside the dialed number. If the CDR shows no LRN field or routing appears incorrect, check your softswitch logs for LRN query errors.
The protocol used for LRN queries depends on the LRN service provider and the configured SS_LRN_SERVER_PORT. Some providers use TCP-based proprietary protocols, while others use SIP-based queries or HTTP/HTTPS REST APIs. VOS3000 supports the query format specified by the LRN server it connects to. The specific protocol details and query format should be obtained from your LRN service provider documentation.
Configuring VOS3000 LRN server settings correctly is essential for accurate US termination routing. Incorrect SS_LRN_SERVER_IP or PORT values will prevent LRN lookups from functioning, causing all ported US numbers to be misrouted. Our team specializes in VOS3000 number portability configurations and can help you integrate with any LRN service provider. (VOS3000 LRN Server Configuration)
Contact us on WhatsApp: +8801911119966
From initial LRN server setup to troubleshooting existing configurations and optimizing query performance, we provide comprehensive support. Reach out today at +8801911119966 and ensure your VOS3000 system delivers accurate US termination routing.
For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:
📱 WhatsApp: +8801911119966
🌐 Website: www.vos3000.com
🌐 Blog: multahost.com/blog
📥 Downloads: VOS3000 Downloads
VOS3000 replace failed reason overrides SIP and H.323 error responses with custom codes. Replace 503 with 486 to prevent failover… Read More
VOS3000 call forward signal recognition with SS_RECOGNIZE_CALL_FORWARD_SIGNAL. Detect 181 Call Is Being Forwarded and 302 Moved Temporarily for billing. Read More
VOS3000 remote ring back mode configures ringback tone delivery with Passthrough, 183+SDP, or 180+SDP modes. Control early media and ringback… Read More
This website uses cookies.