innovaphone wiki - User contributions [en]

Freeedit:Wiki Edit Sandbox

2011-07-04T08:15:21Z

Solei:

Stefano Lugo '''Solei'''

Philipp Krötzsch '''Exabyters Multimedia'''

Sebastian Kobus '''Douglas Informatik & Service GmbH'''

Dennis Baum '''Douglas Informatik & Service GmbH'''

Christian Federspiel '''Gesundheitszentrum Unterengadin'''

Markus Leskow '''WWU Münster'''

Jens Petersen '''PETZ EDV-Beratung'''

Carlo Germani '''Blue Comm'''

Hanna Solbach '''ComNet GmbH'''

Thomas Richter '''Honeywell'''

Lars Enchelmaier '''TELCAT Multicom GmbH'''

Michael Mayer '''Datentechnik Austria'''

Raymond de Win '''Kreuze Telecom'''

Helenius '''Ascom Oy'''

Tomas Bornholm '''Ascom Sweden AB'''

Krister Lenberg '''Ascom Sweden AB'''

Martin Terhalle '''Selectric Nachrichten Systeme GmbH'''

Neuhold Markus '''Lyoness Dataservice GmbH'''

Koller Thomas '''Lippuner-EMT AG'''

Sandro Bernet '''Lippuner-EMT AG'''

Jack Valentijn '''QNS'''

Goetz M. Ritter '''GMR EDV-Beratung'''

Holger Görsch '''alcera '''

Andreas Lugner '''DB Netz AG '''

Ingbert Dierker '''Telcat Multicom GmbH'''

Marc Bau '''Voxtron'''

Jeroen Desloover '''Pilisoft'''

Burbuqe Kadriu '''EFG Financial Products AG'''

Mike Haupt '''Klinikum am Weissenhof - EDV'''

Andreas Winterott ''' Klinikum am Weissenhof'''

Michael Scheer '''Innovaphone AG'''

Patrick Montaine '''Ball Packaging Europe'''

Christoph Anhorn- '''swisspro AG'''

Matthias Lorentz '''DOKOM21 GmbH'''

Torsten Schawaller '''DOKOM21 GmbH'''

Ralf Kramer '''THALES Defence & Security Systems GmbH'''

Frank Weber '''Raber+Märcker GmbH'''

Heinz Stelling '''ST-oneline GmbH'''

= Wiki Syntax ([[Help:Formatting|more about formatting]], [[Help:Contents|generic help]]): =

Italic ''word'': <code>''word''</code> 
Bold '''word''': <code>'''word'''</code> 
:Indented line: <code>:line</code> 

# numbered list item: <code># list item</code>
## numbered list sub item: <code>## list item</code>

* dotted list item: <code>* list item</code>
** dotted list sub item: <code>** list item</code>

hidden search tag:  <code></code>

tiziano pigozzi '''EDSLan'''.

= Play Arena =

Martin Alles '''SWT trilan GmbH''' 
Ralf Tossing '''SWT trilan GmbH''' 
Stefan V. Pettersen '''Network Scenario''' 
Timo Feiner, '''KTF Feuchter''' 
Mathias Kropf, '''Ascom Deutschland''' 
Dirk Pedina, '''Telekommunikation Mittleres Ruhrgebiet GmbH''' 
Andre Lippitz, '''Sec Com GmbH Recklinghausen''' 
Manfred Mauler, '''ACP IT Solutions GmbH, Innsbruck''' 
Christoph Nyffenegger, '''Ascom Schweiz AG''' 
John Larsen '''Ascom Denmark A/S'''
Johann Kiss, '''Triple AcceSSS IT GmbH, Austria''' 
Marco Koch, '''Wrocklage Intermedia GmbH Germany''' 
Frank Schneebeck, '''ETe Datentechnik GmbH Germany''' 
Christoph Hanken, Paragon Data GmbH
Jonas Teckentrup, Paragon Data GmbH
Porretta Mauro, '''SARTE S.p.A. Italy''' 
Kevin Edmonds, '''Consult Partner GmbH''' 
Karsten Otto, '''westko network service GmbH''' 
Arne Stark, '''westko network service GmbH''' 
Henk Schuurman, '''Soft Solutions''' 
Marko Röhncke, '''Kevag-Telekom GmbH''' 
Kristijan Fabina, '''Datentechnik d.o.o.''' 
Dirk Lange, '''Nachrichtentechnik Bielefeld GmbH''' 
Ludwig Kempter, '''LEWTelNet GmbH''' 
Sakari Aaltonen, '''DigiCenter''' 
Jukka Somiska, '''Daimler Finland''' 
Gisbert Cremerius, '''Hack-Attack''' 
Massimiliano Tamaro '''Test s.p.a Italy''' 
Marco Boschi '''Eksaip Vicenza''' 
Stig Aune, '''Stig Aune Consulting''' 
Sandro Haas, '''KufGem EDV GmbH''' 
Daniel Haidacher, '''KufGem EDV GmbH''' 
Marc Steiner, '''Inikon AG''' 
Johan de Jong, '''trizwo GmbH''' 
René Scholz, '''Ascom''' 
Rocco Schmidt, '''ATS Ascom''' 
Marcel Britten, '''Connect GmbH''' 
Hans-Joachim Haun, '''VB OLD''' 
Marco Falger, '''Koch Media GmbH''' 
Swen Angelstein,'''ST.AG''' 
Arne Schmidt, '''TELCAT Multicom GmbH''' 
Liang Zhang, '''Koch Media GmbH''' 
Dirk-Jan van Dalen, '''Telematch BV''' 
Edwin Lansbergen, '''Telematch BV''' 
Benjamin Köhler, '''iits GmbH & Co. KG''' 
Christian Bengtsson, '''COBS AB. Sweden''' 
Sebastian Lutz, '''Oberberg-Online Informationssysteme GmbH''' 
Paul Schrok, '''Ascom Suisse SA''' 
Andreas Moser, '''EFG Financial Products AG''' 
Paul Schrok, '''Ascom Suisse SA''' 
Dennis Moller '''Ascom Denmark''' 
Andre Pooschke '''Fundamental Consulting GmbH & Co. KG''' 
Roman Pietrowski '''Bohnen Computer-Technik GmbH''' 
Oliver Dawid '''ComNet GmbH''' 
Richard Olsson '''Avitel''' 
Roman Festl '''Confidencia Consulting GmbH''' 
Udo Jungmittag, '''Ascom Deutschland GmbH''' 
Peter Fürst, '''swisspro AG''' 
Peter Ruf, '''swisspro AG'''
Carsten Reichelt '''HL komm Telecommunications GmbH''' 
René George, '''Multidata Sàrl''' 
Livane Hellmann, '''Ascom France''' 
Jan Korpegård, '''Ascom Sweden''' 
Knut-Vidar Bogstad, '''Ascom Norway''' 
Olivier Jau, '''Comint''' 
Kristian Tefre, '''Pettersson & Gjellesvik''' 
Kim Hovestad, '''A3BC''' 
Carsten Jenner '''Syncope GmbH''' 
Thomas Liebermann, '''DATARUN GmbH''' 
Tobias von Hebel '''SELECTRIC Nachrichten-Systeme GmbH''' 
Magnus Johansson '''COBS AB''' 
Sune Pedersen '''COBS AB''' 
Andrzej Markiewicz '''AKAM''' 
Frederik Glas '''YouP telecom BV''' 
Ivan Buljan '''NetVision d.o.o.'''

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:14:20Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to edit the following line at the end of the email.xml file:
<pre>
<exec url="mailto:$to?from=$to&subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
</pre>
to
<pre>
<exec url="mailto:$to?from=$from&amp';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
</pre>
otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:13:21Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to edit the following line at the end of the email.xml file:
<pre>
<exec url="mailto:$to?'from=$'''to'''&amp';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
</pre>
to
<pre>
<exec url="mailto:$to?'from=$'''from'''&amp';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
</pre>
otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:11:15Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to edit the following line at the end of the email.xml file:
<pre>
<exec url="mailto:$to?'''from=$to&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
</pre>
to
<pre>
<exec url="mailto:$to?'''from=$from&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
</pre>
otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:10:06Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to edit the following line at the end of the email.xml file:

<exec url="mailto:$to?'''from=$to&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>

to

<exec url="mailto:$to?'''from=$from&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>

otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:09:46Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to edit the following line at the end of the email.xml file:
<exec url="mailto:$to?'''from=$to&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>

to

<exec url="mailto:$to?'''from=$from&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>

otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:09:27Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to edit the following line at the end of the email.xml file:
<exec url="mailto:$to?'''from=$to&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
to
<exec url="mailto:$to?'''from=$from&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:08:27Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to change:
<exec url="mailto:$to?'''from=$to&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>

to

<exec url="mailto:$to?'''from=$from&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]

Howto:Send Email MWI Notification From The innovaphone Voicemail

2009-06-12T15:07:38Z

Solei:

==Applies To==
This information applies to

'''Note: The required Voicemail is not suitable for V6 SR1 environments'''.

* innovaphone PBX, V6 SR2
* innovaphone Voicemail, Build 07-60049

==More Information==
Email notifications about newly received voicemails can be sent towards the owner of a voicebox.
The mechanism is not reliable, because there is no spooling implemented. Currently, there will be one transmission attempt per email.

The destination email address can be taken from a file, that is to be located within the ''../personal'' directory of a voicebox. Alternatively may the email address be configured into a user's URL parameter within the corresping PBX object.

Such an email consists of a subject "You have received a new voicemail from: xxx", where ''xxx'' stands for the number of the calling party. There is additional [[#Send Voicemail As Email Attachment|functionality]] available to attach a voicemail as a wave file (a-law, u-law encoded) to an email.

The email will be sent by means of the Simple Mail Transfer Protocol (SMTP).

As SMTP Authentication mechanisms are supported (as of the writing of this arcticle): PLAIN, LOGIN and CRAM-MD5

===Installation===
Install the above mentioned voicemail build as usual.
* Just take note of the newly distributed file ''email.xml''.
* Ensure that the IP configuration (Default Gateway, DNS server) is appropriate.

===Provisioning Of Destination Email Addresses===
Email addresses must be configured manually. The script file email.xml firstly looks into a user's URL parameter and then into the user's personal file mail.txt, in order to find an email destination. Since the URL parameter may be used in other contexts, the script ensures that a non-empty URL parameter contains the '@' character as an indication that it deals with an email address.

====By URL Parameter====
The email address can be taken from a user's URL parameter.

Provisioning of a user's email address by URL parameter
* Proceed to ''Administration/PBX/Objects''.
* Open the desired Object GUI by clicking on it.
* Enter the email address into the ''URL'' edit field. The email address may be entered raw as e.g. ''pbxuser@mycompany.com'' or as mailto-URL alike e.g. mailto:pbxuser@mycompany.com.
Repeat these steps for each voicebox.

====By File====
The email address can be taken from the mass storage.
The destination email address can be written into a file.

Provisioning of a user's email address by file
* Within a text editor open up a new file.
* Enter the user's email address, e.g.: ''pbxuser@mycompany.com''
* Save the file as ''...yyy/personal/mail.txt'', where ''yyy'' stands for the directory name of the user's voicebox.
Repeat these steps for each voicebox.

===Configure the SMTP Agent===
By default the email will be sent with the sender- and destination- email address being identical. In addition will the email be sent alike a Mail Transfer Agent (MTA) does.

You can configure the content of the above mentioned file email.xml, in order to provide a different sender email address.

You can also control that emails are to be sent alike a Mail User Agent (MUA) does, or in other words: alike a regular email SMTP client does.

Open up the file email.xml within a text editor.

* In order to modify the sender email address, modify the line
<pre>
<assign out="$from" value="$to"/>
</pre>
into e.g.
<pre>
<assign out="$from" value="voicemail@mycompany.com"/>
</pre>

PLEASE NOTE: if your smtp server requires authorization, you will also need to change:
<exec url="mailto:$to?'''from=$to&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
to
<exec url="mailto:$to?'''from=$from&amp''';subject=$subject&subject=$cgpn&srv=$server&usr=$user&pwd=$password&file=$file"/>
otherwise sender address and authorization credentials won't match and you will get an "authorization failed" error

MTA-to-MTA communication may fail, depending on policies implemented within the receiving MTA. Therefore, it is desirable to turn our sending MTA into a simple MUA. That is, emails are to be sent via an SMTP provider server. Such a server is often termed as an ''Outgoing SMTP Server''.

Open up the file email.xml within a text editor.

To configure an outgoing SMTP server, modify the lines
<pre>
<assign out="$server" value=""/>
<assign out="$user" value=""/>
<assign out="$password" value=""/>
</pre>
into e.g.
<pre>
<assign out="$server" value="smtpserver.myprovider.com"/>
<assign out="$user" value="myuser"/>
<assign out="$password" value="mypassword"/>
</pre>

==== MS Exchange 2003====
An in-house test yielded the following approach, allowing to talk to the Exchange 2003 MTA-wise.
The file email.xml was left as-is, except the following line has been set to the dotted decimal IP address of the exchange machine.
<pre>
<assign out="$server" value="172.16.0.4"/>
</pre>
This allowed an intranet PBX to send emails to Exchange users, where the source- destination email address were identical.

===Send Voicemail As Email Attachment===
Emails won't carry a voicemail attachment by default. The file email.xml can be edited, in order to send voicemails as wave files together with the notification email.

Open up the file email.xml within a text editor, modify the line

<assign out="$file" value=""/>

into

<assign out="$file" value="$vm"/>

The wave files will inform about themselves as to contain a-law-, respectively u-law content.
From on Windows XP SP2 the Mediaplayer will contain the required codecs.

===Testing===
* Call a user with a CFU into his/her voicebox.
* Leave a voicemail, tear down (on-hook) the call.
* The owner of the voicebox should now have received an email.

===Troubleshooting===
Before contacting the support, you are asked to create a trace file covering the transmission attempt for an email.

The following lines in the configuration must be changed manually, from:
<pre>
config change DNS0
config change SMTP0
</pre>
into
<pre>
config change DNS0 /trace
config change SMTP0 /trace
</pre>

Activate the trace checkmark at the affected voicemail object. In addition should the voicemail object's trace flags be set to the value ''59'' alike: ''http://192.168.0.1/drive/CF0/vm.xml?$_trace=59''.



[[Category:Howto|{{PAGENAME}}]]