Voicemail

This section describes the voicemail recording flow in PortaSIP and shows how the system:

• prompts the caller
• records the voicemail message and saves it as a file
• stores the file in the user’s voicemail inbox

• When a recipient doesn’t answer within the defined period, e.g., 30 seconds, PortaSIP redirects the incoming call to the voicemail application.

• The voicemail application plays a prompt instructing the caller to leave a message.
• After the prompt, the tone is played, and the recording begins.

• PortaSIP records the audio stream from the caller and saves it as an audio file in AU or G.729 format.
• PortaSIP then sends a request containing the recorded audio file to the web server for further processing.

• The web server converts the file in the AU or G.729 format into a standard audio format (e.g., WAV or MP3) to enable easy playback and storage.
• The audio file is saved in the voicemail storage. The user can then listen to the voicemail later in their mailbox, in the self-care portal or mobile app.

• If the user has configured an external email address and selected what content should be sent to it (e.g., a voicemail recording in audio format, voicemail text transcription, or a notification only), they will receive an email containing the corresponding information based on the selected option.

In the following section, you can see how a user can configure receiving voicemail notifications on their email.

By default, when a new voicemail record is created for a user, the corresponding notification is sent to the email address defined for the user’s account in the Account > Personal info > General info > Email field in PortaBilling, e.g., “user@company.domain.com”.

Additionally, a user can forward the voicemail notifications to their other email address, e.g., a private gmail address. For this, a user needs to:

1. Log in to the Account self-care web interface.
2. Go to Cloud PBX > Voicemail > External email.
3. Specify the email address in the Email field.
4. Select one of the following options in the Action field:
   • None – no voicemail recordings will be sent to the external email.
   • Forward – a voicemail recording will be sent in the specified audio format (see the Voice message audio format field) to the external email. The recordings will be deleted from the voicemail box. This option is useful when the mailbox limit is not sufficient for the user. The user will see their account ID in the “To’’ address, e.g., 1665126356@sip.portaone.com.
   • Forward as Attachment – this works like the “Forward” option, but a voicemail recording will be sent as an attachment in the .eml format. The user will see their email in the “To’’ address, e.g., user@company.domain.com.
   • Copy – a voicemail recording will be sent in the specified audio format (see the Voice message audio format field) to the external email and its copy remains in the voicemail box. The user will see their email in the “To’’ address, e.g., user@company.domain.com.
   • Notify – the user will only receive a notification about the new voicemail recording in the external mail (the recording remains in the voicemail box). The “To’’ address will show the user’s email, e.g., user@company.domain.com.
5. Choose what should be sent to the specified email in the Action field, e.g., a full copy of the message (the notification message with the voice recording).
6. Choose the format of the voice message file in the Voice message audio format field, e.g., mp3.

By default, the sender’s email address (the “From” field in the email) is shown to a user as their account ID followed by the IP address/domain of the SIP node. For example, if a user has an account with ID “1665126356”, they will see that the email is sent from, 1665126356@sip.portaone.com.

You can configure the email address that the users see when they receive an email. For this go to the Configuration server web interface and set an email domain in the MediaServer.email_domain option, e.g., serviceprovider.com.

When a user receives an email with a voicemail notification, the “From” field will contain the email address that includes the account ID followed by the domain name specified on the Configuration server. So, in this case, if a user has an account with ID “1665126356”, they will see that the email is sent from the “1665126356@serviceprovider.com” email address.

The system defines what email address to use as follows:

• By default, the email address set in the Reseller record > Company info > General info > Sender email for customer notifications field is used as a “From” header in the emails. The reseller can change this email address from their self-care web interface.
• If no email is specified in the Sender email for customer notifications field, then the email address set in the Reseller record > Company info > General info > Email field is used. The reseller can change this email from the self-care web interface too.

If both the Sender email for customer notifications and Email fields are not set for a reseller, then the "From" field in the email will consist of a user's account ID followed by the generic domain set on the Configuration server. If the domain is not set there, the email will consist of a user's account ID followed by the IP address/domain of the SIP node. See the Sender’s email section for details.

When a PBX user receives a notification about a new voice message, they see the caller’s extension name and number. The user can immediately respond to the message without having to match the phone number with its owner. This vastly improves the user experience.

For PortaSIP to use the extension’s information in the notification, enable the mailbox_use_ext_id_as_sender option on the Configuration server web interface.

If the extension information is undefined, the notification contains the caller’s phone number.