This page contains instructions on how to add a Calling Card extension to the system.
This type of extension allows setting up a calling card service on the system. This way customers can use a calling card to pay for telephone services, even if their phone is not connected to the VoipNow system.
To set up a Calling Card extension, first you need to define its general settings. Then you may customize it using specific options. You may do this at any time later on by clicking the Calling Card setup icon available in the extension's management page.
Set up the way you need the Calling Card extension to behave.
- Do not allow the user to call if credit is below <x> <currency>: Fill in the minimum credit a user should have when placing a call through the Calling Card extension; The currency that applies is usually the system's default currency.
- Play when the call cannot be initiated due to lack of credit: Select the sound that should be played to the user running out of credit, upon automatically interrupting the conversation;
- Play before disconnecting the call during a conversation: Select the sound that should be played to the user that made the call, upon automatically interrupting the conversation.
- User can interrogate the account credit: Applies if you want to give users the possibility to find out their credit value, before starting the conversation; As soon as the user is authenticated with one of the card codes, they are able to either interrogate their credit or make a phone call.
- Service client must dial remote party number in <x> seconds: Specify the time interval (in seconds) within which the user can dial the remote party number; At the end of this time interval, VoipNow will consider the request as being completed.
These are the CallerID related options.
|CallerID name in public calls|
The options described below allow you to customize the CallerID name that will be displayed on the callee's screen when the extension is calling public destinations.
|CallerID number in public calls||The options described below allow you to customize the CallerID number that will be displayed on the callee's screen when the extension is calling public destinations.|
|Currently using CallerID numbers||Allows you to choose one or several CallerID numbers that will be sent when an outgoing call is initiated.|
The numbers available are the ones defined for the channel(s) (resource) used for routing the calls to public destinations.
Please note that a CallerID can be set as default even if it has not been assigned to the extension's DID pool.
Click here to expand the fields required by the Public Phone Numbers form.
To associate a CallerID with the extension, you need to select the corresponding checkbox and click the Assign CallerIDs link. To disassociate a CallerID, you need to select the corresponding checkbox and click the Remove selected link.
Click here to expand what happens if you associate several CallerIDs to the extension.
1. If you have selected more than one CallerIDs for a resource (channel), then the system will send a random one to the public destination.
Let us assume that the outgoing calls are routed through a resource (channel), Resource #1, for which three public phone numbers have been defined and assigned to the client that owns the extension: 1123, 345876 and 2854478. If you associate all three of them with the extension, when initiating an outgoing call, the callee's phone terminal will display, if it supports the CallerID function, one of the three numbers.
2. If you have selected CallerIDs for more than one resource (channel), then the system will send the CallerID of the resource that routes the call.
Let us assume that the outgoing calls are routed through Resource #1, for which one public number has been defined and assigned to the client who owns the extension: 2255. You associate this number with the extension and another one, 6987560, defined for Resource #2. If it supports the CallerID function, when initiating an outgoing call, the callee's phone terminal will display 2255.
3. If calls are routed through a resource that does not have a public phone number assigned and you have a CallerID that belongs to another resource set as default, then the system will send the default CallerID.
Let us assume that the outgoing calls are routed through a resource (channel), Resource #1, for which no public phone numbers have been defined. Your default CallerID is set to 3689, which belongs to another resource (channel), Resource #2. If it supports the CallerID function, when initiating an outgoing call, the callee's phone terminal will display 3689.
Do not send CallerID on public calls
Applies if you do not want your CallerID to be sent to public destinations. If the callee's phone terminal supports the CallerID function, it will display the Anonymous string.
Send public CallerID on internal calls
Applies if you want the public CallerID (when available) to be used for local and extended local calls as well. It allows the association between the CallerID of the Phone terminal user and an existing card code defined for the same CallerID.
Preserve original CallerID on transferred calls
|Applies if you want VoipNow to keep the original CallerID when the call is forwarded between destinations.|
Send SIP P-Asserted-Identity and P-Preferred-Identity headers
Allows the headers to be added to all outgoing INVITE requests sent from this extension.
The SIP P-Asserted-Identity header contains the caller ID number of the extension, e.g. P-Asserted-Identity:sip:email@example.com.
The P-Preferred-Identity header is sometimes used to indicate an additional identity of preference when there is a choice.
These headers are preserved only on outgoing external calls, e.g. P-Preferred-Identity: "John White" <sip:firstname.lastname@example.org>.
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 4.0 International.