Outbound Calling Issues
Diagnoses and fixes outbound calls or Queue Callback Assist calls that fail to connect because a NetSapiens user has no Caller ID set.
The most common reason an outbound call or a Queue Callback Assist call fails to connect is that the NetSapiens user placing it has no Caller ID set. The termination carrier rejects the call without one.
Accessing User Configuration
- Log in to the NetSapiens Admin (NMS) Portal at
https://<FQDN>/SiPbx/adminlogin.php
Separate Login CredentialsThe Admin (NMS) Portal uses different login credentials than the NetSapiens Manager Portal. The NetSapiens partner responsible for the deployment can provide these if they aren't already known.
- Select
Users, thenConfiguration
Setting Caller ID for One or a Few Users
- From the
Userspage, select the user to edit - On that user's configuration screen, complete
Caller ID Name,Caller ID Number, and911 Caller ID - Select
Modify - Repeat for each affected user
Setting Caller ID for a Group of Users
Correcting many users at once is done by exporting their configuration, editing it, and importing it back.
- From
Users > Configuration, selectExportin the bottom right - Select the desired
Domain(or*for all domains), then selectStart Export— this generates a CSV file - In the CSV, locate the
callid_nmbrandcallid_emgrcolumns - Enter the appropriate
callid_nmbrfor each user — this value is found under the regular portal'sInventorysection - Save the edited CSV
- Return to
Users > Configurationand selectImportin the bottom right - Upload the edited CSV and select
Start Import - When prompted to purge:
| Choice | Description |
|---|---|
| No | Retains existing values not present in the import |
| Yes | Overwrites everything — only intentional if that's the goal |
Updated about 2 hours ago
