| Field Name | Description | Example |
| Gateway name | The name of the gateway used for receiving or sending external calls. | |
| Profile | Select the SIP profile whose configuration is used for handling calls. | |
| Register | Defines whether the gateway should register with the SIP provider. | |
| Username | The username used for authentication with the SIP gateway | |
| Password | The password required to authenticate with the SIP gateway. | |
| Auth username | A specific username used for SIP authentication, separate from the main username if any. | |
| From user | User identity that appears in the ‘From’ field of SIP messages. | |
| From domain | Domain associated with the ‘From’ field in SIP messages. It could be either ip address or domain. | |
| Proxy | The domain or IP address used as an intermediary for call routing. | |
| Register proxy | The proxy server used for handling SIP registrations. | |
| Outbound proxy | A proxy server specifically for handling outbound SIP requests. | |
| Realm | The domain or IP address used for authentication in SIP communications. | |
| Register transport | Transport method for SIP registration. | |
| Codec prefs | This parameter used to define the preferred audio codecs. It allows you to specify which codecs should be used for media negotiation between endpoints. | |
| Ping | Settings for SIP ping functionality. | |
| Ping min | The minimum acceptable SIP ping time. | |
| Ping max | The maximum acceptable SIP ping time. | |
| Contact in ping | Handling of contact settings within SIP pings. | |
| Expire seconds | The time in seconds before a SIP registration expires and needs renewal. | |
| Retry seconds | The interval in seconds before retrying a failed registration attempt. | |
| Distinct to | Determines whether calls should be handled based on distinct ‘To’ headers. | |
| Extension | This parameter is used to control the ‘Contact’ information in SIP registration. If the default behavior registers as gw+gateway_name@ip and causes issues, setting extension here will enforce the format extension@ip. If the extension is blank, it defaults to username@ip. The ‘Contact’ header will be sent as: Contact: <sip:9988776655@7.7.7.7:7080> | |
| Extension in contact | This parameter is used to control the ‘Contact’ information in SIP registration. If the default behavior registers as gw+gateway_name@ip and causes issues, setting this parameter to true will enforce the format extension@ip. If the extension is blank, it defaults to username@ip. The ‘Contact’ header will be sent as: Contact: <sip:9988776655@7.7.7.7:7080> | |
| Caller id in from | This controls whether the Caller ID (CID) is placed in the From header of SIP messages.This ensures that the Caller ID is included in the From header, which some SIP providers or devices require for proper identification. | |
| Sip cid type | It defines how Caller ID (CID) is presented in SIP signaling. It controls where the caller ID information is placed in the SIP headers | |
| Contact Params | This setting defines custom parameters added to the ‘Contact’ header in SIP messages. It is useful for registering endpoints with additional parameters in the ‘Contact’ header, which may be required by some service providers. For example: foo=bar;rinstance=abc123. The ‘Contact’ header will be sent as: Contact: <sip:extension@192.168.1.100:5060;foo=bar;rinstance=abc123> | |
| Description | A brief description or notes for reference and context for this configuration |
© 2025 Nebero. All Rights Reserved.