UNO Communications: portability and NUE112
Configure FTP portability flows, operational tasks, and ETNA/NUE112 number publication.
Last updated: 2026-08-19
Two separate workflows
UNO Communications covers two distinct processes: incoming/outgoing portability exchange through FTP and ETNA/NUE112 number comparison and publication through APIs. FTP credentials do not enable NUE112, and NUE112 credentials do not start portability downloads.
FTP setup and downloads
Enter the provider host, port, username, and password, then verify environment, protocol, server access, and agreed directories. Scheduled processing downloads the previous day’s IN and OUT files.
The settings page also supports a manual date range and runs IN before OUT while displaying progress. Use narrow recovery periods and avoid overlap with scheduled processing.
Incoming portability
The IN list exposes the provider order, telephone number, workflow state, and relevant dates. Use these values together with the associated customer and DID to determine what still requires attention.
Mark completed is a manual internal closure. Use it only after verifying the provider outcome, number activation, local DID state, customer service, and any final task. It does not send a completion request to UNO Communications and must not be used simply to clear an old row.
Outgoing portability
The OUT list tracks numbers leaving the ISP and includes an internal managed flag. Marking a case as managed means an operator has reviewed or taken responsibility for it; it does not prove that the donating process has completed externally.
Before releasing a DID, terminating the linked service, or closing the customer record, confirm the provider’s final state and effective date. Preserve billing and traffic history required by the ISP’s retention policy, and make sure that a pending outbound case is not mistaken for an already transferred number.
Automatic tasks
Task settings can create an activity for qualifying incoming portability cases and require at least one assignee. Select operators with the appropriate permission and define priority, deadline, backup ownership, and closure criteria before enabling automation.
NUE112 credentials and security
NUE112 setup requires username, password, API URL, Dealer ID, and the UNO-assigned VoIP Service ID. A saved password is not rendered back to the page. Authentication obtains a temporary JWT for the current request without storing it, and SSL verification remains enabled.
NUE112 list and DID comparison
The list compares provider records with local DIDs using Present on both, To publish, and NUE112 only. It also shows customer, local DID status, activation date, and number, line, and network states.
Investigate NUE112-only records before acting: they may be historical, belong to another context, or reveal a missing local DID.
Publish a DID
For a To-publish record, open the preview and verify number, customer, and identity data produced from VoIP mappings. Confirming sends the new record to NUE112. Refresh and verify that it becomes Present on both.
The module currently supports list, status, preview, and single-number publication, but not remote edit or delete.
Mappings and number normalization
NUE112 payloads depend on the DID, customer, and VoIP identity mappings, so configure birth and tax data first. Italian comparison removes country prefix 39 when the national number begins with 0; this prevents formatting mismatches but does not repair an incorrect DID.
Automations and functional limits
Scheduled portability processing downloads the agreed previous-day IN and OUT files, while the manual date-range command is intended for controlled recovery. Avoid overlapping the two: check current processing and use the narrowest missing period so the same files are not handled repeatedly.
NUE112 authentication obtains a temporary token for the current request and keeps SSL verification enabled. The module provides listing, comparison, status, preview, and publication of one DID. Remote edit and deletion are not part of this workflow; use the provider’s authorized procedure when a published record must be corrected or removed.
After every automated or manual run, review timestamps, imported rows, unmatched numbers, generated tasks, and provider/local differences. A completed job only proves that processing ended, not that every number is operationally aligned.
Checklist
- Separate FTP and NUE112 setup
- Protect credentials
- Verify FTP environment and directories
- Assign portability task owners
- Check provider outcome before changing services
- Configure VoIP identity mappings
- Use the correct Dealer and Service IDs
- Review local/provider differences
- Confirm the preview before publication
- Verify Present on both afterward
- Use the provider process for unsupported edit or delete operations