innovaphone wiki - User contributions [en]

Howto:Update innovaphone.com Wildcard-Certificate in a Device Trustlist

2026-05-06T07:51:18Z

Melvin.reiniger: Typos

'''This article is obsolete for the push service, please see [[Howto13r2:12r2/13r1 legacy push server will be migrated to push.innovaphone.com]]'''

==Applies To==
This information applies to
* All innovaphone IP-Phones and -Gateways with 12r2, 13r3, 14r1, 14r2 firmware and > V15r1 firmware and no Devices certificate deployment configured.

==More Information==

===Problem Details===
On the end date of the current certificate <code>*.innovaphone.com</code> it will expire. '''We will renew this certificate every year on time.''' This certificate is used in the PBX trust list to establish an encrypted connection between your PBX and the innovaphone services.
To ensure that a service also works for your customers after the existing certificate end date, a new valid certificate must be added to the trust list of the respective PBX.
After the existing certificate end date, the old <code>*.innovaphone.com</code> certificate can be deleted.
This certificate is currently only relevant for gateways on which a service connection to innovaphone is established. During the transition period of the release of a new certificate and the end date of the old certificate, both <code>*.innovaphone.com</code> certificates are required.

Additionally, every time an innovaphone devices is restarted, the current <code>*.innovaphone.com</code> certificate generates a [[Reference9:Event/0x000c1001| x509: A certificate has expired or will expire soon]] event.

'''If you use the [[Reference14r2:Concept App Service Devices#Certificates configuration|Devices - certificate trustlist concept]] you are not affected, and the certificate will be installed automatically.'''

===Resolution===
Here are three ways to replace the certificate on all innovaphone devices.

1. In the version 12r2sr72, 13r3sr22, 14r1sr10 and 14r2sr5 the certificate will be added automatically during the update.
After the old certificate end date, it can be manually deleted. Also, current firmware includes a mechanism to prevent ''Certificate expiration events'' in case that a new certificate exists for the same CN.
Finally, devices with 12r2sr72, 13r3sr22, 14r1sr10 and 14r2sr5 firmware will have after a factory reset only the new *.innovaphone.com certificate.

2. The certificate can be added manually on the PBX. It can be downloaded [[:File:Star innovaphone cert 2025.zip|here]] and then be uploaded on the PBX under [[Reference15r1:General/Certificates#Trust list|General/Certificates/Trust list]].
After 27.12.2024, the old certificate can be manually deleted.

3. The new certificate can be added, and the old certificate can be deleted via commands (which can be sent using an update server or the [[Reference14r2:Concept App Service Devices#Expert configuration| Expert configuration]] in ''Devices''). This needs a reboot of the device.
Save the new certificate in the trust list:
!vars create X509/TRUSTED pba 3082063e30820526a00302010202107ac11bffa149788852b63d5a31ce0959300d06092a864886f70d01010b050030818f310b3009060355040613024742311b30190603550408131247726561746572204d616e636865737465723110300e0603550407130753616c666f726431183016060355040a130f5365637469676f204c696d69746564313730350603550403132e5365637469676f2052534120446f6d61696e2056616c69646174696f6e2053656375726520536572766572204341301e170d3234313132393030303030305a170d3235313233303233353935395a301c311a301806035504030c112a2e696e6e6f766170686f6e652e636f6d30820122300d06092a864886f70d01010105000382010f003082010a0282010100b94fa779dc824ea7e561d83ed2f2b3fd293752832526af285af8e728668323b3d7444e724dbd4a2792998c0eabbac0ec1fcb1ebc7db5dcb174cd74a8aa9763e3eeb2541f2302bcad45b3f4d09a95876ef15e670db519f5bd0b5092389f995e8e0a9241ee462fd34d3af41df4693b571b1bf1dfb4a74ab5a70e68e87c2c12c0e3be5b408ec4d61099f79338dcfa73277d4a237065946795753edb89c9f234329a7b5a47ebc87e86f779281b9381072e1db4f57a3b9f8df67bf65e6090d2ea2ab93deb0b9013b0f762977726c6708b33137d599f82c15c2d72a76e568e22a3fb717c9ddbc9e33b12aacb9fcb543df52f3520f117d0647617801a24d651709645fd0203010001a382030630820302301f0603551d230418301680148d8c5ec454ad8ae177e99bf99b05e1b8018d61e1301d0603551d0e04160414172bc6fe5fa1ed78d9f49257924a714a950d4503300e0603551d0f0101ff0404030205a0300c0603551d130101ff04023000301d0603551d250416301406082b0601050507030106082b0601050507030230490603551d20044230403034060b2b06010401b231010202073025302306082b06010505070201161768747470733a2f2f7365637469676f2e636f6d2f4350533008060667810c01020130818406082b0601050507010104783076304f06082b060105050730028643687474703a2f2f6372742e7365637469676f2e636f6d2f5365637469676f525341446f6d61696e56616c69646174696f6e53656375726553657276657243412e637274302306082b060105050730018617687474703a2f2f6f6373702e7365637469676f2e636f6d302d0603551d110426302482112a2e696e6e6f766170686f6e652e636f6d820f696e6e6f766170686f6e652e636f6d30820180060a2b06010401d679020402048201700482016c016a007700dddcca3495d7e11605e79532fac79ff83d1c50dfdb003a1412760a2cacbbc82a00000193788b6e35000004030048304602210095e474cfc8cb1391e90503117fbb02b3f218adc046ad654a742c554cea1aabb50221009ec6324267f294e3fd82042edc4f75b3d5045186a2c8d7a132cfb930040e6813007700ccfb0f6a85710965fe959b53cee9b27c22e9855c0d978db6a97e54c0fe4c0db000000193788b6df6000004030048304602210096c02ff89884ff81f1d1e06965cc8639e5775eda2548cdf6f1492fe9388edf1a022100f67955e0066763ba7f23020130fe625f9c41cbe5f49626ca71076202ffdece3300760012f14e34bd53724c840619c38f3f7a13f8e7b56287889c6d300584ebe586263a00000193788b6dd50000040300473045022100abec85798805aafecc03b4b9b6e0dbb2beab28b9a5d36ed5021a4fb40e477ed40220131255263bdf66bc618f9f531dedb249c30c6b5f98be23ced37100c7166571c2300d06092a864886f70d01010b05000382010100592acc609c02195145ee6abf875f3ced94e039f83e2f88022013ea40c65ae4738d80a07e518a28f996726422fefa2f53d04aa3635fe98c4c882132f86d92924bace80c185f6fea710bbf48ce12da24440651e6b58cf4f2101634a4c6ca506ea0a75a00266eca09f275d3389ae673fb48e9b587477ba642f95000b4331dd682426be4ac59dfc8e859f8771d1bf98fe7a95dade3f53844c774376f4ca2067953202ac4e1089bd179f124f3eac09d020eadf36b1b018caece0f7159c279801358f9b9b6f15e0d92b4784f5f49ba343b36baa1faab04ab29d6377ba2f9b8760b4a8ae88009de395c580ad97518697cb3a950762fe218b6d965a46eb0c6733f2017f7

Remove old certificate (optional):
!mod cmd X509 form /item-trusted-3ccaa98ee59e6fd2ae91299fab78970d4f9f39a37eed987b32982e6a8a201afb70f7068f on /trusted-delete Remove

===Additional Recommendation===

If you are still connected to the ''old'' push-service (services.innovaphone.com), we recommend switching to the new push-service described in the [[Howto13r2:12r2/13r1 legacy push server will be migrated to push.innovaphone.com| Push Migration (Shutdown planned for 31.12.2024)]]. We currently evaluate to change the certificate used on the push-service to an innovaphone CA-signed one, with a longer duration time.

== Related Articles ==
* [[Howto13r2:12r2/13r1_legacy_push_server_will_be_migrated_to_push.innovaphone.com]]
* [[Reference15r1:Concept App Service Devices#Certificates configuration]]

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

Howto:Integrate External Apps in innovaphone UC clients

2023-04-17T12:53:18Z

Melvin.reiniger:

[[Category:Howto]]
==Applies to==
Following native innovaphone UC clients:
* myPBX for Windows since firmware version 10
* myApps for Windows since firmware version 13r1
* myApps for MacOS since firmware version 13r2

==More Information==
External applications can be integrated in innovaphone UC clients myPBX and myApps.

Those can be locally installed PC-applications as well as web applications.

Upon incoming and outgoing call, such applications may be opened and call-parameters can be handed over optionally.

==Configuration==
===myPBX===
* Right Click on myPBX – Configuration – External Application
* Enter the name of the external app (which will be seen as tooltip of the external app button).
* Paste the path of the external app into the field “Path”. It can be both the URL of a web application (http://crm.example.com/customer-by-number/$n) or the path of a desktop application installed on the local computer (C:\Program Files (x86)\Google\Chrome\Application\chrome.exe)
* Optionally specify command line parameters for Desktop Apps into the field “Parameters”.
* Save the changes.

[[Image:Mypbx_Konfigurationen1.jpg]]

The Path and the Parameters may contain placeholders that are replaced by phone call information.

$n - phone number of the caller
$u - uri of the caller
$d - display name of the caller
$c - conference ID (a global ID for the call)

Now you will get the "start external application" button in every conversation or interaction field.

[[Image:Eigener Screenshot_mit Buttonhinweis_EN.jpg]]

<hr>
===myApps===
* Settings via burger menu / Settings / More / External Applications
* Several may be configured in parallel
* Set name which is displayed in PhoneApp-button upon call
* Set URL or path to application
* Set parameter string
* Optionally choose if application shall be autostarted upon call
For help, press questionmark icon

[[Image:myApps_external_applications.png]]

==Examples==
{{3rd Party Input}}

===Outlook Journal===
Tested with: myPBX V11 / Outlook 2010

Path: ...\Microsoft Office\Office14\OUTLOOK.EXE
Parameters: /c ipm.activity /m bla?subject=Telefongespräch%20mit%20$n

===Firefox===
Tested with: myPBX V11 / Firefox V.38

Path: ...\Mozilla Firefox\firefox.exe
Parameters e.G.: http://xxxx/$n/xxxx

===Notepad===
Tested with: myPBX V11 / Windows 7

Path: ...\Windows\notepad.exe
Parameters e.G.: C:\$d.txt

=== Open the default email client during a call and use the callinfo in the email ===
Tested with: myPBX V12, V13 and myApps V13r1 / Windows 10 

Path: mailto:receivers@email.com?subject=Telephony notification from $u $d tel:$n&body=Hello, %0A%0APlease call back to $u $d tel:$n %0A%0AKind regards, %0AYour Name

=== Open WhatsApp during a call to send a message to your caller during or after the call using the available callinfo and a personal note ===
Tested with: myApps V13r2 / Windows 10 / WhatsApp Windows (web version not possible) 

Path: https://api.whatsapp.com/send?phone=$N&text=Hi+$d%21+Thank+you+for+your+call++++We+keep+in+touch&app_absent=0

=== Open a webbased CRM or Public website to search on a number ===
Tested with: myPBX V12, V13 and myApps V13r1 / Windows 10 

General example Path: https://www.unknownphone.com/search.php?num=$n
Deutschland Das Telefonbuch Path: https://www.dastelefonbuch.de/R%C3%BCckw%C3%A4rts-Suche/$n
Das Oertliche Path: https://www.dasoertliche.de/rueckwaertssuche/?ph=$n
Nederland Gebeld.NL (*) Path: C:\Program Files\Google\Chrome\Application\chrome.exe
parameters: "http://www.gebeld.nl/index.php?page=1&queryfield1=$n&searchfield1=fullnumber&action=Zoeken"
Schweiz Search.ch Path: https://tel.search.ch/?tel=$n
Östenreich Herold.at Path: https://www.herold.at/telefonbuch/telefon_$n
Danmark KRAK.dk Path: https://www.krak.dk/$n/firmaer

(*) URLs containing "&" have to be executes via chrome.exe and to be put in quotes to avoid interpretation by chromium.

=== Open the Outlook client during a call and use the callinfo in the Calendar appointment ===
Tested with: V13 and myApps V13r1 / Windows 10 

Path e.g. : C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE
Parameters e.G.: /c ipm.appointment /m "youremail@domain.com ?subject=call to tel:$I &body=Can we meet please call to tel:$I"

=== Open a customer chart in Microsoft Dynamics Navision (local installed client application) during a call or with the start of the call ===
Tested with: myApps V13r1sr21 / Windows 10 and Microsoft Dynamics NAV 2018 Version BE Dynamics NAV 11.0 11.0.28629.0 

Path e.g. : dynamicsnav://customername-nav:7146/customername_live/customername/runpage?page=21&$filter='Phone No.' IS '$I'

$I at the end of the line is the variable that represents the telephone number in international format E164 eg 3164133xxxx

=== Search on telephone number within CRM or other application on zoho.eu ===
Tested with: myApps V13r1sr26 / Windows 10 and already logged-in on the website zoho.eu

Path to search within all zoho applications e.g. : https://crm.zoho.eu/crm/org12345678901234/search?searchword=$I replace /org12345678901234/ with your own organisation-id
Path to search within your zoho CRM contacts only e.g. : https://search.zoho.eu/search?q=$I&s=crm

$I at the end of the line is the variable that represents the telephone number in international format E164 e.g. 31653394xxx

=== Search on telephone number within HALO or HALOPSA on halopsa.com ===
Tested with: myApps V13r3 / Windows 10 and already logged-in on the website halopsa.com
[[Image:halopsa_example.png|thumb|upright=1.0|right|HALOPSA LINK]]

Path to search within all HALO CRM applications, e.g. : https://karlsnl.halopsa.com/call?showmenu=false&callerid=@callerid replace @callerid with $I

$I at the end of the line is the variable that represents the telephone number in international format E164 e.g. 31653394xxx

Example where to find the right integration link in HALOPSA, look under Configuration, Call Management, General Settings. There are several options for the opened webpage that you can choose from.

==Related articles==
* [[Reference12r2:Concept_myPBX#Starting_an_external_application_for_a_call|call external application via myPBX]]
* [[Reference13r2:Concept_myApps_platform_services#Call_an_external_application_for_calls|call external application via myApps]]

Howto:Group Voicemail

2022-05-05T14:32:53Z

Melvin.reiniger:

==Applies To==
This information applies to
* IPXXX, V13r2
PBX-Build 135779 and later.
VM-Build 135xxx


==More Information==
A comma-separated list of MWI destinations/recipients can be configured by means of a variable ''$_m'' within the script URL's query string. This article outlines a configuration scheme for group voicemail functionality.

===Problem Details===
A group voicemail acts as single point of storage and multiple point of access for several PBX endpoints. MWI-updates are expected to be delivered to all group members.

===System Requirements===
A standard voicemail script vm.xml is expected to be installed underneath ''/drive/CF0/vm/vm.xml''.

'''A PBX-VoicemailUser13 license is required for each group voicemail.'''

===Installation===
Users redirect their calls to the voicemail object via call forwarding. The number of the VM object is appended as the destination number for the call forwarding and for the MWI button, e.g. if the VM object has the number 803, then the call forwarding and the MWI button use 803803 as the destination.
In the URL of the vm.xml script, use the $m variable to configure the recipients of the MWI notification.
The voicebox's directory on the mass-storage will be named like the ''Name'' of the Voicemail-Object.

To activate each group voicemail there may be an initial call needed from any user with "Send Number" of the group voicemail number, e.g. set "Send Number" at the user 101 to 803, call 803803 and enter the PIN.

===Configuration Example===
*Assume following objects exist in your PBX:
**'''User''' ''101(Number):endeavour(Name):Endeavour(LongName)''
**'''User''' ''102(Number):atlantis(Name):Atlantis(LongName)''
**'''Voicemail''' ''803(Number):vm-group(Name):Vm-group(LongName)''
***'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=101,102
</code>
***'''E-Mail''' if desired configure a destination email address serving as a group email address
****Note: The email is sent only once to the destination configured as PBX/Objects/"vm-group"/General/E-Mail. It is up to an admin of the receiving mail server for how to distribute the email towards all potential group members.
*Configure Function-Keys at phones Endeavour, Atlantis
**'''Type''' Message Waiting
**'''Message Center Account'''
***'''Number''' ''803803''
***'''Append Own Number''' inactive/not checked
***'''Name''' ''vm-group'' - needed if multiple MWI-keys (e.g. own Voicemail and Group Voicemail) are configured on the phone.
*Configure source email address and mail server
**Edit the settings underneath '''PBX/Config/Authentication/Email Verification''' accordingly. Those are the settings being considered by the sub-script email.xml.

=== Configuration App Platform===
If using app platform the configuration can done by PBX Manager. There is a new button "add Voicemail group app". This configures the new variable "$_m" and a second one for the app "$_group" which is the name of the VM Object.
It is only necessary for the voicemail app.

The voicemail app works with sip names<ref>sip name: the dialable name, within a user's PBX-UI the edit field '''name'''</ref><ref>A comma within a sip name must be URL-escaped within the comma-separated list ''$_m..'' E.g. ''Doe, John'' => ''Doe%2C John''</ref> so that it is mandatory to configure the Message Waiting Keys and the $_m with names instead of numbers.

'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=endeavour,atlantis&$_group=vm_group&$app=on
</code>

The group voicemail app can be activated for every user by checkmark the group voicemail object in the tab "PBX/User/Apps"

==Known Problems==

==Related==
<references/>

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

Howto:Group Voicemail

2022-05-05T14:31:59Z

Melvin.reiniger:

==Applies To==
This information applies to
* IPXXX, V13r2
PBX-Build 135779 and later.
VM-Build 135xxx


==More Information==
A comma-separated list of MWI destinations/recipients can be configured by means of a variable ''$_m'' within the script URL's query string. This article outlines a configuration scheme for group voicemail functionality.

===Problem Details===
A group voicemail acts as single point of storage and multiple point of access for several PBX endpoints. MWI-updates are expected to be delivered to all group members.

===System Requirements===
A standard voicemail script vm.xml is expected to be installed underneath ''/drive/CF0/vm/vm.xml''.

'''A PBX-VoicemailUser13 license is required for each group voicemail.'''

===Installation===
Users redirect their calls to the voicemail object via call forwarding. The number of the VM object is appended as the destination number for the call forwarding and for the MWI button, e.g. if the VM object has the number 803, then the call forwarding and the MWI button use 803803 as the destination.
In the URL of the vm.xml script, use the $m variable to configure the recipients of the MWI notification.
The voicebox's directory on the mass-storage will be named like the ''Name'' of the Voicemail-Object.

To activate each group voicemail there may be an innitial call needed from any user with "Send Number" of the group voicemail number, e.g. set "Send Number" at the user 101 to 803, call 803803 and enter the PIN.

===Configuration Example===
*Assume following objects exist in your PBX:
**'''User''' ''101(Number):endeavour(Name):Endeavour(LongName)''
**'''User''' ''102(Number):atlantis(Name):Atlantis(LongName)''
**'''Voicemail''' ''803(Number):vm-group(Name):Vm-group(LongName)''
***'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=101,102
</code>
***'''E-Mail''' if desired configure a destination email address serving as a group email address
****Note: The email is sent only once to the destination configured as PBX/Objects/"vm-group"/General/E-Mail. It is up to an admin of the receiving mail server for how to distribute the email towards all potential group members.
*Configure Function-Keys at phones Endeavour, Atlantis
**'''Type''' Message Waiting
**'''Message Center Account'''
***'''Number''' ''803803''
***'''Append Own Number''' inactive/not checked
***'''Name''' ''vm-group'' - needed if multiple MWI-keys (e.g. own Voicemail and Group Voicemail) are configured on the phone.
*Configure source email address and mail server
**Edit the settings underneath '''PBX/Config/Authentication/Email Verification''' accordingly. Those are the settings being considered by the sub-script email.xml.

=== Configuration App Platform===
If using app platform the configuration can done by PBX Manager. There is a new button "add Voicemail group app". This configures the new variable "$_m" and a second one for the app "$_group" which is the name of the VM Object.
It is only necessary for the voicemail app.

The voicemail app works with sip names<ref>sip name: the dialable name, within a user's PBX-UI the edit field '''name'''</ref><ref>A comma within a sip name must be URL-escaped within the comma-separated list ''$_m..'' E.g. ''Doe, John'' => ''Doe%2C John''</ref> so that it is mandatory to configure the Message Waiting Keys and the $_m with names instead of numbers.

'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=endeavour,atlantis&$_group=vm_group&$app=on
</code>

The group voicemail app can be activated for every user by checkmark the group voicemail object in the tab "PBX/User/Apps"

==Known Problems==

==Related==
<references/>

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

Howto:Group Voicemail

2022-05-05T14:31:38Z

Melvin.reiniger:

==Applies To==
This information applies to
* IPXXX, V13r2
PBX-Build 135779 and later.
VM-Build 135xxx


==More Information==
A comma-separated list of MWI destinations/recipients can be configured by means of a variable ''$_m'' within the script URL's query string. This article outlines a configuration scheme for group voicemail functionality.

===Problem Details===
A group voicemail acts as single point of storage and multiple point of access for several PBX endpoints. MWI-updates are expected to be delivered to all group members.

===System Requirements===
A standard voicemail script vm.xml is expected to be installed underneath ''/drive/CF0/vm/vm.xml''.

'''A PBX-VoicemailUser13 license is required for each group voicemail.'''

===Installation===
Users redirect their calls to the voicemail object via call forwarding. The number of the VM object is appended as the destination number for the call forwarding and for the MWI button, e.g. if the VM object has the number 803, then the call forwarding and the MWI button use 803803 as the destination.
In the URL of the vm.xml script, use the $m variable to configure the recipients of the MWI notification.
The voicebox's directory on the mass-storage will be named like the ''Name'' of the Voicemail-Object.
To activate each group voicemail there may be an innitial call needed from any user with "Send Number" of the group voicemail number, e.g. set "Send Number" at the user 101 to 803, call 803803 and enter the PIN.

===Configuration Example===
*Assume following objects exist in your PBX:
**'''User''' ''101(Number):endeavour(Name):Endeavour(LongName)''
**'''User''' ''102(Number):atlantis(Name):Atlantis(LongName)''
**'''Voicemail''' ''803(Number):vm-group(Name):Vm-group(LongName)''
***'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=101,102
</code>
***'''E-Mail''' if desired configure a destination email address serving as a group email address
****Note: The email is sent only once to the destination configured as PBX/Objects/"vm-group"/General/E-Mail. It is up to an admin of the receiving mail server for how to distribute the email towards all potential group members.
*Configure Function-Keys at phones Endeavour, Atlantis
**'''Type''' Message Waiting
**'''Message Center Account'''
***'''Number''' ''803803''
***'''Append Own Number''' inactive/not checked
***'''Name''' ''vm-group'' - needed if multiple MWI-keys (e.g. own Voicemail and Group Voicemail) are configured on the phone.
*Configure source email address and mail server
**Edit the settings underneath '''PBX/Config/Authentication/Email Verification''' accordingly. Those are the settings being considered by the sub-script email.xml.

=== Configuration App Platform===
If using app platform the configuration can done by PBX Manager. There is a new button "add Voicemail group app". This configures the new variable "$_m" and a second one for the app "$_group" which is the name of the VM Object.
It is only necessary for the voicemail app.

The voicemail app works with sip names<ref>sip name: the dialable name, within a user's PBX-UI the edit field '''name'''</ref><ref>A comma within a sip name must be URL-escaped within the comma-separated list ''$_m..'' E.g. ''Doe, John'' => ''Doe%2C John''</ref> so that it is mandatory to configure the Message Waiting Keys and the $_m with names instead of numbers.

'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=endeavour,atlantis&$_group=vm_group&$app=on
</code>

The group voicemail app can be activated for every user by checkmark the group voicemail object in the tab "PBX/User/Apps"

==Known Problems==

==Related==
<references/>

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

Reference12r2:Maintenance/Diagnostics/Tracing

2021-11-25T08:42:54Z

Melvin.reiniger:

Using the '''trace(buffer)''' link, the trace information of the VoIP device can be viewed and saved. In the process, a text file log.txt is generated, which displays the current trace in a new browser window.

Using the '''trace(continuous)''' link, the continuous trace information of the device can be viewed and saved. In the process, a text file clog.txt is generated, which displays the current trace in a new browser window. As already mentioned, the messages are continuously automatically updated and are scrolled upwards, out of the window.

Using the '''trace(crash-dump)''' link (only for IPVA), the trap trace information of the IPVA since last crash can be viewed and saved. In the process, a text file crash_dump.txt is generated, which displays the last trap trace in a new browser window.

For both trace variants, only messages that were enabled in this menu are displayed. Not every section and not every setting is visible, this will depend on which device is being used.

* '''TEL1-n:''' Information on the TEL1-n interface.
* '''BRI1-n:''' Information on the BRI1-n interface.
* '''PRI1-n:''' Information on the PRI1-n interface.
* '''PPP:''' Information on the PPP interface.
* '''H.323/Signaling:''' Information on H.323 signaling.
* '''SIP/UDP Signaling:''' Information on SIP/UDP signaling.
* '''SIP/TCP Signaling:''' Information on SIP/TCP signaling.
* '''SIP/TLS Signaling:''' Information on SIP/TLS signaling.
* '''PBX:''' Information on PBX application.
* '''Gateway:''' Information on Gateway application.
* '''DECT Master:''' Information on DECT Master application.
* '''DECT Master/PP-Manag.:''' Information on DECT Master management.
* '''DECT Radio:''' Information on DECT Radio application.
* '''DECT Radio/PP-Manag.:''' Information on DECT Radio management.
* '''NAT:''' Information on Network Address Translation.
* '''H.323-NAT:''' Information on H.323 specific Network Address Translation.
* '''All TCP/UDP Traffic:''' Information on all TCP/UDP data (may fill up trace buffer quickly).
* '''Enable RPCAP:''' Enable Remote PCAP access in order to get continuous trace information using Wireshark ([[Howto:Pcap]]).
* '''Write PCAP to URL:''' Write PCAP trace to specified URL
:URL is expected to be the URL for a folder on a WebDAV drive like <code>http://172.16.0.1/DRIVE/CF0</code>
:A new file will be created each 20MB. The files will be called like ''<mac>''<code>-</code>''<sequential-number>''<code>.pcap</code> (e.g. <code>0090332f3364-0000003837.pcap</code>).

Howto:Group Voicemail

2021-08-12T15:57:27Z

Melvin.reiniger:

==Applies To==
This information applies to
* IPXXX, V13r2
PBX-Build 135779 and later.
VM-Build 135xxx


==More Information==
A comma-separated list of MWI destinations/recipients can be configured by means of a variable ''$_m'' within the script URL's query string. This article outlines a configuration scheme for group voicemail functionality.

===Problem Details===
A group voicemail acts as single point of storage and multiple point of access for several PBX endpoints. MWI-updates are expected to be delivered to all group members.

===System Requirements===
A standard voicemail script vm.xml is expected to be installed underneath ''/drive/CF0/vm/vm.xml''.

A PBX-VoicemailUser13 license is required for each group voicemail.

===Installation===
Two PBX phone endpoints ''Atlantis'', ''Endeavour'' share a voicebox ''vm-group'' with number ''803''. The voicebox's directory on the mass-storage will be named ''vm-group''.
The phones may redirect towards the voicebox by means of a CFU 803803. The phones access the voicebox by the Message Center Account number 803803.

If Viking calls e.g. Endeavour, it's going to be redirected into ''vm-group'' and may leave a voicemail. On call-end the participants Atlantis, Endeavour are going to receive an MWI-Activate.

===Configuration===
*Add following objects
**'''User''' ''101:Endeavour''
**'''User''' ''102:Atlantis''
**'''User''' ''301:Viking''
**'''Voicemail''' ''803:vm-group''
***'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=101,102
</code>
***'''E-Mail''' if desired configure a destination email address serving as a group email address
****Note: The email is sent only once to the destination configured as PBX/Objects/"vm-group"/General/E-Mail. It is up to an admin of the receiving mail server for how to distribute the email towards all potential group members.
*Configure Function-Keys at phones Endeavour, Atlantis
**'''Type''' Message Waiting
**'''Message Center Account'''
***'''Number''' ''803803''
***'''Append Own Number''' inactive/not checked
*Configure source email address and mail server
**Edit the settings underneath '''PBX/Config/Authentication/Email Verification''' accordingly. Those are the settings being considered by the sub-script email.xml.

=== Configuration App Platform===
If using app platform the configuration can done by PBX Manager. There is a new button "add Voicemail group app". This configures the new variable "$_m" and a second one for the app "$_group" which is the name of the VM Object.
It is only necessary for the voicemail app.

The voicemail app works with sip names<ref>sip name: the dialable name, within a user's PBX-UI the edit field '''name'''</ref><ref>A comma within a sip name must be URL-escaped within the comma-separated list ''$_m..'' E.g. ''Doe, John'' => ''Doe%2C John''</ref> so that it is mandatory to configure the Message Waiting Keys and the $_m with names instead of numbers.

'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=endeavour,atlantis&$_group=vm_group&$app=on
</code>

The group voicemail app can be activated for every user by checkmark the group voicemail object in the tab "PBX/User/Apps"

==Known Problems==

==Related==
<references/>

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

Howto:Group Voicemail

2021-08-12T15:56:20Z

Melvin.reiniger:

==Applies To==
This information applies to
* IPXXX, V13r2
PBX-Build 135779 and later.
VM-Build 135xxx


==More Information==
A comma-separated list of MWI destinations/recipients can be configured by means of a variable ''$_m'' within the script URL's query string. This article outlines a configuration scheme for group voicemail functionality.

===Problem Details===
A group voicemail acts as single point of storage and multiple point of access for several PBX endpoints. MWI-updates are expected to be delivered to all group members.

===System Requirements===
A standard voicemail script vm.xml is expected to be installed underneath ''/drive/CF0/vm/vm.xml''.
A PBX-VoicemailUser13 license is required for each group voicemail.

===Installation===
Two PBX phone endpoints ''Atlantis'', ''Endeavour'' share a voicebox ''vm-group'' with number ''803''. The voicebox's directory on the mass-storage will be named ''vm-group''.
The phones may redirect towards the voicebox by means of a CFU 803803. The phones access the voicebox by the Message Center Account number 803803.

If Viking calls e.g. Endeavour, it's going to be redirected into ''vm-group'' and may leave a voicemail. On call-end the participants Atlantis, Endeavour are going to receive an MWI-Activate.

===Configuration===
*Add following objects
**'''User''' ''101:Endeavour''
**'''User''' ''102:Atlantis''
**'''User''' ''301:Viking''
**'''Voicemail''' ''803:vm-group''
***'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=101,102
</code>
***'''E-Mail''' if desired configure a destination email address serving as a group email address
****Note: The email is sent only once to the destination configured as PBX/Objects/"vm-group"/General/E-Mail. It is up to an admin of the receiving mail server for how to distribute the email towards all potential group members.
*Configure Function-Keys at phones Endeavour, Atlantis
**'''Type''' Message Waiting
**'''Message Center Account'''
***'''Number''' ''803803''
***'''Append Own Number''' inactive/not checked
*Configure source email address and mail server
**Edit the settings underneath '''PBX/Config/Authentication/Email Verification''' accordingly. Those are the settings being considered by the sub-script email.xml.

=== Configuration App Platform===
If using app platform the configuration can done by PBX Manager. There is a new button "add Voicemail group app". This configures the new variable "$_m" and a second one for the app "$_group" which is the name of the VM Object.
It is only necessary for the voicemail app.

The voicemail app works with sip names<ref>sip name: the dialable name, within a user's PBX-UI the edit field '''name'''</ref><ref>A comma within a sip name must be URL-escaped within the comma-separated list ''$_m..'' E.g. ''Doe, John'' => ''Doe%2C John''</ref> so that it is mandatory to configure the Message Waiting Keys and the $_m with names instead of numbers.

'''Script URL''' <code type="text">
http://127.0.0.1/drive/CF0/vm/vm.xml?$_m=endeavour,atlantis&$_group=vm_group&$app=on
</code>

The group voicemail app can be activated for every user by checkmark the group voicemail object in the tab "PBX/User/Apps"

==Known Problems==

==Related==
<references/>

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

Reference11r2:PBX/Objects/Edit CFs

2016-10-07T13:20:06Z

Melvin.reiniger:

With this page call forwarding for an object can be configured. If conflicting call forwardings are configured the ones with a matching filter take precedence over the ones without filter. If there are call forwardings configured with identical filters, the result is random.

On the endpoint only Call Forwards without Boolean and Filters are visible and can be changed.

== Types of Call Forwarding ==

{|
|valign=top nowrap=true|'''CFU'''
|Call Forward Unconditional. The call is forwarded to the new destination without delay.
|-
|valign=top nowrap=true|'''CFB'''
|Call Forward on Busy. The call is forwarded to the new destination if the object is busy. If a call is rejected by the user, this is treated as busy as well.
|-
|valign=top nowrap=true|'''CFNR'''
|Call Forward on No Response. The call is forwarded if the user is not responding. This may be after alerting the user for the configurable CFNR timeout, or may be because no endpoint is registered.
|}

== Properties of a Call Forward configuration ==

{|
|valign=top nowrap=true|'''No, Name'''
|The destination of the Call Forward. If as destination number '''-''' (minus sign) is configured no call forward is executed and the call is also not forwarded to the no-response or busy destination configured at a Trunk or Node.
|-
|valign=top nowrap=true|'''Not, Bool'''
|With this configuration a Call Forward can be made depending on the state of a Boolean Object. This means the Call Forward is only executed if the Boolean Object is 'true'. If the Not checkmark is set, the Call Forward is only executed if the Boolean Object is false.
|-
|valign=top nowrap=true|'''Only, Only Not'''
|A list of filters can be configured to a call forward, to forward calls from 'Only' certain calling numbers or 'Only Not' certain numbers including previous forwarding numbers on this call. A headmatch is performed on the configured numbers. This means if e.g. a filter is configured to forward calls from 'Only 0', all calls from numbers starting with 0 are forwarded.

For conflicting 'Only' and 'Only Not' configurations the 'Only' configuration takes precedence.
|-
|valign=top nowrap=true|'''Int. and Ext.'''
|Filter option to check for Internal/External calls explicitly. The private numbering plan is used to determine if a call is Internal
|-
|valign=top nowrap=true|'''Clid, Fwd, Both'''
|Filter option to select which numbers are taken into account for the filters. By default only the last diverting number is used, if there is one, otherwise the calling line id. With the option 'clid' only the calling line id is used, with 'Fwd' only the last diverting number and with 'Both' the calling line id and the last diverting number.
|}

Reference:Administration/PBX/Filter

2016-01-28T07:45:10Z

Melvin.reiniger: /* Example 3 (restricted external calls via differnet trunk numbers and different number formats) */

In the innovaphone PBX, it is possible to define global call filters. These filters can be used to restrict the numbers which are allowed as destination for calls or diversions on a per user basis.

== Call filter ==

=== Configuration ===

{|
|valign=top nowrap=true|'''Name'''
|The name of the filter. The name may not be ok or nok , since these names refer to filter properties. This name is used to configure a filter at an object.
|-
|valign=top nowrap=true|'''Not / Boolean'''
|A filter can be made dependent on the state of a Boolean object. If a Boolean object was defined here, the filter is only effective if the Boolean object is set to true (Not checkbox not checked) or false (Not checkbox checked)
|-
|valign=top nowrap=true|'''Number'''
|Number used to match a call/diversion destination. A '?' can be used to match any digit (available starting with v6 SR2 hotfix5). If there are multiple matching filters, the match with the highest number of digits wins.
|-
|valign=top nowrap=true|'''Next (ok/nok/filter)'''
|Possible entries: ok, nok, Filter name (for calling up a further filter with the designated filter name).
|}

=== Example 1 (internal calls only) ===

This filter prohibits any number beginning with 0 to be dialed. If the trunk object is defined with number 0 no outside calls can be made by the user with this filter configured.

{|
||'''Number'''
|'''Next'''
|-
||0
|nok
|}

=== Example 2 (internal calls only with exceptions) ===

This filter prohibits any number beginning with 0 to be dialed. If the trunk object is defined with number 0 no outside calls can be made by the user with this filter configured. The numbers 0110 and 0112 are excluded from this rule.

{|
||'''Number'''
|'''Next'''
|-
||0
|nok
|-
||0110
|ok
|-
||0112
|ok
|}

=== Example 3 (restricted external calls via differnet trunk numbers and different number formats) ===

This filter makes use of filter names instead of ''ok'' or ''nok''. This feature is usefull to restrict access to set of public numbers that can be reached via different trunk numbers and differnet number formats like international, national and local.

This example prohibits value added numbers 0900 and 0137 dialed via two trunks 0 and 9 in both number format, national and international.

{| border=1
||'''Filter Name'''||'''Number'''||'''Next'''||'''Comment'''
|-
||restricted||900||nok||value added numbers
|-
|| ||137||nok||value added numbers
|-
||my_filter||00049||restricted||numbers dialed in international format via trunk 0
|-
|| ||00||restricted||numbers dialed in national format via trunk 0
|-
|| ||80049||restricted||numbers dialed in international format via trunk 8
|-
|| ||80||restricted||numbers dialed in national format via trunk 8
|}

== IP Filter ==

In the '''IP Filter''' section, you can define global IP address filters to protect the innovaphone PBX from unauthorised access:
* '''Address:''' The network address to be filtered.
* '''Mask:''' The associated network mask.
On the networks defined here, registrations per PBX object without password are possible (as defined as ''No of Regs w/o Pwd.'' in [[Reference7:Administration/PBX/General|PBX/General]]. If nothing is configured here, a registration without password is possible from any IP address.

== Boolean ==

In the '''Boolean''' section, all objects that were created as a Boolean object in the chapter entitled "[[Reference:Administration/PBX/Objects|Administration/PBX/Objects]]" are displayed.

== Related Articles ==

[[Howto:Diversion_filter_at_the_user_object]]

This page has been locked to prevent editing

2015-11-30T13:08:46Z

Melvin.reiniger:

Sebastian Lesch
'''Altmeyer GmbH'''

Steffen Koch
'''Telekim GmbH'''

Andreas Kapusta
'''E-PROJECTA GmbH'''

Marcel Eisenhut
'''RMD Informatik GmbH'''

Timo Espenschied
'''BIZTEAM Systemhaus GmbH'''

Gabriele Alberti
'''B.F.Telecomunicazioni'''

Sandro Cecchi
'''Sokom Srl'''

Marcel Szloboda
'''Steiger Electronics'''

Tobias Spechtenhauser
'''IZComputer/Interzegg AG'''

Marc Laakmann
'''Nagel Kraftverkehr GmbH & Co. KG'''

Michael Penski
'''Deutsche Windtechnik Service GmbH & Co. KG'''

Maikel Schaap
'''Eilie Telecom'''

Joachim sawatzki
'''Telta Citynetz GmbH'''

Domien Maebe
'''CBM Moerman'''
Stefan Etter
'''Binder-Systemhaus GmbH'''

Nuri Payam
'''Flughafen Münster Osnabrück GmbH'''

Dominik Feistenberger
'''Stahl Computertechnik GmbH'''

Frank von Prondzinsky
'''Langnese Telecom'''

Dirk Köther
'''InterData Praxiscomputer GmbH'''

Roland Alterdinger
'''Ebinger Netzwerktechnik GmbH'''

Christof Wegener
'''Service One Gebäude Management GmbH'''

Nicola

Raffael Helmhart
'''itex it-service GmbH'''

Simon Röblreiter
'''itex it-service GmbH'''

Dennis Uka
'''Kraftverkehr Nagel GmbH & Co. KG'''

Sebastian Schmidt
'''CHT Heinemann GmbH'''

Johnny Zengers
'''LNS'''

Wolfgang Schmid
'''kufgem EDV GmbH'''

Christian Pierson
'''IT-Kontor GmbH & Co. KG'''

Bernd Hässig
'''ASCOM Solutions AG'''

Dominik Pfister
'''ASCOM Solutions AG'''

Sisto Menini
'''Attiva SpA'''

Leon van der Burgt
'''DTC Systems BV'''

Thomas Mayer
'''RTM Business IT GmbH'''

Roland Trieb
'''RTM Business IT GmbH'''

Jan-Simon Lucas
'''IP Dynamics GmbH'''

Manfred Peukert
'''SCOUT CONSULT GmbH'''

Dietmar Simons
'''Ascom Deutschland GmbH'''

Torsten Dieckhoff
'''TEDi GmbH & Co.KG'''

Marian Kühner
'''Sparkasse Mittelthüringen'''

Frank Meisenzahl
'''Comnet Region Mitte GmbH'''

Robert Walter
'''INNOVA-IT GmbH'''

Christoph Karl
'''SEC-COM GmbH'''

Margus Laanem
'''Datafox OÜ'''

Dennis Emde
'''Gelsen-Net Kommunikationsgesellschaft mbH'''

Carsten Buschmann
'''SNcom GmbH'''

Mario Krieg
'''ROMICO GmbH'''

Maurizio Perucchini
'''Vallcom srl'''

Volkan Ucar
'''bilobit GmbH'''

Andre Nitsch
'''Mobene GmbH & Co. KG'''

Frank Dickamp
'''KOMSA NordWest'''

Rico Skerra
'''commehr GmbH'''

Andreas Erdweg
'''Comnet Region Mitte GmbH'''

Melvin Reiniger
'''telenetwork AG'''