Questions Kwebbl SIP Trunk

By default for every customer is a whitelist active for safety reasons. Please find below an overview of all default whitelisted destinations in case no whitelist is selected for a company. If you would like to add a destination, you are able to create your own whitelist in the Provider and Reseller panel. Albania Kosovo Andorra Latvia Argentina Liechtenstein Aruba Luxembourg Australia Macedonia Austria Malta Belgium ...

If outbound calls are anonymous while you want to send your own CallerID, there are a couple things to check. 1. Is the CallerID set in the PBX also added to the SIP Trunk settings on Kwebbl? 2. Is the CallerID set in the PBX in E.164 format? (eg. 31201234567)? 3. Is anonymous calling disabled in the PBX? After these settings are checked and the issue still occurs, please raise a ticket. We would appreciate receiving answers on the questions above and also if available a log from the ...

CLI settings Using the Kwebbl SIP Trunk, please keep in mind that there is no number normalization at the Kwebbl side as you are used to with a SIP device. This means that you should adjust the number format to E.164 (eg. 31201234567) in your own PBX. You can ty calling to a number in E.164 format to check if outbound calls are possible. If so, then you should check the settings in your PBX to adjust an outgoing call starting with 0 will be transferred into eg. 31. P-Asserted Identity B...

If a customer uses a SIP trunk and they cannot receive incoming calls after a certain time being idle, then it is most likely that the firewall is configured with a UDP port closing timer. Probably are incoming calls possible after making an outbound call. If this is the case, the firewall should be checked on the settings of the UDP port closing timer. We advise to configure the registration time in the PBX to 300 seconds. In the firewall the UDP port closing timer must be higher than the r...