2025 Updates - Service Provider Platform

February 2025

Custom SMTP server support

Added a new feature where custom SMTP servers can be added to the Orchestrator. These SMTP servers can be used to deliver email notifications used by templates.

The list of SMTP servers can be found on the E-Mail page in the General menu.  The Peeredge Default SMTP server will always be present in this list and can always be used. Once a new SMTP server has been added it can be set as the default SMTP server.  This will change (toggle) the configured email server for all existing Templates.

To add a new SMTP server click on the + Add button, fill in the appropriate fields and click the Add SMTP Server button.

The Orchestrator will add the new SMTP server to the list of servers after successfully testing the connection. If there is an issue with the connection the following error message will be displayed.

From any Template you can override the default setting, simply select the SMTP Server to use from the SMTP Server drop-down list in the Email Info step of the Template. If the Peeredge Default server is selected, then the From Email Address field can be populated with any customer email address otherwise the username from the SMTP server configuration will be used as the From Email Address and it cannot be edited.

A Test-SMTP option has been added to the horizonal ellipsis pop-up menu for the SMTP Servers. 

Add the email address of the recipient to send the test email.  The From Address will contain the username configured for the SMTP server.

Vendor Billing Account Number (BAN)

Added a Vendor BAN field to Termination Vendor Trunk Groups.  The BAN field will allow the association of a vendor BAN to each Termination Vendor Trunk Group.  This is especially helpful when you receive multiple invoices from a vendor, each with different BANs. You will now be able to map each invoice to the correct Termination Vendor Trunk Group. 

General Improvements and Bug Fixes for February 2025:

Improved input validation for LATA entries in LATA lists (Service Provider Platform).  

The LATA validation now supports 3 to 5 characters in the range [0-9,a-z,A-Z].

Improved MCL Template delete notification error messages when attempting to delete an MCL in an Origination Route Plan that is associated to an existing termination route plan.

Previous error message.

New error message

Improved Numbering and Number Forwarding CSV upload processing.

The CSV file upload process for Numbering and Number forwarding entries to Origination Route Plans has been completely overhauled improving the error handling and decreasing the processing time required to complete the upload process.