Configuring VSTG and VCG Properties / Configuring Caller Information |
In certain Vocera call scenarios, caller information might be confusing or cause unintended results. Consequently, you should weigh the frequency of these scenarios before you decide to enable dial signal caller information in the Vocera SIP Telephony Gateway.
Scenario 1: Using a SIP-enabled desk phone with the extension 5818, Doctor Jankis calls the Vocera Direct Access hunt group number, and then uses the Genie to call a Vocera user. When the user answers the call on a badge, the badge displays 5818 on screen, as intended.
Scenario 2: Using a SIP-enabled desk phone with the extension 5818, Doctor Jankis calls the Vocera Direct Access hunt group number, and then uses the Genie to call a Vocera user. Since the user is not logged in, the call is forwarded to the user's home phone. However, the home phone is set to not accept calls from phones whose caller ID is blocked or does not conform to standard U.S. 10-digit phone numbers. In this case, the call may not go through.
Scenario 3: Using his cell phone, which blocks caller ID, Doctor Jankis calls the Vocera Direct Access hunt group number, and then uses the Genie to call a Vocera user. Since the user is not logged in, the call is forwarded to the user's home phone. However, the home phone is set to not accept calls from phones that block caller ID. In this case, the call may not go through.
Scenario 4: Using his cell phone, Doctor Jankis calls the Vocera Direct Access hunt group number, and then uses the Genie to call a Vocera user. Since the user is not logged in, the call is forwarded to the user's cell phone. Doctor Jankis's caller ID (his cell phone number) is displayed on the user's cell phone. This may not be what Doctor Jankis intended.
If the results of any of these call scenarios are unintended and you would rather display the DID number of the Vocera trunk as the caller ID for all calls, then set the VTGUseDialCallerInfoInINVITE property to FALSE (the default setting).