{"id":1323,"date":"2026-04-21T06:40:09","date_gmt":"2026-04-21T06:40:09","guid":{"rendered":"https:\/\/www.vos3000.com\/blog\/?p=1323"},"modified":"2026-04-21T06:40:18","modified_gmt":"2026-04-21T06:40:18","slug":"vos3000-lrn-server-configuration-setup","status":"publish","type":"post","link":"https:\/\/www.vos3000.com\/blog\/vos3000-lrn-server-configuration-setup\/","title":{"rendered":"VOS3000 LRN Server Configuration Reliable SS_LRN_SERVER_IP PORT Setup"},"content":{"rendered":"\n<h1 class=\"wp-block-heading\" id=\"vos-3000-lrn-server-configuration-reliable-ss-lrn-server-ip-port-setup\">VOS3000 LRN Server Configuration Reliable SS_LRN_SERVER_IP PORT Setup<\/h1>\n\n\n\n<p>Setting up <strong>VOS3000 LRN server configuration<\/strong> 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&#8217;s original rate center rather than the actual serving carrier. Need assistance? Contact us on WhatsApp: <strong>+8801911119966<\/strong>.<\/p>\n\n\n\n<p>The LRN dip server is an external service \u2014 typically provided by a specialized NPAC (Number Portability Administration Center) query aggregator \u2014 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 \u00a74.3.5.2 of the softswitch parameters manual, define where VOS3000 sends these queries.<\/p>\n\n\n\n<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Table of Contents<\/h2><nav><ul><li><a href=\"#vos-3000-lrn-server-configuration-reliable-ss-lrn-server-ip-port-setup\">VOS3000 LRN Server Configuration Reliable SS_LRN_SERVER_IP PORT Setup<\/a><ul><li><a href=\"#vos-3000-lrn-server-configuration-parameter-reference\">VOS3000 LRN Server Configuration Parameter Reference<\/a><\/li><li><a href=\"#why-an-external-lrn-server-is-required\">Why an External LRN Server Is Required<\/a><\/li><li><a href=\"#step-by-step-lrn-server-configuration\">Step-by-Step VOS3000 LRN Server Configuration<\/a><\/li><li><a href=\"#how-vos-3000-sends-and-processes-lrn-lookups\">How VOS3000 Sends and Processes LRN Lookups<\/a><\/li><li><a href=\"#lrn-server-connectivity-requirements\">LRN Server Connectivity Requirements (VOS3000 LRN Server Configuration)<\/a><\/li><li><a href=\"#troubleshooting-lrn-server-connection-issues\">Troubleshooting LRN Server Connection Issues<\/a><\/li><li><a href=\"#related-resources\">Related Resources &#8211; VOS3000 LRN Server Configuration<\/a><\/li><li><a href=\"#frequently-asked-questions-about-vos-3000-lrn-server-configuration\">Frequently Asked Questions About VOS3000 LRN Server Configuration<\/a><ul><li><a href=\"#what-is-ss-lrn-server-ip-in-vos-3000\">What is SS_LRN_SERVER_IP in VOS3000?<\/a><\/li><li><a href=\"#what-port-should-i-use-for-ss-lrn-server-port\">What port should I use for SS_LRN_SERVER_PORT?<\/a><\/li><li><a href=\"#do-i-need-to-restart-vos-3000-after-changing-lrn-server-settings\">Do I need to restart VOS3000 after changing LRN server settings?<\/a><\/li><li><a href=\"#can-vos-3000-connect-to-multiple-lrn-servers-for-redundancy\">Can VOS3000 connect to multiple LRN servers for redundancy?<\/a><\/li><li><a href=\"#how-do-i-verify-the-lrn-server-connection-is-working\">How do I verify the LRN server connection is working?<\/a><\/li><li><a href=\"#what-protocol-does-vos-3000-use-for-lrn-queries\">What protocol does VOS3000 use for LRN queries?<\/a><\/li><\/ul><\/li><li><a href=\"#get-professional-vos-3000-lrn-server-setup\">Get Professional VOS3000 LRN Server Setup<\/a><\/li><li><a href=\"#\ud83d\udcde-need-call-center-setup-support\">\ud83d\udcde Need Professional VOS3000 Setup Support?<\/a><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"vos-3000-lrn-server-configuration-parameter-reference\">VOS3000 LRN Server Configuration Parameter Reference<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Parameter<\/th><th class=\"has-text-align-left\" data-align=\"left\">Description<\/th><th class=\"has-text-align-left\" data-align=\"left\">Default \/ Range<\/th><\/tr><tr><td>SS_LRN_SERVER_IP<\/td><td>IP address of the external LRN dip server<\/td><td>Empty (must be configured)<\/td><\/tr><tr><td>SS_LRN_SERVER_PORT<\/td><td>TCP\/UDP port of the LRN dip server<\/td><td>Empty (must be configured)<\/td><\/tr><tr><td>Configuration File<\/td><td>Softswitch parameters (mbx2008.conf)<\/td><td>\/etc\/vos3000\/mbx2008.conf<\/td><\/tr><tr><td>Manual Section<\/td><td>VOS3000 softswitch parameters reference<\/td><td>\u00a74.3.5.2<\/td><\/tr><tr><td>Scope<\/td><td>Global (applies to all gateways using Internal LRN)<\/td><td>System-wide<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"why-an-external-lrn-server-is-required\">Why an External LRN Server Is Required<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Component<\/th><th class=\"has-text-align-left\" data-align=\"left\">Role<\/th><th class=\"has-text-align-left\" data-align=\"left\">Managed By<\/th><\/tr><tr><td>VOS3000 Softswitch<\/td><td>Sends LRN query, processes response, routes call<\/td><td>VoIP Operator<\/td><\/tr><tr><td>LRN Dip Server<\/td><td>Receives query, looks up NPAC, returns LRN<\/td><td>LRN Service Provider<\/td><\/tr><tr><td>NPAC Database<\/td><td>Master number portability records<\/td><td>Iconectiv \/ Neustar<\/td><\/tr><tr><td>Serving Carrier Switch<\/td><td>Terminates the call to the subscriber<\/td><td>Termination Carrier<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"step-by-step-lrn-server-configuration\">Step-by-Step VOS3000 LRN Server Configuration<\/h2>\n\n\n\n<p>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: <strong>+8801911119966<\/strong>.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Step<\/th><th class=\"has-text-align-left\" data-align=\"left\">Action<\/th><th class=\"has-text-align-left\" data-align=\"left\">Command or Detail<\/th><\/tr><tr><td>1<\/td><td>Backup configuration<\/td><td>cp \/etc\/vos3000\/mbx2008.conf \/etc\/vos3000\/mbx2008.conf.bak<\/td><\/tr><tr><td>2<\/td><td>Open configuration file<\/td><td>vi \/etc\/vos3000\/mbx2008.conf<\/td><\/tr><tr><td>3<\/td><td>Set LRN server IP<\/td><td>SS_LRN_SERVER_IP=203.0.113.50<\/td><\/tr><tr><td>4<\/td><td>Set LRN server port<\/td><td>SS_LRN_SERVER_PORT=8443<\/td><\/tr><tr><td>5<\/td><td>Save and close<\/td><td>:wq in vi<\/td><\/tr><tr><td>6<\/td><td>Restart softswitch service<\/td><td>service vos3000 restart<\/td><\/tr><tr><td>7<\/td><td>Test LRN connectivity<\/td><td>Place test call to ported number, check CDR for LRN field<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"how-vos-3000-sends-and-processes-lrn-lookups\">How VOS3000 Sends and Processes LRN Lookups<\/h2>\n\n\n\n<p>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 <a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-call-flow\/\" target=\"_blank\" rel=\"noopener\">VOS3000 SIP call flow guide<\/a>.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Lookup Phase<\/th><th class=\"has-text-align-left\" data-align=\"left\">Action<\/th><th class=\"has-text-align-left\" data-align=\"left\">Typical Duration<\/th><\/tr><tr><td>Query Send<\/td><td>VOS3000 sends dialed number to LRN server<\/td><td>1-5 ms (local) \/ 10-30 ms (remote)<\/td><\/tr><tr><td>Server Processing<\/td><td>LRN server queries NPAC database<\/td><td>5-50 ms<\/td><\/tr><tr><td>Response Receive<\/td><td>VOS3000 receives LRN response<\/td><td>1-5 ms (local) \/ 10-30 ms (remote)<\/td><\/tr><tr><td>Routing Decision<\/td><td>VOS3000 uses LRN for rate\/gateway lookup<\/td><td>1-5 ms<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"lrn-server-connectivity-requirements\">LRN Server Connectivity Requirements (VOS3000 LRN Server Configuration)<\/h2>\n\n\n\n<p>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.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Requirement<\/th><th class=\"has-text-align-left\" data-align=\"left\">Specification<\/th><th class=\"has-text-align-left\" data-align=\"left\">Notes<\/th><\/tr><tr><td>Network Access<\/td><td>Outbound TCP\/UDP to LRN server<\/td><td>Firewall must allow specified port<\/td><\/tr><tr><td>Latency<\/td><td>Under 50ms round-trip recommended<\/td><td>Higher latency increases PDD<\/td><\/tr><tr><td>TLS Support<\/td><td>Depends on LRN provider<\/td><td>Some providers require encrypted connections<\/td><\/tr><tr><td>Service Availability<\/td><td>99.99% uptime SLA recommended<\/td><td>LRN downtime impacts all US calls<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"troubleshooting-lrn-server-connection-issues\">Troubleshooting LRN Server Connection Issues<\/h2>\n\n\n\n<p>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 <a href=\"https:\/\/multahost.com\/blog\/vos3000-cdr-billing-discrepancy\/\" target=\"_blank\" rel=\"noopener\">CDR billing discrepancy guide<\/a> and <a href=\"https:\/\/multahost.com\/blog\/vos3000-call-termination-reasons\/\" target=\"_blank\" rel=\"noopener\">call termination reasons reference<\/a>.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><th class=\"has-text-align-left\" data-align=\"left\">Problem<\/th><th class=\"has-text-align-left\" data-align=\"left\">Likely Cause<\/th><th class=\"has-text-align-left\" data-align=\"left\">Solution<\/th><\/tr><tr><td>Connection refused<\/td><td>Wrong IP or port in SS_LRN_SERVER_IP\/PORT<\/td><td>Verify IP and port with LRN provider<\/td><\/tr><tr><td>Connection timeout<\/td><td>Firewall blocking or network issue<\/td><td>Check firewall rules, test with telnet<\/td><\/tr><tr><td>LRN queries return empty<\/td><td>LRN server subscription issue<\/td><td>Contact LRN service provider<\/td><\/tr><tr><td>High PDD after LRN enable<\/td><td>High latency to LRN server<\/td><td>Use closer LRN server or reduce timeout<\/td><\/tr><tr><td>Config not taking effect<\/td><td>Service not restarted after change<\/td><td>Restart vos3000 service<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"related-resources\">Related Resources &#8211; VOS3000 LRN Server Configuration<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-sip-call-flow\/\" target=\"_blank\" rel=\"noopener\">VOS3000 SIP Call Flow Guide<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-call-termination-reasons\/\" target=\"_blank\" rel=\"noopener\">VOS3000 Call Termination Reasons<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/multahost.com\/blog\/vos3000-cdr-billing-discrepancy\/\" target=\"_blank\" rel=\"noopener\">VOS3000 CDR Billing Discrepancy<\/a><\/li>\n\n\n\n<li><a href=\"https:\/\/datatracker.ietf.org\/doc\/html\/rfc3482\" target=\"_blank\" rel=\"noopener\">RFC 3482 &#8211; Number Portability Framework<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"frequently-asked-questions-about-vos-3000-lrn-server-configuration\">Frequently Asked Questions About VOS3000 LRN Server Configuration<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"what-is-ss-lrn-server-ip-in-vos-3000\">What is SS_LRN_SERVER_IP in VOS3000?<\/h3>\n\n\n\n<p>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 \u00a74.3.5.2 of the VOS3000 manual. It must be set to the IP address provided by your LRN service provider.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"what-port-should-i-use-for-ss-lrn-server-port\">What port should I use for SS_LRN_SERVER_PORT?<\/h3>\n\n\n\n<p>The port number for SS_LRN_SERVER_PORT depends on your LRN service provider&#8217;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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"do-i-need-to-restart-vos-3000-after-changing-lrn-server-settings\">Do I need to restart VOS3000 after changing LRN server settings?<\/h3>\n\n\n\n<p>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 <code>service vos3000 restart<\/code> after making changes to the configuration file. Always schedule restarts during low-traffic periods to minimize call disruption.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"can-vos-3000-connect-to-multiple-lrn-servers-for-redundancy\">Can VOS3000 connect to multiple LRN servers for redundancy?<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"how-do-i-verify-the-lrn-server-connection-is-working\">How do I verify the LRN server connection is working?<\/h3>\n\n\n\n<p>To verify the LRN server connection, first test network connectivity using <code>telnet SS_LRN_SERVER_IP SS_LRN_SERVER_PORT<\/code> 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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"what-protocol-does-vos-3000-use-for-lrn-queries\">What protocol does VOS3000 use for LRN queries?<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"get-professional-vos-3000-lrn-server-setup\">Get Professional VOS3000 LRN Server Setup<\/h2>\n\n\n\n<p>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)<\/p>\n\n\n\n<p><strong>Contact us on WhatsApp: +8801911119966<\/strong><\/p>\n\n\n\n<p>From initial LRN server setup to troubleshooting existing configurations and optimizing query performance, we provide comprehensive support. Reach out today at <strong>+8801911119966<\/strong> and ensure your VOS3000 system delivers accurate US termination routing.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"\ud83d\udcde-need-call-center-setup-support\">\ud83d\udcde Need Professional VOS3000 Setup Support?<\/h2>\n\n\n\n<p>For professional VOS3000 installations and deployment, VOS3000 Server Rental Solution:<\/p>\n\n\n\n<p>\ud83d\udcf1 <strong>WhatsApp:<\/strong> <a href=\"https:\/\/wa.me\/8801911119966\" target=\"_blank\" rel=\"noopener\">+8801911119966<\/a><br>\ud83c\udf10 <strong>Website:<\/strong> <a href=\"https:\/\/www.vos3000.com\">www.vos3000.com<\/a><br>\ud83c\udf10 <strong>Blog:<\/strong> <a href=\"https:\/\/multahost.com\/blog\" target=\"_blank\" rel=\"noopener\">multahost.com\/blog<\/a><br>\ud83d\udce5 <strong>Downloads:<\/strong> <a href=\"https:\/\/www.vos3000.com\/downloads.php\">VOS3000 Downloads<\/a><\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-VOS3000-LRN-Server-Configuration-VOS3000-Server-Side-End-Reasons-VOS3000-H323-Q850-Cause-Codes-VOS3000-SIP-Response-Codes-CDR-1024x683.png\" alt=\"VOS3000 LRN Number Portability, VOS3000 LRN Server Configuration, VOS3000 Server-Side End Reasons, VOS3000 H323 Q850 Cause Codes, VOS3000 SIP Response Codes CDR\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-VOS3000-LRN-Server-Configuration-VOS3000-Server-Side-End-Reasons-VOS3000-H323-Q850-Cause-Codes-VOS3000-SIP-Response-Codes-CDR-1024x683.png\" alt=\"VOS3000 LRN Number Portability, VOS3000 LRN Server Configuration, VOS3000 Server-Side End Reasons, VOS3000 H323 Q850 Cause Codes, VOS3000 SIP Response Codes CDR\"><\/td><td><img decoding=\"async\" src=\"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-VOS3000-LRN-Server-Configuration-VOS3000-Server-Side-End-Reasons-VOS3000-H323-Q850-Cause-Codes-VOS3000-SIP-Response-Codes-CDR-1024x683.png\" alt=\"VOS3000 LRN Number Portability, VOS3000 LRN Server Configuration, VOS3000 Server-Side End Reasons, VOS3000 H323 Q850 Cause Codes, VOS3000 SIP Response Codes CDR\"><\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>VOS3000 LRN server configuration with SS_LRN_SERVER_IP and PORT parameters. Set up external LRN dip server for US number portability queries and termination routing.<\/p>\n","protected":false},"author":1,"featured_media":1318,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_kadence_starter_templates_imported_post":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[2],"tags":[7579,7575,7596,7574,7615,7588,7609,7614,7612,7587,7591,7581,7607,7616,7605,7593,7580,7602,7599,7598,7584,7611,7597,7576,7604,7594,7578,7618,7586,7620,7577,7590,7619,7589,7601,7600,7583,7592,7582,7606,7617,7613,7585,7603,7595,7608,7610],"class_list":["post-1323","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vos3000","tag-ss_lrn_server_ip","tag-ss_lrn_server_port","tag-vos3000-carrier-lookup-server","tag-vos3000-external-lrn-server","tag-vos3000-h323-lrn-server","tag-vos3000-lnp-server","tag-vos3000-local-routing-number-server","tag-vos3000-lrn-billing-server","tag-vos3000-lrn-cache-server","tag-vos3000-lrn-connection","tag-vos3000-lrn-dip-configuration","tag-vos3000-lrn-dip-server","tag-vos3000-lrn-dip-timeout","tag-vos3000-lrn-high-availability","tag-vos3000-lrn-ip-address","tag-vos3000-lrn-lookup-server","tag-vos3000-lrn-parameter","tag-vos3000-lrn-port-number","tag-vos3000-lrn-protocol","tag-vos3000-lrn-query-endpoint","tag-vos3000-lrn-query-server","tag-vos3000-lrn-response-server","tag-vos3000-lrn-routing-server","tag-vos3000-lrn-server-configuration","tag-vos3000-lrn-server-connectivity","tag-vos3000-lrn-server-failover","tag-vos3000-lrn-server-ip","tag-vos3000-lrn-server-monitoring","tag-vos3000-lrn-server-port","tag-vos3000-lrn-server-port-range","tag-vos3000-lrn-server-setup","tag-vos3000-lrn-server-timeout","tag-vos3000-lrn-server-troubleshooting","tag-vos3000-lrn-service-provider","tag-vos3000-lrn-tcp-udp","tag-vos3000-mbx2008-lrn","tag-vos3000-npac-server","tag-vos3000-number-portability-database","tag-vos3000-number-portability-server","tag-vos3000-ported-number-server","tag-vos3000-rate-lookup-lrn","tag-vos3000-sip-lrn-server","tag-vos3000-softswitch-lrn","tag-vos3000-softswitch-parameter-lrn","tag-vos3000-us-termination-lrn","tag-vos3000-voip-lrn-configuration","tag-vos3000-wholesale-lrn-server"],"acf":[],"jetpack_featured_media_url":"https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability.png","blog_post_layout_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-150x150.png",150,150,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability.png",1536,1024,false]},"categories_names":{"2":{"name":"VOS3000`","link":"https:\/\/www.vos3000.com\/blog\/category\/vos3000\/"}},"tags_names":{"7579":{"name":"SS_LRN_SERVER_IP","link":"https:\/\/www.vos3000.com\/blog\/tag\/ss_lrn_server_ip\/"},"7575":{"name":"SS_LRN_SERVER_PORT","link":"https:\/\/www.vos3000.com\/blog\/tag\/ss_lrn_server_port\/"},"7596":{"name":"VOS3000 carrier lookup server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-carrier-lookup-server\/"},"7574":{"name":"VOS3000 external LRN server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-external-lrn-server\/"},"7615":{"name":"VOS3000 H323 LRN server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-h323-lrn-server\/"},"7588":{"name":"VOS3000 LNP server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lnp-server\/"},"7609":{"name":"VOS3000 local routing number server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-local-routing-number-server\/"},"7614":{"name":"VOS3000 LRN billing server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-billing-server\/"},"7612":{"name":"VOS3000 LRN cache server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-cache-server\/"},"7587":{"name":"VOS3000 LRN connection","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-connection\/"},"7591":{"name":"VOS3000 LRN dip configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-dip-configuration\/"},"7581":{"name":"VOS3000 LRN dip server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-dip-server\/"},"7607":{"name":"VOS3000 LRN dip timeout","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-dip-timeout\/"},"7616":{"name":"VOS3000 LRN high availability","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-high-availability\/"},"7605":{"name":"VOS3000 LRN IP address","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-ip-address\/"},"7593":{"name":"VOS3000 LRN lookup server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-lookup-server\/"},"7580":{"name":"VOS3000 LRN parameter","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-parameter\/"},"7602":{"name":"VOS3000 LRN port number","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-port-number\/"},"7599":{"name":"VOS3000 LRN protocol","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-protocol\/"},"7598":{"name":"VOS3000 LRN query endpoint","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-query-endpoint\/"},"7584":{"name":"VOS3000 LRN query server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-query-server\/"},"7611":{"name":"VOS3000 LRN response server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-response-server\/"},"7597":{"name":"VOS3000 LRN routing server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-routing-server\/"},"7576":{"name":"VOS3000 LRN server configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-configuration\/"},"7604":{"name":"VOS3000 LRN server connectivity","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-connectivity\/"},"7594":{"name":"VOS3000 LRN server failover","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-failover\/"},"7578":{"name":"VOS3000 LRN server IP","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-ip\/"},"7618":{"name":"VOS3000 LRN server monitoring","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-monitoring\/"},"7586":{"name":"VOS3000 LRN server port","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-port\/"},"7620":{"name":"VOS3000 LRN server port range","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-port-range\/"},"7577":{"name":"VOS3000 LRN server setup","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-setup\/"},"7590":{"name":"VOS3000 LRN server timeout","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-timeout\/"},"7619":{"name":"VOS3000 LRN server troubleshooting","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-server-troubleshooting\/"},"7589":{"name":"VOS3000 LRN service provider","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-service-provider\/"},"7601":{"name":"VOS3000 LRN TCP UDP","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-lrn-tcp-udp\/"},"7600":{"name":"VOS3000 mbx2008 LRN","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-mbx2008-lrn\/"},"7583":{"name":"VOS3000 NPAC server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-npac-server\/"},"7592":{"name":"VOS3000 number portability database","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-number-portability-database\/"},"7582":{"name":"VOS3000 number portability server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-number-portability-server\/"},"7606":{"name":"VOS3000 ported number server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-ported-number-server\/"},"7617":{"name":"VOS3000 rate lookup LRN","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-rate-lookup-lrn\/"},"7613":{"name":"VOS3000 SIP LRN server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-sip-lrn-server\/"},"7585":{"name":"VOS3000 softswitch LRN","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-softswitch-lrn\/"},"7603":{"name":"VOS3000 softswitch parameter LRN","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-softswitch-parameter-lrn\/"},"7595":{"name":"VOS3000 US termination LRN","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-us-termination-lrn\/"},"7608":{"name":"VOS3000 VoIP LRN configuration","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-voip-lrn-configuration\/"},"7610":{"name":"VOS3000 wholesale LRN server","link":"https:\/\/www.vos3000.com\/blog\/tag\/vos3000-wholesale-lrn-server\/"}},"comments_number":"0","wpmagazine_modules_lite_featured_media_urls":{"thumbnail":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-150x150.png",150,150,true],"cvmm-medium":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-300x300.png",300,300,true],"cvmm-medium-plus":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-305x207.png",305,207,true],"cvmm-portrait":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-400x600.png",400,600,true],"cvmm-medium-square":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-600x600.png",600,600,true],"cvmm-large":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-1024x1024.png",1024,1024,true],"cvmm-small":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability-130x95.png",130,95,true],"full":["https:\/\/www.vos3000.com\/blog\/wp-content\/uploads\/2026\/04\/VOS3000-LRN-Number-Portability.png",1536,1024,false]},"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1323","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/comments?post=1323"}],"version-history":[{"count":1,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1323\/revisions"}],"predecessor-version":[{"id":1327,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/posts\/1323\/revisions\/1327"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media\/1318"}],"wp:attachment":[{"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/media?parent=1323"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/categories?post=1323"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vos3000.com\/blog\/wp-json\/wp\/v2\/tags?post=1323"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}