RTC Factory
From Pbxnsip Wiki
Contents |
Information about the Provider
RTC Factory AB (RTC) provides vendor independent VoIP infrastructure, enabling our resellers to offer a highly competitive IP telephony to their customers within 4 - 6 weeks.
RTC is located in Sweden, Australia and South Africa.
The service can be used behind NAT.
Trunk Setup
RTC usually provides you with a number of DID numbers. Each of them must be registered, that means you must set up a trunk for each number.
A sample trunk setup is shown on the following picture:
"Name" and "Type": We chose a name that includes the DID number to avoid confusions when selecting the trunk. The "Type" must be a registration.
The "Display Name", the "Account" and the "Username" should be set to the DID number. The "Password" is the password which has been provided along with the account. The domain name is provided by RTC and usually contains the customer name.
The "Outbound Proxy" is also provided by RTC and it is usually "x.rtcfactory.com".
If you want to monitor the line, you may assign a CO-line name. Be careful that you are not mixing the name of the line up with the name of an extension. For example, you can call the CO-line "co_0842095123" to avoid confusions.
Do not enter a STUN server. RTC is taking care about NAT refresh.
We recommend entering a "Keepalive Time". The default value provided by RTC is one hour, which we believe is too high in case that a refresh packet did not make it to the PBX. Also, you should slightly vary the keep alive-time slightly between the trunks, so that the re-registration traffic does not create bursts (for example, for one trunk you choose 300, for the next 299, for the next 298 and so on).
The settings "Strict RTP Routing", "Avoid RFC 4122" and "Accept redirect" should not be changed. Also you don’t need a "Prefix". Typically you don’t want to see that trunk in all dial plans. The "Explicit Remote-Party-ID" can stay empty, because every trunk implicitly has its identity. It seems that RTC does not support any of the "Privacy Indication" methods, therefore you can leave it on "No Indication".
The failover settings are described in Outbound Settings, if you want to use the failover feature.
Because you are terminating traffic over the public Internet it does not make sense to turn "Is Secure" on.
The setting "Extension" should be set to the extension, auto attendant or other account that should receive the calls to this trunk. Because every trunk it is not necessary to use the DID routing mechanisms of the PBX. If you do use the DID numbers as alias to the primary extension number, you may also leave the extension field empty.
"Ringback" can be set to "Media". If you want to avoid the media traffic during a ringing phone call, you may also set it to "Message 180"; however in this case you might experience a delay in the voice path establishment after picking the phone up.
Dial Plan Setup
If you want that users use a different Caller-ID, you need to set up several dial plans that use the trunks in a different way. This way, you can influence what caller-ID is being presented to the outside world. For every Caller-ID, you need to set up a dial plan.
The dial plan is usually very simple. Just select the trunk that should be used for this dial plan and enter a star into the "Pattern" field. After pressing the "Save" button, you will see the following picture (the first line stays empty so that you can enter more patterns):
Extension Setup
If you are sending the calls directly to the extensions with the "Extension" setting in the trunk, you don’t have to add alias names for the DID numbers.
If you do want to provide alias names, we recommend to use the form "tel:0842095123 tel:46842095123". The first form can be used as Caller-ID for outgoing requests, the second can be used to match incoming calls (RTC is using this form to indicate the destination).
For every extension, you need to assign the dial plan that should be used for this extension. This setting influences the Caller-ID for outbound calls.
More Information
Please also see Troubleshooting SIP Trunk Problems for more information on how to set up a trunk.
Future Enhancements
Especially when a large number of DID numbers is being provided, it does make sense to use the RFC 3325 mechanism for indicating the Caller-ID instead of setting up a trunk and a dial plan for every user.
