Page 181 / 286 Scroll up to view Page 176 - 180
Advanced Topics in SPA9000 Administration
Advanced Topics for SPA400 Voice Mail Service
SPA9000 Voice System Administration Guide
179
A
How Voicemail Works
When a user checks voicemail from a client station, the SPA9000 sends an INVITE
on its behalf to the configured <Mailbox Manage URL>. For example:
INVITE sip:mailbox-manage-url SIP/2.0
Via: SIP/2.0/UDP 192.168.2.205:5060;branch=z9hG4bK-
171eb6b5
From:
<sip:[email protected]>;tag=300704dd2590d20bo2;ref=5
031;mbid=53371
To: <sip:mailbox-manage-url>
CSeq: 101 INVITE
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
Here the client station is at extension 5031 and the mailbox ID is 53371. The
voicemail server should then prompt the caller to enter a PIN and access the
voicemail features for the given mailbox.
A user should also be able to call an external number explicitly from anywhere to
retrieve voice mail messages. When the voicemail server receives such a call, it
should prompt the caller to enter the mailbox ID and then the PIN number. If the
user-ID of the voicemail account cannot be uniquely identified from the mailbox ID
or from the called number, the server must first prompt the user to enter the user-
ID before proceeding.
NOTE
If an EXT-To-DID mapping exists for the calling extension on the line interface, the
user-ID and display name fields of the FROM header are replaced by the mapped
DID number and the display name assigned to the phone, respectively. In this case,
a DIVERSION header similar to the REFERRED-BY header is also included.
Downloaded from
www.Manualslib.com
manuals search engine
Page 182 / 286
Advanced Topics in SPA9000 Administration
Advanced Topics for SPA400 Voice Mail Service
SPA9000 Voice System Administration Guide
180
A
Checking Voicemail from an External Number
The Internet voicemail service provider (IVMSP) may have an external number for
their subscribers to call to check/manage their mailboxes. If this is not available,
you may do one of the following:
Assign a DID number (from the ITSP).
Create a virtual extension for this purpose.
For method (a), specify a rule in the <Contact List> for the dedicated DID number.
For the DID number 18005551000, this would look like the following example:
...|...|18005551000:vmm3|...
The syntax vmm<n> tells the SPA9000 to forward calls dialed to 18005551000 to
the voicemail management URL on Line <n>. Because no particular mailbox is
specified in this example, the caller is prompted to enter the voicemail number
after the voicemail server answers. You may also specify a particular mailbox ID
with this syntax (for example,
vm31234
).
Method (b) is used in conjunction with the Auto-Attendant. For example, you can
define a single-digit extension 7 to map to the voicemail management URL on Line
4, by adding a rule to <AA Dial Plan 1> or <AA Dial Plan 2> depending on which
one you are using. The rule would look like the following:
<7:vmm4>
Again, you may also specify a particular mailbox in this syntax. For information
about configuring the Auto-Attendant, refer to
Chapter 7, “Configuring the Auto
Attendant.”
Depositing Voicemail
An external caller can be triggered to deposit voicemail into a mailbox by sending
it a REFER request during a call with <Mailbox Deposit URL> indicated in the
REFER-TO header and the mailbox ID in the REFERRED-BY header. The caller
device then sends INVITE to the <Mailbox Deposit URL> as shown in the example
below:
INVITE sip:mailbox-deposit-url SIP/2.0
Via: SIP/2.0/UDP 24.35.36.111;branch=z9hG4bK-29752ae9
From: “External Caller” <sip:[email protected]>;tag=b99e21414928473o2
To: <sip:mailbox-deposit-url>
CSeq: 101 INVITE
Contact: <sip:[email protected]>
Referred-By: <sip:[email protected]>;ref=5041;mbid=7675
Downloaded from
www.Manualslib.com
manuals search engine
Page 183 / 286
Advanced Topics in SPA9000 Administration
Advanced Topics for SPA400 Voice Mail Service
SPA9000 Voice System Administration Guide
181
A
In the last example, the caller is directed to deposit voicemail in the mailbox ID
7675 on the voicemail account 37683101. It further indicates that the directing
station is at the internal extension 5041. Note that it is assumed that the caller
device (or the ITSP) is faithfully relayed over the REFERRED-BY header.
NOTE
The mailbox ID must be set to the extension number.
The INVITE sent for an internal caller to deposit voicemail is similar, except that the
FROM header also includes a reference parameter, as shown in the following
example:
INVITE sip:mailbox-deposit-url SIP/2.0
Via: SIP/2.0/UDP 172.12.244.56;branch=z9hG4bK-29752ae9
From: Line 1 <sip:[email protected]>;tag=b99e21414928473o2;ref=5031
To: <sip:mailbox-deposit-url>
CSeq: 101 INVITE
Max-Forwards: 70
Contact: <sip:[email protected]>
Referred-By: <sip:[email protected]>;mbid=7675
In the above example, the station wanting to deposit voicemail is at extension
5031; the mailbox ID is 7675 on the account 37683101 (for the station at extension
5041). Note that the referrer is the same as the caller in the last INVITE. In other
words, this INVITE is self-triggered by the SPA9000.
If an EXT-To-DID mapping exists for the calling extension on the line interface, the
user-ID and display name fields of the FROM header is replaced by, respectively,
the mapped DID number and the display name assigned to the phone.
Furthermore, if an EXT-To-DID mapping exists for the called phone, the user-ID
field of the REFERRED-BY header is also replaced by the mapped DID number for
the called extension.
NOTE
For information about how to add an EXT-to-DID mapping, see the <Contact List>
parameter in
Appendix B, “SPA9000 Field Reference.”
Downloaded from
www.Manualslib.com
manuals search engine
Page 184 / 286
Advanced Topics in SPA9000 Administration
Advanced Topics for SPA400 Voice Mail Service
SPA9000 Voice System Administration Guide
182
A
Subscribing to Voicemail Notification
The SPA9000 sends a one-time SUBSCRIBE for the message-summary event
package for each line with a valid <Mailbox Subscribe URL>. The SUBSCRIBE
implies subscription for the status of all the mailboxes associated with the
voicemail account used-ID; it does not include any mailbox ID in the request.
Following is an example:
SUBSCRIBE sip:mailbox-subscribe-url SIP/2.0
Via: SIP/2.0/UDP 172.16.22.23:5062;branch=z9hG4bK-44f9d0f0
From: Line 3 <sip:[email protected]>;tag=ac6013983cce7526
To: <sip:mailbox-subscribe-url>
CSeq: 63017
SUBSCRIBE Max-Forwards: 70
Contact: <sip:[email protected]:5062>
Expires: 30
Event: message-summary
User-Agent: Sipura/SPA9000-3.2.2
Content-Length: 0
The voicemail server is expected to send a NOTIFY immediately upon receiving
this SUBSCRIBE message for each mailbox on this account. The Request-URI of
the NOTIFY should reference the CONTACT header of the corresponding
SUBSCRIBE, but the user-ID in the To header should be the mailbox ID. The
following example shows a NOTIFY for the mailbox ID 5031 on the account
14089991003:
NOTIFY sip:[email protected]:5062 SIP/2.0
Via: SIP/2.0/UDP 178.178.221.230;branch=z9hG4bK-44f9d0f0
From: <sip:[email protected]>;tag=ab789
To: <sip:[email protected]:5062>;tag=ac6013983cce7526
CSeq: 537
NOTIFY Expires: 30
Event: message-summary User-Agent: ITSP/Voicemail-Server
Content-Length: 0
Messages-Waiting: yes
Voice-Message: 2/8 (0/2)
NOTE
Note that SPA9000 does not require the NOTIFY to be sent within the same
subscription dialog. That is, it accepts the NOTIFY even without a TO-tag or a
matching Call-ID as the original SUBSCRIBE.
Downloaded from
www.Manualslib.com
manuals search engine
Page 185 / 286
Advanced Topics in SPA9000 Administration
Remote Provisioning Features
SPA9000 Voice System Administration Guide
183
A
Remote Provisioning Features
The
SPA9000
provides for secure provisioning and remote upgrade. Provisioning is
achieved through configuration profiles that are transferred to the device via TFTP,
HTTP, or HTTPS.
Using Configuration Profiles
The
SPA9000
accepts configuration profiles in XML format, or alternatively in a
proprietary binary format, which is generated by a profile compiler tool available
from Linksys. The
SPA9000
supports up to 256-bit symmetric key encryption of
profiles. For the initial transfer of the profile encryption key (initial provisioning
stage), the
SPA9000
can receive a profile from an encrypted channel (HTTPS with
client authentication), or it can resync to a binary profile generated by the Linksys-
supplied profile compiler. In the latter case, the profile compiler can encrypt the
profile specifically for the target
SPA9000
, without requiring an explicit key
exchange.
The XML file consists of a series of elements (one per configuration parameter),
encapsulated within the element tags <flat-profile> … </flat-profile>. The
encapsulated elements specify values for individual parameters.
Refer to the following example of a valid XML profile:
<flat-profile>
<Admin_Passwd>some secret</Admin_Passwd>
<Upgrade_Enable>Yes</Upgrade_Enable>
</flat-profile>
Binary format profiles contain
SPA9000
parameter values and user access
permissions for the parameters. By convention, the profile uses the extension .cfg
(for example, spa2000.cfg). The Linksys Profile Compiler (SPC) tool compiles a
plain-text file containing parameter-value pairs into a properly formatted and
encrypted .cfg file. The SPC tool is available from Linksys for the Win32
environment and Linux-i386-elf environment. Requests for SPC tools compiled on
other platforms are evaluated on a case-by-case basis. Please contact your
Linksys sales representative for further information about obtaining the SPC tool.
The syntax of the plain-text file accepted by the profile compiler is a series of
parameter-value pairs, with the value in double quotes. Each parameter-value pair
is followed by a semicolon. Here is an example of a valid text source profile for
input to the SPC tool:
Admin_Passwd
“some secret”;
Upgrade_Enable “Yes”;
Downloaded from
www.Manualslib.com
manuals search engine

Rate

3.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top