<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.innovaphone.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=H.daroca</id>
	<title>innovaphone wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.innovaphone.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=H.daroca"/>
	<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Special:Contributions/H.daroca"/>
	<updated>2026-05-09T20:48:52Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.42.3</generator>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:ToaSpeakers_-_toa_-_3rd_Party_Product&amp;diff=76067</id>
		<title>Howto:ToaSpeakers - toa - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:ToaSpeakers_-_toa_-_3rd_Party_Product&amp;diff=76067"/>
		<updated>2025-03-31T15:31:26Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Toa.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Toa IP Horn Speaker [https://www.toa.eu/products/ip-a1sc15/ IP-A1SC15]&amp;lt;br&amp;gt;&lt;br /&gt;
Toa IP Ceiling Speaker [https://www.toa.eu/products/ip-a1pc238/ IP-A1PC238]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be added by innovaphone upon document check &amp;amp; app availablity on appstore --&amp;gt;&lt;br /&gt;
{{Template:Compat_Status_referral_terminals|manufacturername=TOA Electronics Europe GmbH|certificationdate=in July 2024}}&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:Toasinletras.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
TOA offers worldwide innovative products and high-quality services as a specialist manufacturer in the field of sound solutions.&lt;br /&gt;
Dr. Sound embodies the image, strategy and values of TOA, standing behind our slogan, “We supply sound, not equipment.”&lt;br /&gt;
It is our goal to provide first-class sound to find the ideal acoustic solution for each of your projects.&lt;br /&gt;
We supply solutions for excellent sound, not only equipment.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
Plug &amp;amp; Sound: Based on open standards, the IP-A1SC15 IP Horn Speaker plugs right into standard IP networks and can be easily integrated with your VMS or SIP-based system.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Based on open standards, the IP-A1PC238 IP Ceiling Speaker plug right into standard IP networks and can be easily integrated into your video management system (VMS) or SIP-based communication system.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can find technical documentation:&amp;lt;br&amp;gt; &lt;br /&gt;
[https://www.toa.eu/products/ip-a1sc15/ ip-a1sc15]&amp;lt;br&amp;gt;&lt;br /&gt;
[https://www.toa.eu/products/ip-a1pc238/ ip-a1pc238]&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--&#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
TOA’s extensive audio expertise can now be integrated into your IP network solution. Combine the possibilities and benefits of IP security systems and audio devices to help protect people and property. Turn your SIP telephone system into a network paging solution. Or provide your BGM installation with flexible and feature-rich network audio equipment. The applications are manifold.&lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) - no&lt;br /&gt;
* Answer incoming call - no&lt;br /&gt;
* Hold/Retrieve - no&lt;br /&gt;
* Transfer - no&lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* STUN         - no&lt;br /&gt;
* TURN         - no&lt;br /&gt;
* ICE          - no&lt;br /&gt;
* SIP/UDP      - yes&lt;br /&gt;
* SIP/TCP      - no&lt;br /&gt;
* SIP/TLS      - no&lt;br /&gt;
  &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Codec G.711u/a - yes&lt;br /&gt;
* Codec OPUS - no&lt;br /&gt;
* DTLS encryption - no &lt;br /&gt;
&lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* G.722       - yes&lt;br /&gt;
* G.711 A-law - yes&lt;br /&gt;
* G.711 y-law - yes&lt;br /&gt;
* G.723.1     - no&lt;br /&gt;
* G.729A      - no&lt;br /&gt;
* Opus        - no &lt;br /&gt;
&lt;br /&gt;
==DTMF Support==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* RTP DTMF (inband)  - no&lt;br /&gt;
* RFC 2833 RTP Event - yes&lt;br /&gt;
&lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Supports RFC3261 Digest Authentication Scheme (Section 22.4) - no &lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Support LDAP Phonebook - no&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* IP Horn Speaker IP-A1SC15 Version 3.1.0 &lt;br /&gt;
* IP Ceiling Speaker IP-A1PC238 Version 3.1.0&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V14r1sr4&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
1) create a user.&lt;br /&gt;
[[File:Inno1b toa.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
===Toa Configuration===&lt;br /&gt;
1) Networking settings&lt;br /&gt;
[[File:Config inno toa1.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
2) SIP Settings&lt;br /&gt;
[[File:Config toa2 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
3) Save&lt;br /&gt;
[[File:Config toa3 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
4) The changes will be applied after reboot&lt;br /&gt;
[[File:Config toa4 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
5) Reboot&lt;br /&gt;
[[File:Config toa5 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
6) after a minute we will see the device registered&lt;br /&gt;
[[File:Config toa6 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://www.toa.eu/&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| TOA Electronics Europe GmbH &lt;br /&gt;
|-&lt;br /&gt;
| Celia Garcia Aguayo&lt;br /&gt;
|-&lt;br /&gt;
| Süderstraße 282&lt;br /&gt;
|-&lt;br /&gt;
| 20537 Hamburg Germany&lt;br /&gt;
|-&lt;br /&gt;
| Tel: +49 (0) 40 25 17 190&lt;br /&gt;
|-&lt;br /&gt;
| Mob: +34 627 698 745&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:cgarcia@toa-eu.com cgarcia@toa-eu.com]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Inno1b_toa.png&amp;diff=76066</id>
		<title>File:Inno1b toa.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Inno1b_toa.png&amp;diff=76066"/>
		<updated>2025-03-31T15:28:55Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;user creation&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:ToaSpeakers_-_toa_-_3rd_Party_Product&amp;diff=72618</id>
		<title>Howto:ToaSpeakers - toa - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:ToaSpeakers_-_toa_-_3rd_Party_Product&amp;diff=72618"/>
		<updated>2024-07-16T07:42:28Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: Created page with &amp;quot;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt; right  ==Product Name== &amp;lt;!-- Mandatory topic. --&amp;gt; &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt; Toa IP Horn Speaker [https://www.toa.eu/products/ip-a1sc15/ IP-A1SC15]&amp;lt;br&amp;gt; Toa IP Ceiling Speaker [https://www.toa.eu/products/ip-a1pc238/ IP-A1PC238]&amp;lt;br&amp;gt;  ==Certification Status== &amp;lt;!-- do not remove co...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Toa.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Toa IP Horn Speaker [https://www.toa.eu/products/ip-a1sc15/ IP-A1SC15]&amp;lt;br&amp;gt;&lt;br /&gt;
Toa IP Ceiling Speaker [https://www.toa.eu/products/ip-a1pc238/ IP-A1PC238]&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be added by innovaphone upon document check &amp;amp; app availablity on appstore --&amp;gt;&lt;br /&gt;
{{Template:Compat_Status_referral_terminals|manufacturername=TOA Electronics Europe GmbH|certificationdate=in July 2024}}&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:Toasinletras.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
TOA offers worldwide innovative products and high-quality services as a specialist manufacturer in the field of sound solutions.&lt;br /&gt;
Dr. Sound embodies the image, strategy and values of TOA, standing behind our slogan, “We supply sound, not equipment.”&lt;br /&gt;
It is our goal to provide first-class sound to find the ideal acoustic solution for each of your projects.&lt;br /&gt;
We supply solutions for excellent sound, not only equipment.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
Plug &amp;amp; Sound: Based on open standards, the IP-A1SC15 IP Horn Speaker plugs right into standard IP networks and can be easily integrated with your VMS or SIP-based system.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Based on open standards, the IP-A1PC238 IP Ceiling Speaker plug right into standard IP networks and can be easily integrated into your video management system (VMS) or SIP-based communication system.&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
You can find technical documentation:&amp;lt;br&amp;gt; &lt;br /&gt;
[https://www.toa.eu/products/ip-a1sc15/ ip-a1sc15]&amp;lt;br&amp;gt;&lt;br /&gt;
[https://www.toa.eu/products/ip-a1pc238/ ip-a1pc238]&amp;lt;br&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--&#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
TOA’s extensive audio expertise can now be integrated into your IP network solution. Combine the possibilities and benefits of IP security systems and audio devices to help protect people and property. Turn your SIP telephone system into a network paging solution. Or provide your BGM installation with flexible and feature-rich network audio equipment. The applications are manifold.&lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) - no&lt;br /&gt;
* Answer incoming call - no&lt;br /&gt;
* Hold/Retrieve - no&lt;br /&gt;
* Transfer - no&lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* STUN         - no&lt;br /&gt;
* TURN         - no&lt;br /&gt;
* ICE          - no&lt;br /&gt;
* SIP/UDP      - yes&lt;br /&gt;
* SIP/TCP      - no&lt;br /&gt;
* SIP/TLS      - no&lt;br /&gt;
  &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Codec G.711u/a - yes&lt;br /&gt;
* Codec OPUS - no&lt;br /&gt;
* DTLS encryption - no &lt;br /&gt;
&lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* G.722       - yes&lt;br /&gt;
* G.711 A-law - yes&lt;br /&gt;
* G.711 y-law - yes&lt;br /&gt;
* G.723.1     - no&lt;br /&gt;
* G.729A      - no&lt;br /&gt;
* Opus        - no &lt;br /&gt;
&lt;br /&gt;
==DTMF Support==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* RTP DTMF (inband)  - no&lt;br /&gt;
* RFC 2833 RTP Event - yes&lt;br /&gt;
&lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Supports RFC3261 Digest Authentication Scheme (Section 22.4) - no &lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
* Support LDAP Phonebook - no&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* IP Horn Speaker IP-A1SC15 Version 3.1.0 &lt;br /&gt;
* IP Ceiling Speaker IP-A1PC238 Version 3.1.0&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V14r1sr4&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
1) create a user.&lt;br /&gt;
[[File:Config inno1 toa.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
===Toa Configuration===&lt;br /&gt;
1) Networking settings&lt;br /&gt;
[[File:Config inno toa1.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
2) SIP Settings&lt;br /&gt;
[[File:Config toa2 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
3) Save&lt;br /&gt;
[[File:Config toa3 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
4) The changes will be applied after reboot&lt;br /&gt;
[[File:Config toa4 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
5) Reboot&lt;br /&gt;
[[File:Config toa5 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
6) after a minute we will see the device registered&lt;br /&gt;
[[File:Config toa6 inno.png|thumb|left]]&lt;br /&gt;
&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://www.toa.eu/&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{|&lt;br /&gt;
| TOA Electronics Europe GmbH &lt;br /&gt;
|-&lt;br /&gt;
| Celia Garcia Aguayo&lt;br /&gt;
|-&lt;br /&gt;
| Süderstraße 282&lt;br /&gt;
|-&lt;br /&gt;
| 20537 Hamburg Germany&lt;br /&gt;
|-&lt;br /&gt;
| Tel: +49 (0) 40 25 17 190&lt;br /&gt;
|-&lt;br /&gt;
| Mob: +34 627 698 745&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:cgarcia@toa-eu.com cgarcia@toa-eu.com]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Config_toa6_inno.png&amp;diff=72413</id>
		<title>File:Config toa6 inno.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Config_toa6_inno.png&amp;diff=72413"/>
		<updated>2024-07-01T16:32:44Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Config toa6 inno&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Config_toa5_inno.png&amp;diff=72412</id>
		<title>File:Config toa5 inno.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Config_toa5_inno.png&amp;diff=72412"/>
		<updated>2024-07-01T16:25:05Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Config toa5 inno&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Config_toa4_inno.png&amp;diff=72411</id>
		<title>File:Config toa4 inno.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Config_toa4_inno.png&amp;diff=72411"/>
		<updated>2024-07-01T16:22:20Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Config toa4 inno&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Config_toa3_inno.png&amp;diff=72410</id>
		<title>File:Config toa3 inno.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Config_toa3_inno.png&amp;diff=72410"/>
		<updated>2024-07-01T16:21:03Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Config toa3 inno&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Config_toa2_inno.png&amp;diff=72409</id>
		<title>File:Config toa2 inno.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Config_toa2_inno.png&amp;diff=72409"/>
		<updated>2024-07-01T16:19:46Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Config toa2 inno&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Config_inno_toa1.png&amp;diff=72408</id>
		<title>File:Config inno toa1.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Config_inno_toa1.png&amp;diff=72408"/>
		<updated>2024-07-01T16:07:36Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Config inno toa1&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Config_inno1_toa.png&amp;diff=72407</id>
		<title>File:Config inno1 toa.png</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Config_inno1_toa.png&amp;diff=72407"/>
		<updated>2024-07-01T15:56:02Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Config inno1 toa&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:IP-A1SC15-520x400.jpg&amp;diff=72391</id>
		<title>File:IP-A1SC15-520x400.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:IP-A1SC15-520x400.jpg&amp;diff=72391"/>
		<updated>2024-07-01T14:31:01Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;IP-A1SC15-520x400.jpg&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Toasinletras.jpg&amp;diff=72390</id>
		<title>File:Toasinletras.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Toasinletras.jpg&amp;diff=72390"/>
		<updated>2024-07-01T14:16:23Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Toa sin letras&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Toa.jpg&amp;diff=72388</id>
		<title>File:Toa.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Toa.jpg&amp;diff=72388"/>
		<updated>2024-07-01T13:56:18Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Logo Toa&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=71079</id>
		<title>Howto14r1:Firmware Upgrade V13r3 V14r1</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=71079"/>
		<updated>2024-03-05T14:55:49Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 14r1 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 14r1, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
== Licenses ==&lt;br /&gt;
If the system is licensed on premise, you&#039;ll need to regenerate the license file for V14 in https://portal.innovaphone.com/ and load into the system before upgrade (The system needs to have the SSC up to date).&lt;br /&gt;
&lt;br /&gt;
In case of cloud or rental model, don&#039;t worry about licenses.&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 14r1.&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 14r1 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend upgrading the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend reviewing all the configuration changes described below &#039;&#039;&#039;before&#039;&#039;&#039; you begin the update.&lt;br /&gt;
&lt;br /&gt;
== Changes visible to the end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 14r1 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
=== Softphone/Phone App UI changes === &lt;br /&gt;
* Dial-pad is now a new tab in the navigation.&lt;br /&gt;
* On Smartphones, the Navigation is in the bottom.&lt;br /&gt;
* Call button is removed from the searchbar. Calling only via the search results.&lt;br /&gt;
=== Configuration of Logo URI ===&lt;br /&gt;
* In 13r3 this configuration was done in the advanced UI on the page PBX / Config / myPBX / Logo URI.&lt;br /&gt;
* But in 14r1 it can be found on the page PBX / Config / General / Logo URL.&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
Extra features for the users:&lt;br /&gt;
* Call the voicemailbox directly from the app.&lt;br /&gt;
* PIN-code can be checked (hidden by default; visible with a click) and changed/set back to default.&lt;br /&gt;
* Call Forwards to the Voicemailbox can be activated/removed (CFU/CFB/CFNR).&lt;br /&gt;
* Number Resolution via the Search Provider.&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
* While sending an outgoing fax via the fax app, you now can select and configure a fax cover page before sending.&lt;br /&gt;
* While configuring a fax app or groupfax via the PBX Manager plugin, you can customize the header line of fax pages and select a language.&lt;br /&gt;
* After updating from 13r3 or setting up your device with 14r1, the Fax object has 4 new options, which are enabled by default:&lt;br /&gt;
** Modem capability: the supported modem class can be changed if necessary.&lt;br /&gt;
** Append user number: if checked, the user number will be appended to the object number.&lt;br /&gt;
** ECM: that allows the T.30 connection to use error correction mode.&lt;br /&gt;
** Receiving with 400dpi allowed: which allows you to receive 400*400dpi documents.&lt;br /&gt;
===AP Manager===&lt;br /&gt;
* The AP Manager UI has been reworked. It is now responsive design, improved view of all app services and instance. Rework of statistic of CPU/RAM/used disk. This change is for the IT administrator, not relevant for end users&lt;br /&gt;
&lt;br /&gt;
== Changed Apps ==&lt;br /&gt;
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Devices App ===&lt;br /&gt;
New Device Configurations option to roll out certificates to the trust list of your devices. [[Reference14r1:Concept_App_Service_Devices#Certificates_configuration]]&lt;br /&gt;
&lt;br /&gt;
=== Recordings App ===&lt;br /&gt;
New option to add WebDav credentials in RecordingsAdmin. [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]&lt;br /&gt;
&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
* New Setting to configure the automatic deletion of old(er) voicemail-messages per app. [[Reference14r1:Concept_App_Service_Voicemail#Settings]]&lt;br /&gt;
* New Option to configure the default PIN per voicemail system. [[Reference14r1:Concept_App_Service_Voicemail#add_voicemail]]&lt;br /&gt;
: By configuring a PIN code from a different length, you also configure the length of the PIN code used by the system.&lt;br /&gt;
&lt;br /&gt;
== New Apps ==&lt;br /&gt;
New Apps will not be installed automatically by the 13r3 to 14r1 upgrade. The installation description of new 14r1 apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.&lt;br /&gt;
&lt;br /&gt;
=== Calculator ===&lt;br /&gt;
*Although already released in 13r3 sr11, this app is now part of the 14r1 install. This app is explained in [[Reference13r3:Concept_App_Service_Calculator_App | the concept article]] and [[Howto14r1:Set_up_the_calculator_app| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connect ===&lt;br /&gt;
* A microblogging tool. This app is explained in [[Reference14r1:Concept_App_Service_Messages | the concept article]] and [[Howto14r1:Set_up_Connect| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connector for Let&#039;s Encrypt ===&lt;br /&gt;
* Automatically creates &amp;amp; renews Let&#039;s Encrypt certificates, the App is included in the Install process - however when doing an upgrade it needs to be [[Reference14r1:Concept_Let%27s_Encrypt#Configuration | setup manually]].&lt;br /&gt;
&lt;br /&gt;
=== Contact Widgets App ===&lt;br /&gt;
* A Contact Widget (or Website Widget) is an element that can be added to a website. It offers to website visitors a way to get in contact with agents (e.g. help-desk). Website visitors can start chat sessions (asking questions, getting answers) or can start voice or even video calls. &lt;br /&gt;
&lt;br /&gt;
For more details have a look at [[Reference14r1:Concept Contact Widgets | the concept article]].&lt;br /&gt;
&lt;br /&gt;
Customers using the previous Widgets, should change to the new [[Howto14r1:Firmware_Upgrade_V13r3_V14r1#Widgets | Contact Widgets App ]]&lt;br /&gt;
&lt;br /&gt;
===Notes===&lt;br /&gt;
*Digital notes can be managed with the innovaphone app Notes. The app has a minimalistic feature set and is easy to use. The notes are saved on the server and available on all devices of the users. More infos available in the [[Reference14r1:Concept_App_Service_Notes_App | Reference article]]&lt;br /&gt;
&lt;br /&gt;
===PBX Manager - AP app installer===&lt;br /&gt;
*in the PBX manager you will find a new coloured plugin. this new plugin give access to the App store in order to ease the installation of an App service and its instance. You basically do not need to go to the AP platform when you want to install a new application. Idea is to have the further installed app done by this plugin, this also ease the way to discover new applications. More infos available in the [[Reference14r1:Concept_App_Platform#App_Installer_PBX_Manager_Plugin | Reference article]]&lt;br /&gt;
&lt;br /&gt;
=== Search App ===&lt;br /&gt;
* The app is immediately available on the PBX (no configuration is needed). In a new V14r1 configuration the Install provides all Users with this Search App via the &amp;quot;Config User&amp;quot;-Template. If the same configuration is required on an upgraded config, the Search App (&amp;quot;search&amp;quot;) can be ticked in the &amp;quot;Config User&amp;quot; template. For details refer to [[Reference14r1:Concept_App_Search | the concept article]].&lt;br /&gt;
&lt;br /&gt;
=== TechAssist ===&lt;br /&gt;
* Application for quality assurance and improvement of systems by collecting static and runtime information. For details refer to [[Reference14r1:Concept_App_Service_TechAssist | the concept article]].&lt;br /&gt;
&lt;br /&gt;
== Needed configuration changes ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== EchoCanceller of myApps Client for Windows ===&lt;br /&gt;
In 14r1 the Windows client uses by default a Windows provided EchoCanceller. To switch back to the default Echocanceller used in 13r3, create a Windows registry entry in Computer\HKEY_CURRENT_USER\Software\innovaphone\myApps with the following values:&lt;br /&gt;
 Type: DWORD (REG_DWORD)&lt;br /&gt;
 Name: webrtcEchoCanceller&lt;br /&gt;
 Value: 1&lt;br /&gt;
&lt;br /&gt;
If the 13r3 echo-canceller is used, the myApps trace of a call will contain a line &#039;&#039;[AC] echo canceller is WebRTC aec3&#039;&#039;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Virtual Appliance on VMWare ===&lt;br /&gt;
After deploying the new firmware modify the guest configuration file (stemming from ipva.vmx) for all network cards as such:&lt;br /&gt;
Modify e.g. &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vlance&amp;quot;&amp;lt;/code&amp;gt; to become &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vmxnet3&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== IPVA certificates ==&lt;br /&gt;
IPVA certificates are no longer signed by &#039;&#039;&#039;innovaphone Device Certification Authority 2&#039;&#039;&#039;.&lt;br /&gt;
Instead they will be now signed by &#039;&#039;&#039;innovaphone Unverified Device CA&#039;&#039;&#039;, as innovaphone cannot control the serial numbers and thus the certificate creation of IPVAs.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In a 14r1 install you&#039;ll be asked whether you want to always trust this new CA or not. If you decide not to trust this CA, you have to manually trust newly created IPVA certificates.&amp;lt;br/&amp;gt;&lt;br /&gt;
Note that this is not neccessary for local registrations inside the IPVA itself and doesn&#039;t affect hardware phone registrations.&lt;br /&gt;
&lt;br /&gt;
You can download the innovaphone Unverified Device CA here: https://download.innovaphone.com/certificates/ca-unverified.pem &amp;lt;br/&amp;gt;&lt;br /&gt;
If you want to trust this new CA or your own IPVA certificates, you can use the Devices App to roll out certificates to the trust list of your devices.&lt;br /&gt;
&lt;br /&gt;
== Removed in 14r1 ==&lt;br /&gt;
The following software is no longer included in 14r1.&lt;br /&gt;
=== myPBX ===&lt;br /&gt;
This includes the following components&lt;br /&gt;
* myPBX webclient&lt;br /&gt;
* myPBX for Windows&lt;br /&gt;
* myPBX for iOS&lt;br /&gt;
* myPBX for Android&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Widgets===&lt;br /&gt;
The Widgets were based on the myPBX interfaces that have been removed. Please migrate to the [[Reference14r1:Concept Contact Widgets | the Contacts Widget App]].&lt;br /&gt;
&lt;br /&gt;
===WebRTC toolkit===&lt;br /&gt;
The WebRTC toolkit was based on the myPBX interfaces that have been removed.&lt;br /&gt;
Please use the current interfaces and libraries described in the &#039;&#039;&#039;[https://sdk.innovaphone.com innovaphone SDK]&#039;&#039;&#039;.&lt;br /&gt;
=== Windows Softwarephone ===&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps for Windows&#039;&#039;&#039; and the &#039;&#039;&#039;Softphone App&#039;&#039;&#039;.&lt;br /&gt;
===PBX Object Settings ===&lt;br /&gt;
The object provided the PBX Settings App that was used to configure dynamic group memberships in myPBX.&lt;br /&gt;
Please use the &#039;&#039;&#039;Profile App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
===PBX Object ICP ===&lt;br /&gt;
Please use the integrated presence features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
===Service Call-Lists ===&lt;br /&gt;
This service implemented call lists for myPBX on the local CF card.&lt;br /&gt;
Please use the &#039;&#039;&#039;Reports App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
== Deprecated in 14r1 ==&lt;br /&gt;
The following software is based on legacy technology with no further development and limited maintenance and support.&lt;br /&gt;
We strongly recommend migrating to our successor products that are fully compatible with 14r1 and myApps technology.&lt;br /&gt;
&lt;br /&gt;
=== Linux Application Platform (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;innovaphone App Platform&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
&lt;br /&gt;
=== innovaphone Faxserver (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Fax App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Reporting (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Reports App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Exchange (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Calendar App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== Operator (v9) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Switchboard App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Voice Recording 2014 ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Recordings App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== PBX Object External UC ===&lt;br /&gt;
Existing configurations still work. But new configurations can&#039;t be done using the advanced UI anymore.&lt;br /&gt;
&lt;br /&gt;
Please use the integrated &#039;&#039;&#039;UC&#039;&#039;&#039; and &#039;&#039;&#039;federation&#039;&#039;&#039; features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For presence synchronization with other systems we recommend using&lt;br /&gt;
* &#039;&#039;&#039;innovaphone myApps Connector for Microsoft 365&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Connector for kuando®&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Calendar App&#039;&#039;&#039;&lt;br /&gt;
==Known Problems==&lt;br /&gt;
===Long Update-duration===&lt;br /&gt;
When you update, it can be up to 10 minutes before you have access to your app platform again.&lt;br /&gt;
===Fax from 14r1 to 13r3 App===&lt;br /&gt;
14r1 faxes are sent with 400dpi by default, which the 13r3 app doesn&#039;t support and you will see a [[Reference14r1:Concept_App_Service_Fax#Known_Issues|non working incoming fax]]. The second try with lower resolution will work.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 14r1 release will consume the same amount of RAM compared to a v13r3 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory  ===&lt;br /&gt;
As a rough rule of thumb, a v14r1 release will consume ~ 1.8 MB more flash memory compared to a v13r3 firmware.&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v14r1.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 13r3 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 13r3, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 13r2.  For hints on upgrading a system to 13r2 see [[Howto:V13_Firmware_Upgrade_V13r1_V13r2]].&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 13r3 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend to upgrade the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend to review all the configuration changes described below before you begin the update.&lt;br /&gt;
&lt;br /&gt;
== Configuration Changes ==&lt;br /&gt;
In 13r3 we have introduced some new features which are automatically configured if you use the installer to setup your new 13r3 from scratch. If you upgrade an existing installation, you have to configure the following settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Default SRTP key exchange value in device configuration of Phones/Interfaces ===&lt;br /&gt;
Before v13r3, the default value for SRTP key exchange was SDES-DTLS - with v13r3 it changes to the more secure DTLS-SDES. Therefore innovaphone devices now use DTLS instead - if the called endpoint has this preference. To make sure the more secure key exchange is used, we recommend adjusting the &#039;&#039;SRTP key exchange setting&#039;&#039; in the Devices App, &#039;&#039;Device Configuration&#039;&#039; for &#039;&#039;[Phone]&#039;&#039; and &#039;&#039;[Analog phone/fax]&#039;&#039;. An exception to this recommendation is if you are using old phone models (IP110A, IP240A) or gateway models (IP24, IP22) in your setup - as these may have CPU performance issues in the connection setup phase. In that case, use &#039;&#039;&#039;SDES-DTLS&#039;&#039;&#039; as value for the &#039;&#039;SRTP key exchange&#039;&#039; for all devices, not only for the old phone models.&lt;br /&gt;
&lt;br /&gt;
===Group Fax===&lt;br /&gt;
The fax object has to be configured as external resource of a group fax object in 13r3. It is therefore &#039;&#039;&#039;mandatory&#039;&#039;&#039; to assign the fax object as an external resource to all group fax objects after the upgrade - via PBX Manager .&lt;br /&gt;
&lt;br /&gt;
In the Advanced UI, you have to enter the h323/sip name of the fax object in the field &#039;&#039;&#039;External Resource Destination&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Also, with 13r3, group faxes can have their own international fax number and company name, so you should fill in these fields, or else the fax header will be empty.&lt;br /&gt;
&lt;br /&gt;
===Contacts App | User drop-down menu for sharing address books===&lt;br /&gt;
With 13r3, personal address books can be created and shared with users/groups. To have a search and drop-down menu in the sharing step, you have to activate the &amp;quot;Admin&amp;quot; option at the &amp;quot;ContactsApi&amp;quot; app object (tab &amp;quot;App&amp;quot;) over the Advanced UI. Otherwise, no results will be shown, and you have to enter the correct h323 name of a user.&lt;br /&gt;
&lt;br /&gt;
===Improved Conference Rooms===&lt;br /&gt;
* The &#039;&#039;Web Access allowed&#039;&#039; checkbox in the conference app has to be set in order to access the Conference Web Access UI.&lt;br /&gt;
: To be able create HTTP links for external participants, the conferencing App is required.&lt;br /&gt;
* Update the [[Reference13r3:PBX/Objects/Conference/Announcement_types#Sample_Announcement_Files | announcements]] for your conference rooms, to include also the &#039;&#039;Web Access announcements&#039;&#039;. &lt;br /&gt;
* it is recommended to use a second Turn-Server listening on TCP port 443 as a fallback option for external conference participants, with local firewalls not allowing access to your standard Turn-server. Configure this second Turn-Server in [[Reference13r3:IP4/General/STUN#TURN_Extern | IP4/General/STUN -&amp;gt; Turn Extern]] [[User:Sga|Sga]] TBD: info zu inno Turn Fallback server&lt;br /&gt;
* 13r3 adds a search-API for the Conference Rooms, allowing users to search for Conference room names from their Phone, Softphone or RCC App. Each conference object provides its own search API which is named like &#039;&#039;&amp;lt;Name-of-conference-object&amp;gt;.search&#039;&#039; and access to it can be granted using the App-Section of a PBX-object. The PBX-Manager Plugin for Conferences offers also an option to add the rights for all conference rooms and their search-APIs to the Config-User and/or Config-Admin template.&lt;br /&gt;
&lt;br /&gt;
=== NTLM/OAuth===&lt;br /&gt;
13r3 introduces OAuth2 Windows Authentication for myApps. If your are currently using NTLM/Netlogon for authentication, you might want to consider upgrading it OAuth2, since this authentication mechanisms is more secure. See [[Reference13r3:Concept OAuth2 Windows Authentication]] for details. &lt;br /&gt;
In 13r3 only Microsoft AD FS is supported as OpenID Server.&lt;br /&gt;
&lt;br /&gt;
===HTTP-Proxy===&lt;br /&gt;
13r3 introduces [[Reference13r3:Concept_myApps_platform_services#HTTP_proxy_support | HTTP-Proxy]] support for myApps. Now, myApps follows by default the OS-settings regarding HTTP-Proxy. This might affect existing setups when updating from 13r2 to 13r3. We recommend to check before a 13r3 update if an HTTP-Proxy is used and if so, test before the update for interop problems between myApps and the used HTTP-Proxy.&lt;br /&gt;
&lt;br /&gt;
===Physical Location===&lt;br /&gt;
The Softphone App supports in 13r3 the determination of the Physical Location. Similar to an IP-Phone, this is determined automatically based on HTTP-Redirects of the myApps PBX-login process. If you use PBX-objects with activated &amp;quot;Local&amp;quot; option (often this is a Trunk Line object), the determined physical location might lead to a different behavior when calling these objects. If this leads to unwanted call flows, you can either adjust the initial myApps registration PBX or configure the Physical location manually at the Softphone.&lt;br /&gt;
&lt;br /&gt;
== Application Platform and its applications ==&lt;br /&gt;
===App Platform image===&lt;br /&gt;
&lt;br /&gt;
It is not mandatory but recommended to [[Reference13r3:Concept_App_Platform#Update_of_the_App_Platform_itself | update the App Platform image]] to the latest version to receive a newer kernel and updated Linux packages.&lt;br /&gt;
&lt;br /&gt;
===Recordings App===&lt;br /&gt;
Please follow the procedure described in the [[Reference13r3:Concept_App_Service_Recordings#Upgrade_from_V13r2_to_V13r3_Recordings_App | Recordings App concept article]].&lt;br /&gt;
&lt;br /&gt;
===Reports App===&lt;br /&gt;
The Reports App will improve missed calls queries by adding a new database index during the first start after an update. Depending on the size of the reporting database, this database adjustment can take some minutes and results also in high CPU-load and missed CDRs during that time.&lt;br /&gt;
&lt;br /&gt;
=== App Service Queues, Switchboard App ===&lt;br /&gt;
To allow monitoring of all queues by all switchboard users, configure a group (e.g. with the name &#039;&#039;queues&#039;&#039;) in the PBX and assign it as &#039;&#039;&#039;Static&#039;&#039;&#039; to all Waiting Queues used by the Switchboard App and assign it also as &#039;&#039;&#039;Static&#039;&#039;&#039; and &#039;&#039;&#039;Active&#039;&#039;&#039; to all Switchboard Users.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Apps new in 13r3===&lt;br /&gt;
New Apps will not be installed automatically by the 13r2 to 13r3 upgrade. The installation description of new 13r3 apps is usually in the concept article. New apps are:&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_kuando®#Configuration | Connector for kuando®]]&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_Microsoft_365 | innovaphone myApps Connector for Microsoft 365]]&lt;br /&gt;
&lt;br /&gt;
== Changes visible to end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 13r3 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
===Rework of Phone &amp;amp; Softphone UI===&lt;br /&gt;
Several feature and UI improvements, see &#039;Features&#039; in [[Reference13r3:Concept_App_SoftphoneApp#Features | Reference13r3:Concept App SoftphoneApp ]] and [[Reference13r3:Concept Multi-Video-Conference]].&lt;br /&gt;
&lt;br /&gt;
===CallForwarding in Profile App===&lt;br /&gt;
Added configuration option on call diversions: call forwardings depending on &#039;&#039;myApps online&#039;&#039; and &#039;&#039;Presence&#039;&#039; state. This can be switched on or off by the user in the Profile App.&lt;br /&gt;
&lt;br /&gt;
===Focus App===&lt;br /&gt;
The &amp;quot;App focus&amp;quot; can be used to define a default app for the user. It is started and shown automatically when myApps is loaded. When closing other apps, the app is shown instead of the home screen. Users can activate (default) or deactivate the Focus function in their myApps Client settings (hamburger menu). See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
===Pin Apps===&lt;br /&gt;
Apps can be pinned to the main window. Pinned apps are always running and can&#039;t be closed. They are also started automatically when the myApps client is loaded. This setting is locally stored per-client. So you can pin different apps on your computer and your smartphone.  See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
The [[Reference13r3:Concept_App_Service_Fax#Mail_Configuration | Mail Configuration]] section of the Fax App offers in 13r3 additional options:&lt;br /&gt;
* Transmission confirmations&lt;br /&gt;
* Transmission reports for outgoing fax jobs as PDF&lt;br /&gt;
* Error notifications for outgoing fax jobs&lt;br /&gt;
&lt;br /&gt;
==Hardware Restrictions==&lt;br /&gt;
For a list of devices with no/restricted support in 13r3, see the [[Howto:Firmware_Upgrade#Version_13r3 | Firmware Upgrade article]].&lt;br /&gt;
&lt;br /&gt;
==Known Problems==&lt;br /&gt;
&lt;br /&gt;
===Boolean App===&lt;br /&gt;
Following the update to 13r3, it is not possible to edit Boolean Apps using the myApps client (except when using the myApps client in a web browser). To resolve this issue, you will need to delete the approxy folder for all users who use the boolean app. You can locate this folder in the following directory: %USERPROFILE%\AppData\Local\innovaphone\myApps.&lt;br /&gt;
Reload or restart myApps afterwards.&lt;br /&gt;
&lt;br /&gt;
This behavior can also occur under Mac OS. Here the problem can be solved by uninstalling the app and then reinstalling it again.&lt;br /&gt;
&lt;br /&gt;
===Current major issues that will be fixed with upcoming 13r3SR1 release===&lt;br /&gt;
* [[Support:PBX_13r3_final_trap_with_Unknown_Registrations | PBX 13r3 Final trap with Unknown Registrations]]&lt;br /&gt;
* [[Support:13r3final_App_Platform_-_SMTP_delivery_may_fail_due_to_IPv6_DNS_results | 13r3final App Platform - SMTP delivery may fail due to IPv6 DNS results]]&lt;br /&gt;
* [[Support:13r3final PBX randomly does not execute CFU | 13r3final PBX randomly does not execute CFU]]&lt;br /&gt;
&lt;br /&gt;
More info on other 13r3 SR1 changes can be found in the [[Reference13r3:Release_Notes_Firmware#13r3_Service_Release_1 | Release Notes]].&lt;br /&gt;
&lt;br /&gt;
===Regex Expression===&lt;br /&gt;
We updated the regular expression syntax which is used for the AD replication. A &#039;\&#039; followed by a non-special character is no longer allowed.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Technical_data_and_recommended_number_of_users_supported | the specs ]] will run on all supported hardware.  However, unusual configurations may not.  It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade.  Please find details in [[Reference:Device Health Check]].&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 13r3 release will consume the same amount of RAM compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory ===&lt;br /&gt;
As a rough rule of thumb, a v13r3 release will consume ~ 0.5 MB flash more compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v13r3.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file.&lt;br /&gt;
&lt;br /&gt;
=== Conferences ===&lt;br /&gt;
Since Conferences now use [[Reference13r3:Concept_Multi-Video-Conference | multiple video streams]] to display each conference participant (in 13r1 &amp;amp; 13r2 only the video stream of the speaker was shown), the number of concurrent video streams used in a single conference increased. Please review this [[Reference13r3:Concept_Multi-Video-Conference#Bandwidth_Consideration | bandwidth considerations]]. As a result, a device hosting a multivideo conference on its CONF or SCNF interface has a higher CPU load in 13r3 than in 13r2.&lt;br /&gt;
&lt;br /&gt;
[[Image:13r3_conference_bandwidth.png|700px|Estimated Conference bandwidth requirements]]&lt;br /&gt;
&lt;br /&gt;
The graph shows the bandwidth needed for a device running the CONF interface to participate in a conference. The values shown are for when all participants are in gallery mode (which is the worst case scenario) and in fullscreen presentation mode (which is the best case scenario). In general, the actual bandwidth needed will fall somewhere between these two extremes. &lt;br /&gt;
&lt;br /&gt;
To calculate the CPU requirements for the device, you can use the following formula: &amp;lt;code&amp;gt;CPU% = Bandwidth (in Mbps) / x&amp;lt;/code&amp;gt;, where x is&lt;br /&gt;
* 0.42 for a xx10 device &lt;br /&gt;
* 0.18 for IP311 and IP411 devices&lt;br /&gt;
* 0.56 for a xx11 device&lt;br /&gt;
* 3.6 for a xx13 device &lt;br /&gt;
&lt;br /&gt;
For example, if you are hosting a conference with 10 participants on a xx11 device in gallery mode, the upstream and downstream bandwidth would be 25 Mbps. Using the formula, you can calculate the CPU requirements as follows: CPU% = 25 Mbps / 0.56 = 44.64%. This means that the device should have at least 45% free CPU capacity to handle the conference.&lt;br /&gt;
&lt;br /&gt;
From the client&#039;s perspective, the worst case values for upstream bandwidth (when presenting) would be 1 Mbps, and for downstream bandwidth (when in a gallery mode conference with 20 participants) would be 5 Mbps.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
*[[Howto:Firmware_Upgrade]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V11r2 V12r1]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V12r1 V12r2]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V12r2 V13r1]]&lt;br /&gt;
&lt;br /&gt;
*[[Support:PBX_V13r3_Final_trap_with_Unkown_Registrations]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=71078</id>
		<title>Howto14r1:Firmware Upgrade V13r3 V14r1</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=71078"/>
		<updated>2024-03-05T14:54:35Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 14r1 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 14r1, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
== Licenses ==&lt;br /&gt;
If the system is licensed on premise, you&#039;ll need to regenerate the license file for V14 in https://portal.innovaphone.com/ (The system needs to have the SSC up to date).&lt;br /&gt;
&lt;br /&gt;
In case of cloud or rental model, don&#039;t worry about licenses.&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 14r1.&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 14r1 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend upgrading the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend reviewing all the configuration changes described below &#039;&#039;&#039;before&#039;&#039;&#039; you begin the update.&lt;br /&gt;
&lt;br /&gt;
== Changes visible to the end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 14r1 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
=== Softphone/Phone App UI changes === &lt;br /&gt;
* Dial-pad is now a new tab in the navigation.&lt;br /&gt;
* On Smartphones, the Navigation is in the bottom.&lt;br /&gt;
* Call button is removed from the searchbar. Calling only via the search results.&lt;br /&gt;
=== Configuration of Logo URI ===&lt;br /&gt;
* In 13r3 this configuration was done in the advanced UI on the page PBX / Config / myPBX / Logo URI.&lt;br /&gt;
* But in 14r1 it can be found on the page PBX / Config / General / Logo URL.&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
Extra features for the users:&lt;br /&gt;
* Call the voicemailbox directly from the app.&lt;br /&gt;
* PIN-code can be checked (hidden by default; visible with a click) and changed/set back to default.&lt;br /&gt;
* Call Forwards to the Voicemailbox can be activated/removed (CFU/CFB/CFNR).&lt;br /&gt;
* Number Resolution via the Search Provider.&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
* While sending an outgoing fax via the fax app, you now can select and configure a fax cover page before sending.&lt;br /&gt;
* While configuring a fax app or groupfax via the PBX Manager plugin, you can customize the header line of fax pages and select a language.&lt;br /&gt;
* After updating from 13r3 or setting up your device with 14r1, the Fax object has 4 new options, which are enabled by default:&lt;br /&gt;
** Modem capability: the supported modem class can be changed if necessary.&lt;br /&gt;
** Append user number: if checked, the user number will be appended to the object number.&lt;br /&gt;
** ECM: that allows the T.30 connection to use error correction mode.&lt;br /&gt;
** Receiving with 400dpi allowed: which allows you to receive 400*400dpi documents.&lt;br /&gt;
===AP Manager===&lt;br /&gt;
* The AP Manager UI has been reworked. It is now responsive design, improved view of all app services and instance. Rework of statistic of CPU/RAM/used disk. This change is for the IT administrator, not relevant for end users&lt;br /&gt;
&lt;br /&gt;
== Changed Apps ==&lt;br /&gt;
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Devices App ===&lt;br /&gt;
New Device Configurations option to roll out certificates to the trust list of your devices. [[Reference14r1:Concept_App_Service_Devices#Certificates_configuration]]&lt;br /&gt;
&lt;br /&gt;
=== Recordings App ===&lt;br /&gt;
New option to add WebDav credentials in RecordingsAdmin. [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]&lt;br /&gt;
&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
* New Setting to configure the automatic deletion of old(er) voicemail-messages per app. [[Reference14r1:Concept_App_Service_Voicemail#Settings]]&lt;br /&gt;
* New Option to configure the default PIN per voicemail system. [[Reference14r1:Concept_App_Service_Voicemail#add_voicemail]]&lt;br /&gt;
: By configuring a PIN code from a different length, you also configure the length of the PIN code used by the system.&lt;br /&gt;
&lt;br /&gt;
== New Apps ==&lt;br /&gt;
New Apps will not be installed automatically by the 13r3 to 14r1 upgrade. The installation description of new 14r1 apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.&lt;br /&gt;
&lt;br /&gt;
=== Calculator ===&lt;br /&gt;
*Although already released in 13r3 sr11, this app is now part of the 14r1 install. This app is explained in [[Reference13r3:Concept_App_Service_Calculator_App | the concept article]] and [[Howto14r1:Set_up_the_calculator_app| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connect ===&lt;br /&gt;
* A microblogging tool. This app is explained in [[Reference14r1:Concept_App_Service_Messages | the concept article]] and [[Howto14r1:Set_up_Connect| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connector for Let&#039;s Encrypt ===&lt;br /&gt;
* Automatically creates &amp;amp; renews Let&#039;s Encrypt certificates, the App is included in the Install process - however when doing an upgrade it needs to be [[Reference14r1:Concept_Let%27s_Encrypt#Configuration | setup manually]].&lt;br /&gt;
&lt;br /&gt;
=== Contact Widgets App ===&lt;br /&gt;
* A Contact Widget (or Website Widget) is an element that can be added to a website. It offers to website visitors a way to get in contact with agents (e.g. help-desk). Website visitors can start chat sessions (asking questions, getting answers) or can start voice or even video calls. &lt;br /&gt;
&lt;br /&gt;
For more details have a look at [[Reference14r1:Concept Contact Widgets | the concept article]].&lt;br /&gt;
&lt;br /&gt;
Customers using the previous Widgets, should change to the new [[Howto14r1:Firmware_Upgrade_V13r3_V14r1#Widgets | Contact Widgets App ]]&lt;br /&gt;
&lt;br /&gt;
===Notes===&lt;br /&gt;
*Digital notes can be managed with the innovaphone app Notes. The app has a minimalistic feature set and is easy to use. The notes are saved on the server and available on all devices of the users. More infos available in the [[Reference14r1:Concept_App_Service_Notes_App | Reference article]]&lt;br /&gt;
&lt;br /&gt;
===PBX Manager - AP app installer===&lt;br /&gt;
*in the PBX manager you will find a new coloured plugin. this new plugin give access to the App store in order to ease the installation of an App service and its instance. You basically do not need to go to the AP platform when you want to install a new application. Idea is to have the further installed app done by this plugin, this also ease the way to discover new applications. More infos available in the [[Reference14r1:Concept_App_Platform#App_Installer_PBX_Manager_Plugin | Reference article]]&lt;br /&gt;
&lt;br /&gt;
=== Search App ===&lt;br /&gt;
* The app is immediately available on the PBX (no configuration is needed). In a new V14r1 configuration the Install provides all Users with this Search App via the &amp;quot;Config User&amp;quot;-Template. If the same configuration is required on an upgraded config, the Search App (&amp;quot;search&amp;quot;) can be ticked in the &amp;quot;Config User&amp;quot; template. For details refer to [[Reference14r1:Concept_App_Search | the concept article]].&lt;br /&gt;
&lt;br /&gt;
=== TechAssist ===&lt;br /&gt;
* Application for quality assurance and improvement of systems by collecting static and runtime information. For details refer to [[Reference14r1:Concept_App_Service_TechAssist | the concept article]].&lt;br /&gt;
&lt;br /&gt;
== Needed configuration changes ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== EchoCanceller of myApps Client for Windows ===&lt;br /&gt;
In 14r1 the Windows client uses by default a Windows provided EchoCanceller. To switch back to the default Echocanceller used in 13r3, create a Windows registry entry in Computer\HKEY_CURRENT_USER\Software\innovaphone\myApps with the following values:&lt;br /&gt;
 Type: DWORD (REG_DWORD)&lt;br /&gt;
 Name: webrtcEchoCanceller&lt;br /&gt;
 Value: 1&lt;br /&gt;
&lt;br /&gt;
If the 13r3 echo-canceller is used, the myApps trace of a call will contain a line &#039;&#039;[AC] echo canceller is WebRTC aec3&#039;&#039;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Virtual Appliance on VMWare ===&lt;br /&gt;
After deploying the new firmware modify the guest configuration file (stemming from ipva.vmx) for all network cards as such:&lt;br /&gt;
Modify e.g. &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vlance&amp;quot;&amp;lt;/code&amp;gt; to become &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vmxnet3&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== IPVA certificates ==&lt;br /&gt;
IPVA certificates are no longer signed by &#039;&#039;&#039;innovaphone Device Certification Authority 2&#039;&#039;&#039;.&lt;br /&gt;
Instead they will be now signed by &#039;&#039;&#039;innovaphone Unverified Device CA&#039;&#039;&#039;, as innovaphone cannot control the serial numbers and thus the certificate creation of IPVAs.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In a 14r1 install you&#039;ll be asked whether you want to always trust this new CA or not. If you decide not to trust this CA, you have to manually trust newly created IPVA certificates.&amp;lt;br/&amp;gt;&lt;br /&gt;
Note that this is not neccessary for local registrations inside the IPVA itself and doesn&#039;t affect hardware phone registrations.&lt;br /&gt;
&lt;br /&gt;
You can download the innovaphone Unverified Device CA here: https://download.innovaphone.com/certificates/ca-unverified.pem &amp;lt;br/&amp;gt;&lt;br /&gt;
If you want to trust this new CA or your own IPVA certificates, you can use the Devices App to roll out certificates to the trust list of your devices.&lt;br /&gt;
&lt;br /&gt;
== Removed in 14r1 ==&lt;br /&gt;
The following software is no longer included in 14r1.&lt;br /&gt;
=== myPBX ===&lt;br /&gt;
This includes the following components&lt;br /&gt;
* myPBX webclient&lt;br /&gt;
* myPBX for Windows&lt;br /&gt;
* myPBX for iOS&lt;br /&gt;
* myPBX for Android&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Widgets===&lt;br /&gt;
The Widgets were based on the myPBX interfaces that have been removed. Please migrate to the [[Reference14r1:Concept Contact Widgets | the Contacts Widget App]].&lt;br /&gt;
&lt;br /&gt;
===WebRTC toolkit===&lt;br /&gt;
The WebRTC toolkit was based on the myPBX interfaces that have been removed.&lt;br /&gt;
Please use the current interfaces and libraries described in the &#039;&#039;&#039;[https://sdk.innovaphone.com innovaphone SDK]&#039;&#039;&#039;.&lt;br /&gt;
=== Windows Softwarephone ===&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps for Windows&#039;&#039;&#039; and the &#039;&#039;&#039;Softphone App&#039;&#039;&#039;.&lt;br /&gt;
===PBX Object Settings ===&lt;br /&gt;
The object provided the PBX Settings App that was used to configure dynamic group memberships in myPBX.&lt;br /&gt;
Please use the &#039;&#039;&#039;Profile App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
===PBX Object ICP ===&lt;br /&gt;
Please use the integrated presence features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
===Service Call-Lists ===&lt;br /&gt;
This service implemented call lists for myPBX on the local CF card.&lt;br /&gt;
Please use the &#039;&#039;&#039;Reports App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
== Deprecated in 14r1 ==&lt;br /&gt;
The following software is based on legacy technology with no further development and limited maintenance and support.&lt;br /&gt;
We strongly recommend migrating to our successor products that are fully compatible with 14r1 and myApps technology.&lt;br /&gt;
&lt;br /&gt;
=== Linux Application Platform (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;innovaphone App Platform&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
&lt;br /&gt;
=== innovaphone Faxserver (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Fax App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Reporting (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Reports App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Exchange (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Calendar App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== Operator (v9) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Switchboard App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Voice Recording 2014 ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Recordings App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== PBX Object External UC ===&lt;br /&gt;
Existing configurations still work. But new configurations can&#039;t be done using the advanced UI anymore.&lt;br /&gt;
&lt;br /&gt;
Please use the integrated &#039;&#039;&#039;UC&#039;&#039;&#039; and &#039;&#039;&#039;federation&#039;&#039;&#039; features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For presence synchronization with other systems we recommend using&lt;br /&gt;
* &#039;&#039;&#039;innovaphone myApps Connector for Microsoft 365&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Connector for kuando®&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Calendar App&#039;&#039;&#039;&lt;br /&gt;
==Known Problems==&lt;br /&gt;
===Long Update-duration===&lt;br /&gt;
When you update, it can be up to 10 minutes before you have access to your app platform again.&lt;br /&gt;
===Fax from 14r1 to 13r3 App===&lt;br /&gt;
14r1 faxes are sent with 400dpi by default, which the 13r3 app doesn&#039;t support and you will see a [[Reference14r1:Concept_App_Service_Fax#Known_Issues|non working incoming fax]]. The second try with lower resolution will work.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 14r1 release will consume the same amount of RAM compared to a v13r3 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory  ===&lt;br /&gt;
As a rough rule of thumb, a v14r1 release will consume ~ 1.8 MB more flash memory compared to a v13r3 firmware.&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v14r1.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 13r3 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 13r3, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 13r2.  For hints on upgrading a system to 13r2 see [[Howto:V13_Firmware_Upgrade_V13r1_V13r2]].&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 13r3 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend to upgrade the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend to review all the configuration changes described below before you begin the update.&lt;br /&gt;
&lt;br /&gt;
== Configuration Changes ==&lt;br /&gt;
In 13r3 we have introduced some new features which are automatically configured if you use the installer to setup your new 13r3 from scratch. If you upgrade an existing installation, you have to configure the following settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Default SRTP key exchange value in device configuration of Phones/Interfaces ===&lt;br /&gt;
Before v13r3, the default value for SRTP key exchange was SDES-DTLS - with v13r3 it changes to the more secure DTLS-SDES. Therefore innovaphone devices now use DTLS instead - if the called endpoint has this preference. To make sure the more secure key exchange is used, we recommend adjusting the &#039;&#039;SRTP key exchange setting&#039;&#039; in the Devices App, &#039;&#039;Device Configuration&#039;&#039; for &#039;&#039;[Phone]&#039;&#039; and &#039;&#039;[Analog phone/fax]&#039;&#039;. An exception to this recommendation is if you are using old phone models (IP110A, IP240A) or gateway models (IP24, IP22) in your setup - as these may have CPU performance issues in the connection setup phase. In that case, use &#039;&#039;&#039;SDES-DTLS&#039;&#039;&#039; as value for the &#039;&#039;SRTP key exchange&#039;&#039; for all devices, not only for the old phone models.&lt;br /&gt;
&lt;br /&gt;
===Group Fax===&lt;br /&gt;
The fax object has to be configured as external resource of a group fax object in 13r3. It is therefore &#039;&#039;&#039;mandatory&#039;&#039;&#039; to assign the fax object as an external resource to all group fax objects after the upgrade - via PBX Manager .&lt;br /&gt;
&lt;br /&gt;
In the Advanced UI, you have to enter the h323/sip name of the fax object in the field &#039;&#039;&#039;External Resource Destination&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Also, with 13r3, group faxes can have their own international fax number and company name, so you should fill in these fields, or else the fax header will be empty.&lt;br /&gt;
&lt;br /&gt;
===Contacts App | User drop-down menu for sharing address books===&lt;br /&gt;
With 13r3, personal address books can be created and shared with users/groups. To have a search and drop-down menu in the sharing step, you have to activate the &amp;quot;Admin&amp;quot; option at the &amp;quot;ContactsApi&amp;quot; app object (tab &amp;quot;App&amp;quot;) over the Advanced UI. Otherwise, no results will be shown, and you have to enter the correct h323 name of a user.&lt;br /&gt;
&lt;br /&gt;
===Improved Conference Rooms===&lt;br /&gt;
* The &#039;&#039;Web Access allowed&#039;&#039; checkbox in the conference app has to be set in order to access the Conference Web Access UI.&lt;br /&gt;
: To be able create HTTP links for external participants, the conferencing App is required.&lt;br /&gt;
* Update the [[Reference13r3:PBX/Objects/Conference/Announcement_types#Sample_Announcement_Files | announcements]] for your conference rooms, to include also the &#039;&#039;Web Access announcements&#039;&#039;. &lt;br /&gt;
* it is recommended to use a second Turn-Server listening on TCP port 443 as a fallback option for external conference participants, with local firewalls not allowing access to your standard Turn-server. Configure this second Turn-Server in [[Reference13r3:IP4/General/STUN#TURN_Extern | IP4/General/STUN -&amp;gt; Turn Extern]] [[User:Sga|Sga]] TBD: info zu inno Turn Fallback server&lt;br /&gt;
* 13r3 adds a search-API for the Conference Rooms, allowing users to search for Conference room names from their Phone, Softphone or RCC App. Each conference object provides its own search API which is named like &#039;&#039;&amp;lt;Name-of-conference-object&amp;gt;.search&#039;&#039; and access to it can be granted using the App-Section of a PBX-object. The PBX-Manager Plugin for Conferences offers also an option to add the rights for all conference rooms and their search-APIs to the Config-User and/or Config-Admin template.&lt;br /&gt;
&lt;br /&gt;
=== NTLM/OAuth===&lt;br /&gt;
13r3 introduces OAuth2 Windows Authentication for myApps. If your are currently using NTLM/Netlogon for authentication, you might want to consider upgrading it OAuth2, since this authentication mechanisms is more secure. See [[Reference13r3:Concept OAuth2 Windows Authentication]] for details. &lt;br /&gt;
In 13r3 only Microsoft AD FS is supported as OpenID Server.&lt;br /&gt;
&lt;br /&gt;
===HTTP-Proxy===&lt;br /&gt;
13r3 introduces [[Reference13r3:Concept_myApps_platform_services#HTTP_proxy_support | HTTP-Proxy]] support for myApps. Now, myApps follows by default the OS-settings regarding HTTP-Proxy. This might affect existing setups when updating from 13r2 to 13r3. We recommend to check before a 13r3 update if an HTTP-Proxy is used and if so, test before the update for interop problems between myApps and the used HTTP-Proxy.&lt;br /&gt;
&lt;br /&gt;
===Physical Location===&lt;br /&gt;
The Softphone App supports in 13r3 the determination of the Physical Location. Similar to an IP-Phone, this is determined automatically based on HTTP-Redirects of the myApps PBX-login process. If you use PBX-objects with activated &amp;quot;Local&amp;quot; option (often this is a Trunk Line object), the determined physical location might lead to a different behavior when calling these objects. If this leads to unwanted call flows, you can either adjust the initial myApps registration PBX or configure the Physical location manually at the Softphone.&lt;br /&gt;
&lt;br /&gt;
== Application Platform and its applications ==&lt;br /&gt;
===App Platform image===&lt;br /&gt;
&lt;br /&gt;
It is not mandatory but recommended to [[Reference13r3:Concept_App_Platform#Update_of_the_App_Platform_itself | update the App Platform image]] to the latest version to receive a newer kernel and updated Linux packages.&lt;br /&gt;
&lt;br /&gt;
===Recordings App===&lt;br /&gt;
Please follow the procedure described in the [[Reference13r3:Concept_App_Service_Recordings#Upgrade_from_V13r2_to_V13r3_Recordings_App | Recordings App concept article]].&lt;br /&gt;
&lt;br /&gt;
===Reports App===&lt;br /&gt;
The Reports App will improve missed calls queries by adding a new database index during the first start after an update. Depending on the size of the reporting database, this database adjustment can take some minutes and results also in high CPU-load and missed CDRs during that time.&lt;br /&gt;
&lt;br /&gt;
=== App Service Queues, Switchboard App ===&lt;br /&gt;
To allow monitoring of all queues by all switchboard users, configure a group (e.g. with the name &#039;&#039;queues&#039;&#039;) in the PBX and assign it as &#039;&#039;&#039;Static&#039;&#039;&#039; to all Waiting Queues used by the Switchboard App and assign it also as &#039;&#039;&#039;Static&#039;&#039;&#039; and &#039;&#039;&#039;Active&#039;&#039;&#039; to all Switchboard Users.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Apps new in 13r3===&lt;br /&gt;
New Apps will not be installed automatically by the 13r2 to 13r3 upgrade. The installation description of new 13r3 apps is usually in the concept article. New apps are:&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_kuando®#Configuration | Connector for kuando®]]&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_Microsoft_365 | innovaphone myApps Connector for Microsoft 365]]&lt;br /&gt;
&lt;br /&gt;
== Changes visible to end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 13r3 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
===Rework of Phone &amp;amp; Softphone UI===&lt;br /&gt;
Several feature and UI improvements, see &#039;Features&#039; in [[Reference13r3:Concept_App_SoftphoneApp#Features | Reference13r3:Concept App SoftphoneApp ]] and [[Reference13r3:Concept Multi-Video-Conference]].&lt;br /&gt;
&lt;br /&gt;
===CallForwarding in Profile App===&lt;br /&gt;
Added configuration option on call diversions: call forwardings depending on &#039;&#039;myApps online&#039;&#039; and &#039;&#039;Presence&#039;&#039; state. This can be switched on or off by the user in the Profile App.&lt;br /&gt;
&lt;br /&gt;
===Focus App===&lt;br /&gt;
The &amp;quot;App focus&amp;quot; can be used to define a default app for the user. It is started and shown automatically when myApps is loaded. When closing other apps, the app is shown instead of the home screen. Users can activate (default) or deactivate the Focus function in their myApps Client settings (hamburger menu). See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
===Pin Apps===&lt;br /&gt;
Apps can be pinned to the main window. Pinned apps are always running and can&#039;t be closed. They are also started automatically when the myApps client is loaded. This setting is locally stored per-client. So you can pin different apps on your computer and your smartphone.  See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
The [[Reference13r3:Concept_App_Service_Fax#Mail_Configuration | Mail Configuration]] section of the Fax App offers in 13r3 additional options:&lt;br /&gt;
* Transmission confirmations&lt;br /&gt;
* Transmission reports for outgoing fax jobs as PDF&lt;br /&gt;
* Error notifications for outgoing fax jobs&lt;br /&gt;
&lt;br /&gt;
==Hardware Restrictions==&lt;br /&gt;
For a list of devices with no/restricted support in 13r3, see the [[Howto:Firmware_Upgrade#Version_13r3 | Firmware Upgrade article]].&lt;br /&gt;
&lt;br /&gt;
==Known Problems==&lt;br /&gt;
&lt;br /&gt;
===Boolean App===&lt;br /&gt;
Following the update to 13r3, it is not possible to edit Boolean Apps using the myApps client (except when using the myApps client in a web browser). To resolve this issue, you will need to delete the approxy folder for all users who use the boolean app. You can locate this folder in the following directory: %USERPROFILE%\AppData\Local\innovaphone\myApps.&lt;br /&gt;
Reload or restart myApps afterwards.&lt;br /&gt;
&lt;br /&gt;
This behavior can also occur under Mac OS. Here the problem can be solved by uninstalling the app and then reinstalling it again.&lt;br /&gt;
&lt;br /&gt;
===Current major issues that will be fixed with upcoming 13r3SR1 release===&lt;br /&gt;
* [[Support:PBX_13r3_final_trap_with_Unknown_Registrations | PBX 13r3 Final trap with Unknown Registrations]]&lt;br /&gt;
* [[Support:13r3final_App_Platform_-_SMTP_delivery_may_fail_due_to_IPv6_DNS_results | 13r3final App Platform - SMTP delivery may fail due to IPv6 DNS results]]&lt;br /&gt;
* [[Support:13r3final PBX randomly does not execute CFU | 13r3final PBX randomly does not execute CFU]]&lt;br /&gt;
&lt;br /&gt;
More info on other 13r3 SR1 changes can be found in the [[Reference13r3:Release_Notes_Firmware#13r3_Service_Release_1 | Release Notes]].&lt;br /&gt;
&lt;br /&gt;
===Regex Expression===&lt;br /&gt;
We updated the regular expression syntax which is used for the AD replication. A &#039;\&#039; followed by a non-special character is no longer allowed.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Technical_data_and_recommended_number_of_users_supported | the specs ]] will run on all supported hardware.  However, unusual configurations may not.  It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade.  Please find details in [[Reference:Device Health Check]].&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 13r3 release will consume the same amount of RAM compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory ===&lt;br /&gt;
As a rough rule of thumb, a v13r3 release will consume ~ 0.5 MB flash more compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v13r3.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file.&lt;br /&gt;
&lt;br /&gt;
=== Conferences ===&lt;br /&gt;
Since Conferences now use [[Reference13r3:Concept_Multi-Video-Conference | multiple video streams]] to display each conference participant (in 13r1 &amp;amp; 13r2 only the video stream of the speaker was shown), the number of concurrent video streams used in a single conference increased. Please review this [[Reference13r3:Concept_Multi-Video-Conference#Bandwidth_Consideration | bandwidth considerations]]. As a result, a device hosting a multivideo conference on its CONF or SCNF interface has a higher CPU load in 13r3 than in 13r2.&lt;br /&gt;
&lt;br /&gt;
[[Image:13r3_conference_bandwidth.png|700px|Estimated Conference bandwidth requirements]]&lt;br /&gt;
&lt;br /&gt;
The graph shows the bandwidth needed for a device running the CONF interface to participate in a conference. The values shown are for when all participants are in gallery mode (which is the worst case scenario) and in fullscreen presentation mode (which is the best case scenario). In general, the actual bandwidth needed will fall somewhere between these two extremes. &lt;br /&gt;
&lt;br /&gt;
To calculate the CPU requirements for the device, you can use the following formula: &amp;lt;code&amp;gt;CPU% = Bandwidth (in Mbps) / x&amp;lt;/code&amp;gt;, where x is&lt;br /&gt;
* 0.42 for a xx10 device &lt;br /&gt;
* 0.18 for IP311 and IP411 devices&lt;br /&gt;
* 0.56 for a xx11 device&lt;br /&gt;
* 3.6 for a xx13 device &lt;br /&gt;
&lt;br /&gt;
For example, if you are hosting a conference with 10 participants on a xx11 device in gallery mode, the upstream and downstream bandwidth would be 25 Mbps. Using the formula, you can calculate the CPU requirements as follows: CPU% = 25 Mbps / 0.56 = 44.64%. This means that the device should have at least 45% free CPU capacity to handle the conference.&lt;br /&gt;
&lt;br /&gt;
From the client&#039;s perspective, the worst case values for upstream bandwidth (when presenting) would be 1 Mbps, and for downstream bandwidth (when in a gallery mode conference with 20 participants) would be 5 Mbps.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
*[[Howto:Firmware_Upgrade]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V11r2 V12r1]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V12r1 V12r2]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V12r2 V13r1]]&lt;br /&gt;
&lt;br /&gt;
*[[Support:PBX_V13r3_Final_trap_with_Unkown_Registrations]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=71077</id>
		<title>Howto14r1:Firmware Upgrade V13r3 V14r1</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto14r1:Firmware_Upgrade_V13r3_V14r1&amp;diff=71077"/>
		<updated>2024-03-05T14:52:14Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 14r1 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 14r1, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
== Licenses ==&lt;br /&gt;
If the system is licensed on premise, you&#039;ll need to regenerate the license file for V14 in https://portal.innovaphone.com/ (The system needs to have the SSC up to date).&lt;br /&gt;
In case of cloud or rental model, don&#039;t worry about licenses.&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 14r1.&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 14r1 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend upgrading the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend reviewing all the configuration changes described below &#039;&#039;&#039;before&#039;&#039;&#039; you begin the update.&lt;br /&gt;
&lt;br /&gt;
== Changes visible to the end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 14r1 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
=== Softphone/Phone App UI changes === &lt;br /&gt;
* Dial-pad is now a new tab in the navigation.&lt;br /&gt;
* On Smartphones, the Navigation is in the bottom.&lt;br /&gt;
* Call button is removed from the searchbar. Calling only via the search results.&lt;br /&gt;
=== Configuration of Logo URI ===&lt;br /&gt;
* In 13r3 this configuration was done in the advanced UI on the page PBX / Config / myPBX / Logo URI.&lt;br /&gt;
* But in 14r1 it can be found on the page PBX / Config / General / Logo URL.&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
Extra features for the users:&lt;br /&gt;
* Call the voicemailbox directly from the app.&lt;br /&gt;
* PIN-code can be checked (hidden by default; visible with a click) and changed/set back to default.&lt;br /&gt;
* Call Forwards to the Voicemailbox can be activated/removed (CFU/CFB/CFNR).&lt;br /&gt;
* Number Resolution via the Search Provider.&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
* While sending an outgoing fax via the fax app, you now can select and configure a fax cover page before sending.&lt;br /&gt;
* While configuring a fax app or groupfax via the PBX Manager plugin, you can customize the header line of fax pages and select a language.&lt;br /&gt;
* After updating from 13r3 or setting up your device with 14r1, the Fax object has 4 new options, which are enabled by default:&lt;br /&gt;
** Modem capability: the supported modem class can be changed if necessary.&lt;br /&gt;
** Append user number: if checked, the user number will be appended to the object number.&lt;br /&gt;
** ECM: that allows the T.30 connection to use error correction mode.&lt;br /&gt;
** Receiving with 400dpi allowed: which allows you to receive 400*400dpi documents.&lt;br /&gt;
===AP Manager===&lt;br /&gt;
* The AP Manager UI has been reworked. It is now responsive design, improved view of all app services and instance. Rework of statistic of CPU/RAM/used disk. This change is for the IT administrator, not relevant for end users&lt;br /&gt;
&lt;br /&gt;
== Changed Apps ==&lt;br /&gt;
If the installer is not used for a new installation, some new default settings are not set. Please evaluate per app whether you want to configure the new default settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Devices App ===&lt;br /&gt;
New Device Configurations option to roll out certificates to the trust list of your devices. [[Reference14r1:Concept_App_Service_Devices#Certificates_configuration]]&lt;br /&gt;
&lt;br /&gt;
=== Recordings App ===&lt;br /&gt;
New option to add WebDav credentials in RecordingsAdmin. [[Howto14r1:RecordingsApp#Configuring_WebDav_credentials_in_RecordingsAdmin]]&lt;br /&gt;
&lt;br /&gt;
=== Voicemail App ===&lt;br /&gt;
* New Setting to configure the automatic deletion of old(er) voicemail-messages per app. [[Reference14r1:Concept_App_Service_Voicemail#Settings]]&lt;br /&gt;
* New Option to configure the default PIN per voicemail system. [[Reference14r1:Concept_App_Service_Voicemail#add_voicemail]]&lt;br /&gt;
: By configuring a PIN code from a different length, you also configure the length of the PIN code used by the system.&lt;br /&gt;
&lt;br /&gt;
== New Apps ==&lt;br /&gt;
New Apps will not be installed automatically by the 13r3 to 14r1 upgrade. The installation description of new 14r1 apps is usually in the concept article. Please rate per app whether you want to install/use the new app and configure it manually.&lt;br /&gt;
&lt;br /&gt;
=== Calculator ===&lt;br /&gt;
*Although already released in 13r3 sr11, this app is now part of the 14r1 install. This app is explained in [[Reference13r3:Concept_App_Service_Calculator_App | the concept article]] and [[Howto14r1:Set_up_the_calculator_app| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connect ===&lt;br /&gt;
* A microblogging tool. This app is explained in [[Reference14r1:Concept_App_Service_Messages | the concept article]] and [[Howto14r1:Set_up_Connect| the how to article]].&lt;br /&gt;
&lt;br /&gt;
=== Connector for Let&#039;s Encrypt ===&lt;br /&gt;
* Automatically creates &amp;amp; renews Let&#039;s Encrypt certificates, the App is included in the Install process - however when doing an upgrade it needs to be [[Reference14r1:Concept_Let%27s_Encrypt#Configuration | setup manually]].&lt;br /&gt;
&lt;br /&gt;
=== Contact Widgets App ===&lt;br /&gt;
* A Contact Widget (or Website Widget) is an element that can be added to a website. It offers to website visitors a way to get in contact with agents (e.g. help-desk). Website visitors can start chat sessions (asking questions, getting answers) or can start voice or even video calls. &lt;br /&gt;
&lt;br /&gt;
For more details have a look at [[Reference14r1:Concept Contact Widgets | the concept article]].&lt;br /&gt;
&lt;br /&gt;
Customers using the previous Widgets, should change to the new [[Howto14r1:Firmware_Upgrade_V13r3_V14r1#Widgets | Contact Widgets App ]]&lt;br /&gt;
&lt;br /&gt;
===Notes===&lt;br /&gt;
*Digital notes can be managed with the innovaphone app Notes. The app has a minimalistic feature set and is easy to use. The notes are saved on the server and available on all devices of the users. More infos available in the [[Reference14r1:Concept_App_Service_Notes_App | Reference article]]&lt;br /&gt;
&lt;br /&gt;
===PBX Manager - AP app installer===&lt;br /&gt;
*in the PBX manager you will find a new coloured plugin. this new plugin give access to the App store in order to ease the installation of an App service and its instance. You basically do not need to go to the AP platform when you want to install a new application. Idea is to have the further installed app done by this plugin, this also ease the way to discover new applications. More infos available in the [[Reference14r1:Concept_App_Platform#App_Installer_PBX_Manager_Plugin | Reference article]]&lt;br /&gt;
&lt;br /&gt;
=== Search App ===&lt;br /&gt;
* The app is immediately available on the PBX (no configuration is needed). In a new V14r1 configuration the Install provides all Users with this Search App via the &amp;quot;Config User&amp;quot;-Template. If the same configuration is required on an upgraded config, the Search App (&amp;quot;search&amp;quot;) can be ticked in the &amp;quot;Config User&amp;quot; template. For details refer to [[Reference14r1:Concept_App_Search | the concept article]].&lt;br /&gt;
&lt;br /&gt;
=== TechAssist ===&lt;br /&gt;
* Application for quality assurance and improvement of systems by collecting static and runtime information. For details refer to [[Reference14r1:Concept_App_Service_TechAssist | the concept article]].&lt;br /&gt;
&lt;br /&gt;
== Needed configuration changes ==&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
=== EchoCanceller of myApps Client for Windows ===&lt;br /&gt;
In 14r1 the Windows client uses by default a Windows provided EchoCanceller. To switch back to the default Echocanceller used in 13r3, create a Windows registry entry in Computer\HKEY_CURRENT_USER\Software\innovaphone\myApps with the following values:&lt;br /&gt;
 Type: DWORD (REG_DWORD)&lt;br /&gt;
 Name: webrtcEchoCanceller&lt;br /&gt;
 Value: 1&lt;br /&gt;
&lt;br /&gt;
If the 13r3 echo-canceller is used, the myApps trace of a call will contain a line &#039;&#039;[AC] echo canceller is WebRTC aec3&#039;&#039;&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Virtual Appliance on VMWare ===&lt;br /&gt;
After deploying the new firmware modify the guest configuration file (stemming from ipva.vmx) for all network cards as such:&lt;br /&gt;
Modify e.g. &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vlance&amp;quot;&amp;lt;/code&amp;gt; to become &amp;lt;code&amp;gt;ethernet0.virtualDev = &amp;quot;vmxnet3&amp;quot;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== IPVA certificates ==&lt;br /&gt;
IPVA certificates are no longer signed by &#039;&#039;&#039;innovaphone Device Certification Authority 2&#039;&#039;&#039;.&lt;br /&gt;
Instead they will be now signed by &#039;&#039;&#039;innovaphone Unverified Device CA&#039;&#039;&#039;, as innovaphone cannot control the serial numbers and thus the certificate creation of IPVAs.&amp;lt;br/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
In a 14r1 install you&#039;ll be asked whether you want to always trust this new CA or not. If you decide not to trust this CA, you have to manually trust newly created IPVA certificates.&amp;lt;br/&amp;gt;&lt;br /&gt;
Note that this is not neccessary for local registrations inside the IPVA itself and doesn&#039;t affect hardware phone registrations.&lt;br /&gt;
&lt;br /&gt;
You can download the innovaphone Unverified Device CA here: https://download.innovaphone.com/certificates/ca-unverified.pem &amp;lt;br/&amp;gt;&lt;br /&gt;
If you want to trust this new CA or your own IPVA certificates, you can use the Devices App to roll out certificates to the trust list of your devices.&lt;br /&gt;
&lt;br /&gt;
== Removed in 14r1 ==&lt;br /&gt;
The following software is no longer included in 14r1.&lt;br /&gt;
=== myPBX ===&lt;br /&gt;
This includes the following components&lt;br /&gt;
* myPBX webclient&lt;br /&gt;
* myPBX for Windows&lt;br /&gt;
* myPBX for iOS&lt;br /&gt;
* myPBX for Android&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
===Widgets===&lt;br /&gt;
The Widgets were based on the myPBX interfaces that have been removed. Please migrate to the [[Reference14r1:Concept Contact Widgets | the Contacts Widget App]].&lt;br /&gt;
&lt;br /&gt;
===WebRTC toolkit===&lt;br /&gt;
The WebRTC toolkit was based on the myPBX interfaces that have been removed.&lt;br /&gt;
Please use the current interfaces and libraries described in the &#039;&#039;&#039;[https://sdk.innovaphone.com innovaphone SDK]&#039;&#039;&#039;.&lt;br /&gt;
=== Windows Softwarephone ===&lt;br /&gt;
Please migrate to &#039;&#039;&#039;innovaphone myApps for Windows&#039;&#039;&#039; and the &#039;&#039;&#039;Softphone App&#039;&#039;&#039;.&lt;br /&gt;
===PBX Object Settings ===&lt;br /&gt;
The object provided the PBX Settings App that was used to configure dynamic group memberships in myPBX.&lt;br /&gt;
Please use the &#039;&#039;&#039;Profile App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
===PBX Object ICP ===&lt;br /&gt;
Please use the integrated presence features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
===Service Call-Lists ===&lt;br /&gt;
This service implemented call lists for myPBX on the local CF card.&lt;br /&gt;
Please use the &#039;&#039;&#039;Reports App&#039;&#039;&#039; instead.&lt;br /&gt;
&lt;br /&gt;
== Deprecated in 14r1 ==&lt;br /&gt;
The following software is based on legacy technology with no further development and limited maintenance and support.&lt;br /&gt;
We strongly recommend migrating to our successor products that are fully compatible with 14r1 and myApps technology.&lt;br /&gt;
&lt;br /&gt;
=== Linux Application Platform (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;innovaphone App Platform&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
&lt;br /&gt;
=== innovaphone Faxserver (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Fax App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Reporting (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Reports App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Exchange (v10) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Calendar App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== Operator (v9) ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Switchboard App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== innovaphone Voice Recording 2014 ===&lt;br /&gt;
Please migrate to the &#039;&#039;&#039;Recordings App&#039;&#039;&#039; for 14r1 installations.&lt;br /&gt;
=== PBX Object External UC ===&lt;br /&gt;
Existing configurations still work. But new configurations can&#039;t be done using the advanced UI anymore.&lt;br /&gt;
&lt;br /&gt;
Please use the integrated &#039;&#039;&#039;UC&#039;&#039;&#039; and &#039;&#039;&#039;federation&#039;&#039;&#039; features of the &#039;&#039;&#039;innovaphone PBX&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
For presence synchronization with other systems we recommend using&lt;br /&gt;
* &#039;&#039;&#039;innovaphone myApps Connector for Microsoft 365&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Connector for kuando®&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Calendar App&#039;&#039;&#039;&lt;br /&gt;
==Known Problems==&lt;br /&gt;
===Long Update-duration===&lt;br /&gt;
When you update, it can be up to 10 minutes before you have access to your app platform again.&lt;br /&gt;
===Fax from 14r1 to 13r3 App===&lt;br /&gt;
14r1 faxes are sent with 400dpi by default, which the 13r3 app doesn&#039;t support and you will see a [[Reference14r1:Concept_App_Service_Fax#Known_Issues|non working incoming fax]]. The second try with lower resolution will work.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according the specs will run on all supported hardware. However, unusual configurations may not. It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade. Please find details in Reference:Device Health Check.&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 14r1 release will consume the same amount of RAM compared to a v13r3 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory  ===&lt;br /&gt;
As a rough rule of thumb, a v14r1 release will consume ~ 1.8 MB more flash memory compared to a v13r3 firmware.&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v14r1.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
== Applies To ==&lt;br /&gt;
This information applies to:&lt;br /&gt;
&lt;br /&gt;
* All 13r3 capable innovaphone devices&lt;br /&gt;
: For a general overview of the upgrade process and a list of supported devices with 13r3, see [[Howto:Firmware Upgrade]]&lt;br /&gt;
&lt;br /&gt;
== Migration Policy ==&lt;br /&gt;
Here is how you upgrade a system to 13r3 from 13r2.  For hints on upgrading a system to 13r2 see [[Howto:V13_Firmware_Upgrade_V13r1_V13r2]].&lt;br /&gt;
&lt;br /&gt;
=== Single AP/Single PBX===&lt;br /&gt;
* Create a new update job in devices and select 13r3 as major version&lt;br /&gt;
&lt;br /&gt;
===Shared AP/Several PBX&#039;es===&lt;br /&gt;
We generally recommend to upgrade the entire system (endpoints, PBXs, AP) in &#039;&#039;one shot&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
If this is not possible for any reason, the recommended sequence is:&lt;br /&gt;
# update the master PBX&lt;br /&gt;
# update the slave PBX and all its endpoints location by location&lt;br /&gt;
# update the App Platform to the latest build&lt;br /&gt;
# update all Apps&lt;br /&gt;
# perform the configuration changes described below&lt;br /&gt;
&lt;br /&gt;
Note that during the update time frame, some App data such as Reporting and Recording may be incomplete.&lt;br /&gt;
&lt;br /&gt;
We recommend to review all the configuration changes described below before you begin the update.&lt;br /&gt;
&lt;br /&gt;
== Configuration Changes ==&lt;br /&gt;
In 13r3 we have introduced some new features which are automatically configured if you use the installer to setup your new 13r3 from scratch. If you upgrade an existing installation, you have to configure the following settings manually.&lt;br /&gt;
&lt;br /&gt;
=== Default SRTP key exchange value in device configuration of Phones/Interfaces ===&lt;br /&gt;
Before v13r3, the default value for SRTP key exchange was SDES-DTLS - with v13r3 it changes to the more secure DTLS-SDES. Therefore innovaphone devices now use DTLS instead - if the called endpoint has this preference. To make sure the more secure key exchange is used, we recommend adjusting the &#039;&#039;SRTP key exchange setting&#039;&#039; in the Devices App, &#039;&#039;Device Configuration&#039;&#039; for &#039;&#039;[Phone]&#039;&#039; and &#039;&#039;[Analog phone/fax]&#039;&#039;. An exception to this recommendation is if you are using old phone models (IP110A, IP240A) or gateway models (IP24, IP22) in your setup - as these may have CPU performance issues in the connection setup phase. In that case, use &#039;&#039;&#039;SDES-DTLS&#039;&#039;&#039; as value for the &#039;&#039;SRTP key exchange&#039;&#039; for all devices, not only for the old phone models.&lt;br /&gt;
&lt;br /&gt;
===Group Fax===&lt;br /&gt;
The fax object has to be configured as external resource of a group fax object in 13r3. It is therefore &#039;&#039;&#039;mandatory&#039;&#039;&#039; to assign the fax object as an external resource to all group fax objects after the upgrade - via PBX Manager .&lt;br /&gt;
&lt;br /&gt;
In the Advanced UI, you have to enter the h323/sip name of the fax object in the field &#039;&#039;&#039;External Resource Destination&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
Also, with 13r3, group faxes can have their own international fax number and company name, so you should fill in these fields, or else the fax header will be empty.&lt;br /&gt;
&lt;br /&gt;
===Contacts App | User drop-down menu for sharing address books===&lt;br /&gt;
With 13r3, personal address books can be created and shared with users/groups. To have a search and drop-down menu in the sharing step, you have to activate the &amp;quot;Admin&amp;quot; option at the &amp;quot;ContactsApi&amp;quot; app object (tab &amp;quot;App&amp;quot;) over the Advanced UI. Otherwise, no results will be shown, and you have to enter the correct h323 name of a user.&lt;br /&gt;
&lt;br /&gt;
===Improved Conference Rooms===&lt;br /&gt;
* The &#039;&#039;Web Access allowed&#039;&#039; checkbox in the conference app has to be set in order to access the Conference Web Access UI.&lt;br /&gt;
: To be able create HTTP links for external participants, the conferencing App is required.&lt;br /&gt;
* Update the [[Reference13r3:PBX/Objects/Conference/Announcement_types#Sample_Announcement_Files | announcements]] for your conference rooms, to include also the &#039;&#039;Web Access announcements&#039;&#039;. &lt;br /&gt;
* it is recommended to use a second Turn-Server listening on TCP port 443 as a fallback option for external conference participants, with local firewalls not allowing access to your standard Turn-server. Configure this second Turn-Server in [[Reference13r3:IP4/General/STUN#TURN_Extern | IP4/General/STUN -&amp;gt; Turn Extern]] [[User:Sga|Sga]] TBD: info zu inno Turn Fallback server&lt;br /&gt;
* 13r3 adds a search-API for the Conference Rooms, allowing users to search for Conference room names from their Phone, Softphone or RCC App. Each conference object provides its own search API which is named like &#039;&#039;&amp;lt;Name-of-conference-object&amp;gt;.search&#039;&#039; and access to it can be granted using the App-Section of a PBX-object. The PBX-Manager Plugin for Conferences offers also an option to add the rights for all conference rooms and their search-APIs to the Config-User and/or Config-Admin template.&lt;br /&gt;
&lt;br /&gt;
=== NTLM/OAuth===&lt;br /&gt;
13r3 introduces OAuth2 Windows Authentication for myApps. If your are currently using NTLM/Netlogon for authentication, you might want to consider upgrading it OAuth2, since this authentication mechanisms is more secure. See [[Reference13r3:Concept OAuth2 Windows Authentication]] for details. &lt;br /&gt;
In 13r3 only Microsoft AD FS is supported as OpenID Server.&lt;br /&gt;
&lt;br /&gt;
===HTTP-Proxy===&lt;br /&gt;
13r3 introduces [[Reference13r3:Concept_myApps_platform_services#HTTP_proxy_support | HTTP-Proxy]] support for myApps. Now, myApps follows by default the OS-settings regarding HTTP-Proxy. This might affect existing setups when updating from 13r2 to 13r3. We recommend to check before a 13r3 update if an HTTP-Proxy is used and if so, test before the update for interop problems between myApps and the used HTTP-Proxy.&lt;br /&gt;
&lt;br /&gt;
===Physical Location===&lt;br /&gt;
The Softphone App supports in 13r3 the determination of the Physical Location. Similar to an IP-Phone, this is determined automatically based on HTTP-Redirects of the myApps PBX-login process. If you use PBX-objects with activated &amp;quot;Local&amp;quot; option (often this is a Trunk Line object), the determined physical location might lead to a different behavior when calling these objects. If this leads to unwanted call flows, you can either adjust the initial myApps registration PBX or configure the Physical location manually at the Softphone.&lt;br /&gt;
&lt;br /&gt;
== Application Platform and its applications ==&lt;br /&gt;
===App Platform image===&lt;br /&gt;
&lt;br /&gt;
It is not mandatory but recommended to [[Reference13r3:Concept_App_Platform#Update_of_the_App_Platform_itself | update the App Platform image]] to the latest version to receive a newer kernel and updated Linux packages.&lt;br /&gt;
&lt;br /&gt;
===Recordings App===&lt;br /&gt;
Please follow the procedure described in the [[Reference13r3:Concept_App_Service_Recordings#Upgrade_from_V13r2_to_V13r3_Recordings_App | Recordings App concept article]].&lt;br /&gt;
&lt;br /&gt;
===Reports App===&lt;br /&gt;
The Reports App will improve missed calls queries by adding a new database index during the first start after an update. Depending on the size of the reporting database, this database adjustment can take some minutes and results also in high CPU-load and missed CDRs during that time.&lt;br /&gt;
&lt;br /&gt;
=== App Service Queues, Switchboard App ===&lt;br /&gt;
To allow monitoring of all queues by all switchboard users, configure a group (e.g. with the name &#039;&#039;queues&#039;&#039;) in the PBX and assign it as &#039;&#039;&#039;Static&#039;&#039;&#039; to all Waiting Queues used by the Switchboard App and assign it also as &#039;&#039;&#039;Static&#039;&#039;&#039; and &#039;&#039;&#039;Active&#039;&#039;&#039; to all Switchboard Users.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Apps new in 13r3===&lt;br /&gt;
New Apps will not be installed automatically by the 13r2 to 13r3 upgrade. The installation description of new 13r3 apps is usually in the concept article. New apps are:&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_kuando®#Configuration | Connector for kuando®]]&lt;br /&gt;
* [[Reference13r3:Concept_App_Service_Connector_for_Microsoft_365 | innovaphone myApps Connector for Microsoft 365]]&lt;br /&gt;
&lt;br /&gt;
== Changes visible to end customers ==&lt;br /&gt;
Listed here are changes that should be communicated by resellers to end users prior to a 13r3 upgrade, as the change will be visible/audible in the behaviour of the application/device.&lt;br /&gt;
===Rework of Phone &amp;amp; Softphone UI===&lt;br /&gt;
Several feature and UI improvements, see &#039;Features&#039; in [[Reference13r3:Concept_App_SoftphoneApp#Features | Reference13r3:Concept App SoftphoneApp ]] and [[Reference13r3:Concept Multi-Video-Conference]].&lt;br /&gt;
&lt;br /&gt;
===CallForwarding in Profile App===&lt;br /&gt;
Added configuration option on call diversions: call forwardings depending on &#039;&#039;myApps online&#039;&#039; and &#039;&#039;Presence&#039;&#039; state. This can be switched on or off by the user in the Profile App.&lt;br /&gt;
&lt;br /&gt;
===Focus App===&lt;br /&gt;
The &amp;quot;App focus&amp;quot; can be used to define a default app for the user. It is started and shown automatically when myApps is loaded. When closing other apps, the app is shown instead of the home screen. Users can activate (default) or deactivate the Focus function in their myApps Client settings (hamburger menu). See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
===Pin Apps===&lt;br /&gt;
Apps can be pinned to the main window. Pinned apps are always running and can&#039;t be closed. They are also started automatically when the myApps client is loaded. This setting is locally stored per-client. So you can pin different apps on your computer and your smartphone.  See &#039;Features&#039; in [[Reference13r3:Concept_myApps#Features | Reference13r3:Concept myApps]]&lt;br /&gt;
&lt;br /&gt;
=== Fax App ===&lt;br /&gt;
The [[Reference13r3:Concept_App_Service_Fax#Mail_Configuration | Mail Configuration]] section of the Fax App offers in 13r3 additional options:&lt;br /&gt;
* Transmission confirmations&lt;br /&gt;
* Transmission reports for outgoing fax jobs as PDF&lt;br /&gt;
* Error notifications for outgoing fax jobs&lt;br /&gt;
&lt;br /&gt;
==Hardware Restrictions==&lt;br /&gt;
For a list of devices with no/restricted support in 13r3, see the [[Howto:Firmware_Upgrade#Version_13r3 | Firmware Upgrade article]].&lt;br /&gt;
&lt;br /&gt;
==Known Problems==&lt;br /&gt;
&lt;br /&gt;
===Boolean App===&lt;br /&gt;
Following the update to 13r3, it is not possible to edit Boolean Apps using the myApps client (except when using the myApps client in a web browser). To resolve this issue, you will need to delete the approxy folder for all users who use the boolean app. You can locate this folder in the following directory: %USERPROFILE%\AppData\Local\innovaphone\myApps.&lt;br /&gt;
Reload or restart myApps afterwards.&lt;br /&gt;
&lt;br /&gt;
This behavior can also occur under Mac OS. Here the problem can be solved by uninstalling the app and then reinstalling it again.&lt;br /&gt;
&lt;br /&gt;
===Current major issues that will be fixed with upcoming 13r3SR1 release===&lt;br /&gt;
* [[Support:PBX_13r3_final_trap_with_Unknown_Registrations | PBX 13r3 Final trap with Unknown Registrations]]&lt;br /&gt;
* [[Support:13r3final_App_Platform_-_SMTP_delivery_may_fail_due_to_IPv6_DNS_results | 13r3final App Platform - SMTP delivery may fail due to IPv6 DNS results]]&lt;br /&gt;
* [[Support:13r3final PBX randomly does not execute CFU | 13r3final PBX randomly does not execute CFU]]&lt;br /&gt;
&lt;br /&gt;
More info on other 13r3 SR1 changes can be found in the [[Reference13r3:Release_Notes_Firmware#13r3_Service_Release_1 | Release Notes]].&lt;br /&gt;
&lt;br /&gt;
===Regex Expression===&lt;br /&gt;
We updated the regular expression syntax which is used for the AD replication. A &#039;\&#039; followed by a non-special character is no longer allowed.&lt;br /&gt;
&lt;br /&gt;
== Resources Considerations ==&lt;br /&gt;
New firmware always has more features which in turn requires more resources. Growing firmware will thus consume both more flash and RAM for sure. A given system configuration will run flawlessly after a firmware largely only if there is still enough memory left after boot.&lt;br /&gt;
&lt;br /&gt;
Standard configurations which are according [[Howto:How_to_implement_large_PBXs#Technical_data_and_recommended_number_of_users_supported | the specs ]] will run on all supported hardware.  However, unusual configurations may not.  It is a good idea to examine both flash and RAM memory left on high load situations in your existing configuration to see if there is enough resources left for an upgrade.  Please find details in [[Reference:Device Health Check]].&lt;br /&gt;
&lt;br /&gt;
=== RAM ===&lt;br /&gt;
As a rough rule of thumb, a 13r3 release will consume the same amount of RAM compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
=== Flash Memory ===&lt;br /&gt;
As a rough rule of thumb, a v13r3 release will consume ~ 0.5 MB flash more compared to a v13r2 firmware.&lt;br /&gt;
&lt;br /&gt;
New firmware comes with new code for new features which consumes more flash memory for the firmware image. For this reason, devices may run out of flash memory during upgrade to v13r3.  Here is the recommended procedure for upgrade on such devices:&lt;br /&gt;
&lt;br /&gt;
* save entire configuration&lt;br /&gt;
* reset to factory defaults&lt;br /&gt;
* load saved configuration (this will reorganize the flash memory usage)&lt;br /&gt;
* upgrade to new firmware&lt;br /&gt;
&lt;br /&gt;
When there is still not enough flash memory available to store the new firmware (Web GUI ends up in a &#039;&#039;Firmwareupdate failed:no space&#039;&#039; / Update client end in a &#039;&#039;Error 0x00130001 Major FLASHMAN0 no space&#039;&#039; event) please open a support case with your current configuration file.&lt;br /&gt;
&lt;br /&gt;
=== Conferences ===&lt;br /&gt;
Since Conferences now use [[Reference13r3:Concept_Multi-Video-Conference | multiple video streams]] to display each conference participant (in 13r1 &amp;amp; 13r2 only the video stream of the speaker was shown), the number of concurrent video streams used in a single conference increased. Please review this [[Reference13r3:Concept_Multi-Video-Conference#Bandwidth_Consideration | bandwidth considerations]]. As a result, a device hosting a multivideo conference on its CONF or SCNF interface has a higher CPU load in 13r3 than in 13r2.&lt;br /&gt;
&lt;br /&gt;
[[Image:13r3_conference_bandwidth.png|700px|Estimated Conference bandwidth requirements]]&lt;br /&gt;
&lt;br /&gt;
The graph shows the bandwidth needed for a device running the CONF interface to participate in a conference. The values shown are for when all participants are in gallery mode (which is the worst case scenario) and in fullscreen presentation mode (which is the best case scenario). In general, the actual bandwidth needed will fall somewhere between these two extremes. &lt;br /&gt;
&lt;br /&gt;
To calculate the CPU requirements for the device, you can use the following formula: &amp;lt;code&amp;gt;CPU% = Bandwidth (in Mbps) / x&amp;lt;/code&amp;gt;, where x is&lt;br /&gt;
* 0.42 for a xx10 device &lt;br /&gt;
* 0.18 for IP311 and IP411 devices&lt;br /&gt;
* 0.56 for a xx11 device&lt;br /&gt;
* 3.6 for a xx13 device &lt;br /&gt;
&lt;br /&gt;
For example, if you are hosting a conference with 10 participants on a xx11 device in gallery mode, the upstream and downstream bandwidth would be 25 Mbps. Using the formula, you can calculate the CPU requirements as follows: CPU% = 25 Mbps / 0.56 = 44.64%. This means that the device should have at least 45% free CPU capacity to handle the conference.&lt;br /&gt;
&lt;br /&gt;
From the client&#039;s perspective, the worst case values for upstream bandwidth (when presenting) would be 1 Mbps, and for downstream bandwidth (when in a gallery mode conference with 20 participants) would be 5 Mbps.&lt;br /&gt;
&lt;br /&gt;
== Related Articles ==&lt;br /&gt;
*[[Howto:Firmware_Upgrade]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V11r2 V12r1]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V12r1 V12r2]]&lt;br /&gt;
* [[Howto:Firmware Upgrade V12r2 V13r1]]&lt;br /&gt;
&lt;br /&gt;
*[[Support:PBX_V13r3_Final_trap_with_Unkown_Registrations]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;br /&gt;
--&amp;gt;&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70633</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70633"/>
		<updated>2024-01-11T12:41:34Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Disclaimer */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- G.722 no --&amp;gt;&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
&amp;lt;!--  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
==Disclaimer==&lt;br /&gt;
Tests have been done in local, Both Fermax intercom pannel and Innovaphone PBX in same lan segment.&amp;lt;br&amp;gt;&lt;br /&gt;
In case of remote installations (use of Reverse Proxy), the video will be driven trought the fermax App&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70632</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70632"/>
		<updated>2024-01-11T12:40:47Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- G.722 no --&amp;gt;&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
&amp;lt;!--  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
==Disclaimer==&lt;br /&gt;
Tests have been done in local, Both Fermax intercom pannel and Innovaphone PBX in same lan segment.&lt;br /&gt;
&lt;br /&gt;
In case of remote installations (use of Reverse Proxy), the video will be driven trought the fermax App&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70631</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70631"/>
		<updated>2024-01-11T12:40:12Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- G.722 no --&amp;gt;&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
&amp;lt;!--  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
==Disclaimer==&lt;br /&gt;
Tests have been done in local, Both Fermax intercom pannel and Innovaphone PBX in same lan segment&lt;br /&gt;
In case of remote installations (use of Reverse Proxy), the video will be driven trought the fermax App&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70630</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70630"/>
		<updated>2024-01-11T12:34:25Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- G.722 no --&amp;gt;&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
&amp;lt;!--  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
==Disclaimer==&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70629</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70629"/>
		<updated>2024-01-11T11:27:27Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- G.722 no --&amp;gt;&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
&amp;lt;!--  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70628</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70628"/>
		<updated>2024-01-11T11:26:35Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- G.722 no --&amp;gt;&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
&amp;lt;!--  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70627</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70627"/>
		<updated>2024-01-11T11:20:57Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
  G.722 no&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70626</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70626"/>
		<updated>2024-01-11T11:19:55Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* DTMF Support */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
  G.722 no&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!--==DTMF Support== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--  RTP DTMF (inband)  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Supports RFC3261 Digest Authentication Scheme (Section 22.4) no  --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Support LDAP Phonebook no --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70625</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70625"/>
		<updated>2024-01-11T11:18:26Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Version */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
FERMAX is a leading video door phone manufacturer, based in Spain. We also manufacture Access Control. We do have a broad portfolio of connected outdoor panels, phones and video door phones that can solve any project with basic and advanced functionalities. FERMAX is a major player in IP video door phones integration. Always at the forefront of innovation.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
MEET IP is a FULL IP system SIP compatible. In this integration case it will be described how calls can be done from the outdoor intercom panel to a SIP Client registered in INNOVAPHONE SIP server or unified communication system.&lt;br /&gt;
&lt;br /&gt;
In offices and enterprises, it is common to connect the video door entry panel to the telephone switchboard in order to receive the call on a specific extension, simplifying the work of the employees. For this purpose, a telephone interface is used that connects the outdoor panel to an analogue input of the switchboard. With the evolution of PBXs, and their deployment in the cloud, a world of previously unimaginable advantages is now available, such as receiving the call on any extension located in different locations or even on a smartphone, and receiving video on the call, which is not available on an analogue telephone interface. You therefore have the same features as in a video door entry monitor if the terminal receiving the call has a screen: two-way conversation, visualisation of the visit and door unlock.  The Fermax outdoor panel has also evolved to adapt to this environment, and a clear example is the MEET panel, with IP technology, which supports SIP protocol, necessary in this type of integration. In this application, the outdoor panel must register in the SIP switchboard with a username and password and route calls to the required extension(s).   In the specific case of the Innovaphone SIP PBX, let&#039;s see how to configure the MEET outdoor panel and the Innovaphone PBX so that they can work together.  This document explains how to set up the Innovaphone PBX for any model (cloud, on premises, physical), as the user interface is practically the same, except for some slight differences.   Innovaphone provides a softphone in their My Apps application suite for desktop (Windows) that allows the implementation of a SIP client.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone CTI ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes&lt;br /&gt;
  Answer incoming call yes&lt;br /&gt;
  Hold/Retrieve no&lt;br /&gt;
  Transfer no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone Reverse Proxy ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==innovaphone WebRTC ready== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  Codec G.711 yes&lt;br /&gt;
  Codec OPUS no&lt;br /&gt;
  DTLS encryption no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
  G.722 no&lt;br /&gt;
  G.711 A-law yes&lt;br /&gt;
  G.711 y-law yes&lt;br /&gt;
  G.723.1 no&lt;br /&gt;
  G.729A no&lt;br /&gt;
  Opus no &lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
  RTP DTMF (inband)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 Supports RFC3261 Digest Authentication Scheme (Section 22.4) no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- ==Support LDAP Phonebook== --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 Support LDAP Phonebook no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
FERMAX MEET v3.0&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
innovaphone V13r3&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Required equipment===&lt;br /&gt;
Any Fermax MEET outdoor panel can be used for this integration, as all of them support SIP protocol. If you want to call a single extension, it is advisable to use the one-way MILO panel (a single push button). If you want to call different extensions to locate different people, you can use the MILO panel or, if an electronic directory is required, the KIN or MARINE panel. The outdoor panel may require a power supply if it does not support PoE, as well as the electric strike. To connect to the cloud version of the PBX, an internet connection with sufficient bandwidth (10Mbit minimum) will be required to access it. &lt;br /&gt;
&lt;br /&gt;
===Basic Scheme===&lt;br /&gt;
[[File:MEETWIRING.jpg|thumb|left|MEET IP INTERCOM]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Installation===&lt;br /&gt;
Once the outdoor panel is installed, it must be connected to a switch or directly to the installation&#039;s router. The connection of the electric lock release will be wired to the outdoor panel or, if maximum security is required, a reference 1490 module with 2 relays will be used to open the door from indoors, wiring the module to the panel using 3 wires (Cat-5 recommended). Finally, the panel is wired to the power supply.  It is possible to connect a MEET monitor to simultaneously receive the call inside the office, as a backup to the call through the PBX. &lt;br /&gt;
&lt;br /&gt;
===Innovaphone Configuration===&lt;br /&gt;
Innovaphone PABX MEET PANEL MEET PANEL  Once we have a PBX, either by means of a licence or a physical PBX, we must access to configure it through its web server using a browser: http://PBX_IP/admin.xml?xsl=admin.xsl &lt;br /&gt;
&lt;br /&gt;
1) First of all, &#039;config disable digest&#039; must be activated. To do this, go to Maintenance&amp;gt;Diagnostics&amp;gt;Command and enter the following commands: &lt;br /&gt;
[[File:1.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
They must be entered one after the other and the Command button must be pressed each time. &lt;br /&gt;
2) Next, a Gateway must be created to be able to display the video correctly on the Innovaphone softphone. If softphone is not used, this step is not necessary. In this example, the Gateway is assigned the number 2, which means that the calls to be routed through the Gateway must be prefixed with &lt;br /&gt;
&lt;br /&gt;
2. Option PBX&amp;gt;Objects&amp;gt;new user &lt;br /&gt;
&lt;br /&gt;
[[File:2.jpg|thumb|left|INNOVAPHONE 2]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:2b.jpg|thumb|left|INNOVAPHONE 2B]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must then be configured as follows: &lt;br /&gt;
&lt;br /&gt;
[[File:2c.jpg|thumb|left|INNOVAPHONE 2C]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
3) The devices are then added. Option PBX&amp;gt;Objects&amp;gt;new user&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   * For MEET outdoor panel&lt;br /&gt;
[[File:3a.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is important to assign an extension number (Number) and password for later configuration in the entrance panel. &lt;br /&gt;
&lt;br /&gt;
    * For the softphone&lt;br /&gt;
[[File:3b.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
You are also assigned an extension number and password.  A MEET monitor can be also integrated into the control unit as we did with the panel or left as a Meet device.  The devices that have been registered are checked: &lt;br /&gt;
&lt;br /&gt;
[[File:3c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Outdoor panel configuration===&lt;br /&gt;
&lt;br /&gt;
To configure the entrance panel, use a browser and access the IP address assigned to the entrance panel, by default 10.1.0.1 (building entrance panel) or 10.1.1.2 (single line panel) and enter the user admin and default password 123456.  The following steps will be followed:  &lt;br /&gt;
 &lt;br /&gt;
*  1) GENERAL CONFIGURATION&lt;br /&gt;
  a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W)&lt;br /&gt;
&lt;br /&gt;
   You must configure the panel as an Individual Panel, assign a block (default 1), a dwelling (default is 101), and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
&lt;br /&gt;
  In this example we have used a KIN building entrance panel. The panel must be configured as a Block Panel, assigned a block (default 1) and a panel number (default 1).  The Device Tag is important to identify the origin of the call on SIP extensions. The resolution of the camera shall be adjusted to the needs of the terminals used to receive the call. &lt;br /&gt;
&lt;br /&gt;
[[File:41B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   In case of calling more than one extension at the same time, it must be indicated whether the call will be made in parallel or sequentially, calling the next extension if the previous one is not answered within 30 seconds. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*  2) NETWORK SETTINGS&lt;br /&gt;
&lt;br /&gt;
An IP address compatible with the installation&#039;s LAN will be assigned and the gateway or router address will be indicated to access the Internet. A DNS server is necessary to be defined.   The IP of the software will be left as the default because in this case it is not going to be used unless it is required to manage access control registrations and cancellations for employees (proximity cards or facial recognition). In this case, the IP address of the computer that has the MEET management software (MMS) installed shall be indicated. &lt;br /&gt;
&lt;br /&gt;
[[File:41C.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   3) INNOVAPHONE SIP PBX SETTINGS&lt;br /&gt;
&lt;br /&gt;
In the SIP Configuration section, indicate the IP of the assigned Innovaphone PBX, as shown in the screen below (192.168.1.221). Enter the user (extension number) and the password assigned to the outdoor panel extension (registration password). Next, check if the panel is correctly configured in the switchboard by clicking on the VIEW SIP STATUS link. If REGISTERED does not appear, check the information entered. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:41D.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
In the console of the SIP PBX the extension of the MEET panels will appear as registered in PBX&amp;gt;Registrations: &lt;br /&gt;
&lt;br /&gt;
[[File:41E.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
*   4) CALL EXTENSIONS CONFIGURATIONS&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    a. OUTDOOR PANEL 1 PUSHBUTTON (MILO 1W) &lt;br /&gt;
    Go to the &#039;SIP CALL&#039; tab and enter the apartment number indicated in the &#039;GENERAL&#039; section (101 in our example) and as NUMBER the SIP extension you want to call (110 in the example) and click on &#039;SAVE&#039;. &lt;br /&gt;
[[File:5A.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
    &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
     b. OUTDOOR PANEL WITH MULTICALL KEYPAD (KIN/MARINE/MILO)&lt;br /&gt;
     A CSV file will be configured with the assignment of call codes to the extensions to be called. The CSV file format can be downloaded from the SIP CALL section of the panel’s web server, EXPORT option.&lt;br /&gt;
     An example is the following:  &lt;br /&gt;
&lt;br /&gt;
[[File:5Aa.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   The code to be dialled is indicated first and separated by a comma, the extension of the switchboard that is to receive the call when this dialling code is dialled. In the example, dialling 1 will call the softphone with extension 110 through the gateway. Dialling 2 will call the same softphone without going through the gateway.  It is possible to call more than one extension by listing multiple extensions in the same row separated by semicolons. One of these extensions can be a MeetMe licence to be able to call a smartphone via the MeetMe application. This allows you to call a smartphone outside the local network, including video.  To load the CSV file on the panel, select the file created and click on the IMPORT button. The list of calls of the file will appear on the screen. Sometimes it is necessary to refresh the browser screen by clicking on the corresponding icon: &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[File:5B.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   If we want to be able to call via the agenda in the case of a KIN panel, the agenda will be created in a CSV file (different from the previous one). The CSV file format can be downloaded from the ADVANCED section of the panel’s web server, EXPORT option.  One row is filled in per phonebook item, indicating the call code, Name to appear, blank, Y,.  Example: &lt;br /&gt;
&lt;br /&gt;
[[File:5c.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
   &lt;br /&gt;
   The file is loaded using the IMPORT option:  &lt;br /&gt;
&lt;br /&gt;
[[File:5d.jpg|thumb|left]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
   &lt;br /&gt;
    The DIRECTORY option is enabled so that this option appears on the panel.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Operation===&lt;br /&gt;
&lt;br /&gt;
To call a specific extension, press the call button (one-way panel) or enter the associated call code (building panel) and confirm with the bell button (Milo, Marine) or the off-hook icon (KIN). In the case of the KIN or MARINE panel, you also have the option of making the call via the agenda, by searching for the name of the receiver and pressing on it. &lt;br /&gt;
&lt;br /&gt;
The panel will generate the call : &lt;br /&gt;
&lt;br /&gt;
The called extension will receive the ringing tone and call origin information showing the name assigned in the PBX and the camera image (depending on whether the receiving device has a video option). The call will ring for a maximum of 30 seconds. When the call is accepted, two-way audio communication shall be established and may last up to a maximum of 120 seconds. You have the option of opening the door by pressing the &#039;*&#039; or &#039;#&#039; key on the keypad, which will activate the internal relay of the panel and also first external relay of ref. 1490 (if installed). The &#039;0&#039; key activates only the second relay of ref. 1490.  &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
For more info check &lt;br /&gt;
https://meet.fermax.com&lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| FERMAX&lt;br /&gt;
|- &lt;br /&gt;
| Carlos Ferrer&lt;br /&gt;
|- &lt;br /&gt;
| Avda. Tres Cruces 133 Valencia (Spain)&lt;br /&gt;
|-&lt;br /&gt;
| 46017&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| +34 96 317 80 00&lt;br /&gt;
|-&lt;br /&gt;
| [mailto:cferrer@fermax.com cferrer@fermax.com]&lt;br /&gt;
|-&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://meet.fermax.com meet.fermax.com].&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70613</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70613"/>
		<updated>2024-01-10T15:58:42Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
XXXXXX (Introduccion a Fermax) GmbH specializes in leading-edge building communication and automation solutions. Since our inception in Kappelrodeck in 2018, we have dedicated ourselves to crafting state-of-the-art smart home solutions and IP video door intercom systems. Our flagship product, the SIAS IP video door intercom, transcends the traditional doorbell, weaving security, convenience, and advanced technology into the fabric of daily living.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70612</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70612"/>
		<updated>2024-01-10T15:57:01Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
XXXXXX (Introduccion a Fermax) GmbH specializes in leading-edge building communication and automation solutions. Since our inception in Kappelrodeck in 2018, we have dedicated ourselves to crafting state-of-the-art smart home solutions and IP video door intercom systems. Our flagship product, the SIAS IP video door intercom, transcends the traditional doorbell, weaving security, convenience, and advanced technology into the fabric of daily living.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70611</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70611"/>
		<updated>2024-01-10T15:56:12Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Description */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
XXXXXX (Introduccion a Fermax) GmbH specializes in leading-edge building communication and automation solutions. Since our inception in Kappelrodeck in 2018, we have dedicated ourselves to crafting state-of-the-art smart home solutions and IP video door intercom systems. Our flagship product, the SIAS IP video door intercom, transcends the traditional doorbell, weaving security, convenience, and advanced technology into the fabric of daily living.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
MEET IP system is a 100% full IP video intercom system that is SIP compatible. Therefore it is possible to call a SIP extension registered in a SIP server. For that the IP outdoor panel can be registered (not mandatory) in a SIP server. The call to a SIP terminal can be combined in parallel with calls to FERMAX MEET indoor monitor stations, or FERMAX MEET ME app, so it is really flexible.&lt;br /&gt;
&lt;br /&gt;
It is not the main purpose of this article, but MEET outdoor panels can also call direct to an IP of a SIP client since it is Peer to Peer compatible.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70610</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70610"/>
		<updated>2024-01-10T15:54:58Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
XXXXXX (Introduccion a Fermax) GmbH specializes in leading-edge building communication and automation solutions. Since our inception in Kappelrodeck in 2018, we have dedicated ourselves to crafting state-of-the-art smart home solutions and IP video door intercom systems. Our flagship product, the SIAS IP video door intercom, transcends the traditional doorbell, weaving security, convenience, and advanced technology into the fabric of daily living.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70609</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70609"/>
		<updated>2024-01-10T15:54:36Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
XXXXXX GmbH specializes in leading-edge building communication and automation solutions. Since our inception in Kappelrodeck in 2018, we have dedicated ourselves to crafting state-of-the-art smart home solutions and IP video door intercom systems. Our flagship product, the SIAS IP video door intercom, transcends the traditional doorbell, weaving security, convenience, and advanced technology into the fabric of daily living.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70608</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70608"/>
		<updated>2024-01-10T15:54:16Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
XXXXXX GmbH specializes in leading-edge building communication and automation solutions. Since our inception in Kappelrodeck in 2018, we have dedicated ourselves to crafting state-of-the-art smart home solutions and IP video door intercom systems. Our flagship product, the SIAS IP video door intercom, transcends the traditional doorbell, weaving security, convenience, and advanced technology into the fabric of daily living.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70607</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70607"/>
		<updated>2024-01-10T15:52:56Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70606</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70606"/>
		<updated>2024-01-10T15:50:16Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
[[Image:CompanyLogo.png|150px]] &lt;br /&gt;
 &lt;br /&gt;
==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
&#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
&amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V12r2sr24&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
{|&lt;br /&gt;
| CompanyName&lt;br /&gt;
|-&lt;br /&gt;
| ContactName&lt;br /&gt;
|-&lt;br /&gt;
| Street&lt;br /&gt;
|-&lt;br /&gt;
| ZIP City&lt;br /&gt;
|-&lt;br /&gt;
| Tel: &lt;br /&gt;
|-&lt;br /&gt;
| Mobile:&lt;br /&gt;
|-&lt;br /&gt;
| Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
|} &lt;br /&gt;
&lt;br /&gt;
For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70605</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70605"/>
		<updated>2024-01-10T15:48:18Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
 [[Image:CompanyLogo.png|150px]] &lt;br /&gt;
 &lt;br /&gt;
 ==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
 ==Title2==&lt;br /&gt;
 ===Title3===&lt;br /&gt;
 &#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
 * - list item&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 Product versions used for interop testing:&lt;br /&gt;
 &amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
 * 3rd-Pty-Product Version&lt;br /&gt;
 &amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
 * innovaphone V12r2sr24&lt;br /&gt;
 &lt;br /&gt;
 ==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
 ==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 ==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 {|&lt;br /&gt;
 | CompanyName&lt;br /&gt;
 |-&lt;br /&gt;
 | ContactName&lt;br /&gt;
 |-&lt;br /&gt;
 | Street&lt;br /&gt;
 |-&lt;br /&gt;
 | ZIP City&lt;br /&gt;
 |-&lt;br /&gt;
 | Tel: &lt;br /&gt;
 |-&lt;br /&gt;
 | Mobile:&lt;br /&gt;
 |-&lt;br /&gt;
 | Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
 |} &lt;br /&gt;
&lt;br /&gt;
 For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70604</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70604"/>
		<updated>2024-01-10T15:43:56Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
 ==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
 [[Image:CompanyLogo.png|150px]] &lt;br /&gt;
 &lt;br /&gt;
 ==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
 ==Title2==&lt;br /&gt;
 ===Title3===&lt;br /&gt;
 &#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
 * - list item&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 Product versions used for interop testing:&lt;br /&gt;
 &amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
 * 3rd-Pty-Product Version&lt;br /&gt;
 &amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
 * innovaphone V12r2sr24&lt;br /&gt;
 &lt;br /&gt;
 ==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
 ==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 ==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 {|&lt;br /&gt;
 | CompanyName&lt;br /&gt;
 |-&lt;br /&gt;
 | ContactName&lt;br /&gt;
 |-&lt;br /&gt;
 | Street&lt;br /&gt;
 |-&lt;br /&gt;
 | ZIP City&lt;br /&gt;
 |-&lt;br /&gt;
 | Tel: &lt;br /&gt;
 |-&lt;br /&gt;
 | Mobile:&lt;br /&gt;
 |-&lt;br /&gt;
 | Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
 |} &lt;br /&gt;
&lt;br /&gt;
 For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70603</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70603"/>
		<updated>2024-01-10T15:43:11Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
 ==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
 ==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
 [[Image:CompanyLogo.png|150px]] &lt;br /&gt;
 &lt;br /&gt;
 ==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
 ==Title2==&lt;br /&gt;
 ===Title3===&lt;br /&gt;
 &#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
 * - list item&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 Product versions used for interop testing:&lt;br /&gt;
 &amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
 * 3rd-Pty-Product Version&lt;br /&gt;
 &amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
 * innovaphone V12r2sr24&lt;br /&gt;
 &lt;br /&gt;
 ==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
 ==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 ==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 {|&lt;br /&gt;
 | CompanyName&lt;br /&gt;
 |-&lt;br /&gt;
 | ContactName&lt;br /&gt;
 |-&lt;br /&gt;
 | Street&lt;br /&gt;
 |-&lt;br /&gt;
 | ZIP City&lt;br /&gt;
 |-&lt;br /&gt;
 | Tel: &lt;br /&gt;
 |-&lt;br /&gt;
 | Mobile:&lt;br /&gt;
 |-&lt;br /&gt;
 | Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
 |} &lt;br /&gt;
&lt;br /&gt;
 For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70602</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70602"/>
		<updated>2024-01-10T15:40:44Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
 ==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
 Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
 &lt;br /&gt;
 ==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
 [[Image:CompanyLogo.png|150px]] &lt;br /&gt;
 &lt;br /&gt;
 ==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
 ==Title2==&lt;br /&gt;
 ===Title3===&lt;br /&gt;
 &#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
 * - list item&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 Product versions used for interop testing:&lt;br /&gt;
 &amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
 * 3rd-Pty-Product Version&lt;br /&gt;
 &amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
 * innovaphone V12r2sr24&lt;br /&gt;
 &lt;br /&gt;
 ==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
 ==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 ==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 {|&lt;br /&gt;
 | CompanyName&lt;br /&gt;
 |-&lt;br /&gt;
 | ContactName&lt;br /&gt;
 |-&lt;br /&gt;
 | Street&lt;br /&gt;
 |-&lt;br /&gt;
 | ZIP City&lt;br /&gt;
 |-&lt;br /&gt;
 | Tel: &lt;br /&gt;
 |-&lt;br /&gt;
 | Mobile:&lt;br /&gt;
 |-&lt;br /&gt;
 | Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
 |} &lt;br /&gt;
&lt;br /&gt;
 For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70601</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70601"/>
		<updated>2024-01-10T14:42:53Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
 ==Product Name==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
 CompanyName [https://www.linktoproductpage.com ProductName]&lt;br /&gt;
 &lt;br /&gt;
 ==Certification Status==&lt;br /&gt;
 &amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Category==&lt;br /&gt;
 &amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Vendor==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
 [[Image:CompanyLogo.png|150px]] &lt;br /&gt;
 &lt;br /&gt;
 ==Description==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
 ==Title2==&lt;br /&gt;
 ===Title3===&lt;br /&gt;
 &#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
 * - list item&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- [[Image:ProductLogo.png]] --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone CTI ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supported Codecs==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==DTMF Support==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Support LDAP Phonebook==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Version==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 Product versions used for interop testing:&lt;br /&gt;
 &amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
 * 3rd-Pty-Product Version&lt;br /&gt;
 &amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
 * innovaphone V12r2sr24&lt;br /&gt;
 &lt;br /&gt;
 ==Configuration==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
 ==Summary==&lt;br /&gt;
 &amp;lt;!-- Optional topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 ==Contact==&lt;br /&gt;
 &amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 {|&lt;br /&gt;
 | CompanyName&lt;br /&gt;
 |-&lt;br /&gt;
 | ContactName&lt;br /&gt;
 |-&lt;br /&gt;
 | Street&lt;br /&gt;
 |-&lt;br /&gt;
 | ZIP City&lt;br /&gt;
 |-&lt;br /&gt;
 | Tel: &lt;br /&gt;
 |-&lt;br /&gt;
 | Mobile:&lt;br /&gt;
 |-&lt;br /&gt;
 | Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
 |} &lt;br /&gt;
&lt;br /&gt;
 For any questions please refer to [https://www.vendor.tld/contact our contact page].FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70600</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70600"/>
		<updated>2024-01-10T14:39:50Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;amp;gt;&lt;br /&gt;
 [[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
 &lt;br /&gt;
 ==Product Name==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;amp;gt;&lt;br /&gt;
 CompanyName [https://www.linktoproductpage.com ProductName]&lt;br /&gt;
 &lt;br /&gt;
 ==Certification Status==&lt;br /&gt;
 &amp;amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- {{Template:Compat_Status_referral_terminals|manufacturername=Acme Ltd.|certificationdate=in January 1970}} --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Category==&lt;br /&gt;
 &amp;amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- [[Category:Referral Product|{{PAGENAME}}]] --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- [[Category:3rdParty product categorie to be filled by innovaphone|{{PAGENAME}}]] --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Vendor==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- Give some introducting words about the vendor itself --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;amp;gt;&lt;br /&gt;
 [[Image:CompanyLogo.png|150px]] &lt;br /&gt;
 &lt;br /&gt;
 ==Description==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- place optional product logo or functional overwiew. --&amp;amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
 ==Title2==&lt;br /&gt;
 ===Title3===&lt;br /&gt;
 &#039;&#039;&#039;xxx&#039;&#039;&#039; fat text&lt;br /&gt;
 * - list item&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;amp;lt;!-- [[Image:ProductLogo.png]] --&amp;amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 &amp;amp;lt;!-- some text --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;amp;lt;!-- &#039;&#039;&#039;Benefits at a glance:&#039;&#039;&#039;--&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &lt;br /&gt;
 &amp;amp;lt;!--&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 * Bullet-point&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Functions==&lt;br /&gt;
 &lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 &amp;amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone CTI ready==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!--&lt;br /&gt;
 * Initiate outgoing call (automatic call with no manual intervention, update of called party, correct call direction in call list) yes/no&lt;br /&gt;
 * Answer incoming call yes/no&lt;br /&gt;
 * Hold/Retrieve yes/no&lt;br /&gt;
 * Transfer yes/no&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone Reverse Proxy ready==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!--&lt;br /&gt;
 * STUN yes/no&lt;br /&gt;
 * TURN yes/no&lt;br /&gt;
 * ICE yes/no&lt;br /&gt;
 * SIP/TCP yes/no&lt;br /&gt;
 * SIP/TLS yes/no&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==innovaphone WebRTC ready==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!--&lt;br /&gt;
 * Codec G.711 yes/no&lt;br /&gt;
 * Codec OPUS yes/no&lt;br /&gt;
 * DTLS encryption yes/no (RFC?)&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supported Codecs==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&amp;amp;lt;!--&lt;br /&gt;
 * G.722 yes/no&lt;br /&gt;
 * G.711 A-law yes/no&lt;br /&gt;
 * G.711 y-law yes/no&lt;br /&gt;
 * G.723.1 (53) yes/no&lt;br /&gt;
 * G.729A yes/no&lt;br /&gt;
 * Opus yes/no (RFC, WB, NB?)&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==DTMF Support==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!--&lt;br /&gt;
 * SIP INFO (RFC?)&lt;br /&gt;
 * RTP DTMF (RFC?)&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Supports RFC3261 Digest Authentication Scheme (Section 22.4)==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!--&lt;br /&gt;
 * Supports RFC3261 Digest Authentication Scheme (Section 22.4) yes/no&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Support LDAP Phonebook==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!--&lt;br /&gt;
 * Support LDAP Phonebook yes/no&lt;br /&gt;
 --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 ==Version==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 Product versions used for interop testing:&lt;br /&gt;
 &amp;amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;amp;gt;&lt;br /&gt;
 * 3rd-Pty-Product Version&lt;br /&gt;
 &amp;amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;amp;gt;&lt;br /&gt;
 * innovaphone V12r2sr24&lt;br /&gt;
 &lt;br /&gt;
 ==Configuration==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- If not present, no certificate will be given at all --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;amp;gt;&lt;br /&gt;
 ==Summary==&lt;br /&gt;
 &amp;amp;lt;!-- Optional topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;amp;gt; &lt;br /&gt;
 &lt;br /&gt;
 ==Contact==&lt;br /&gt;
 &amp;amp;lt;!-- Mandatory topic. --&amp;amp;gt;&lt;br /&gt;
 &amp;amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;amp;gt;&lt;br /&gt;
 &lt;br /&gt;
 {|&lt;br /&gt;
 | CompanyName&lt;br /&gt;
 |-&lt;br /&gt;
 | ContactName&lt;br /&gt;
 |-&lt;br /&gt;
 | Street&lt;br /&gt;
 |-&lt;br /&gt;
 | ZIP City&lt;br /&gt;
 |-&lt;br /&gt;
 | Tel: &lt;br /&gt;
 |-&lt;br /&gt;
 | Mobile:&lt;br /&gt;
 |-&lt;br /&gt;
 | Mail: [mailto:contactname@companyname contactname@companyname]&lt;br /&gt;
 |} &lt;br /&gt;
&lt;br /&gt;
 For any questions please refer to [https://www.vendor.tld/contact our contact page].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
FIN&lt;br /&gt;
&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:logo-MEET-400.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
Fermax [https://meet.fermax.com/ MEET]&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- {{Category:3rdParty product categorie to be filled by innovaphone}} --&amp;gt;&lt;br /&gt;
[[Category:Referral Product|{{PAGENAME}}]]&lt;br /&gt;
{{Category:3rdParty_Terminal_Devices}}&lt;br /&gt;
[[Category:3rdParty_Terminal_Devices|{{PAGENAME}}]]&lt;br /&gt;
&lt;br /&gt;
FIN&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70599</id>
		<title>Howto:MEET - Fermax - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:MEET_-_Fermax_-_3rd_Party_Product&amp;diff=70599"/>
		<updated>2024-01-10T14:36:07Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: Created page with &amp;quot;Hello&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Hello&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=File:Logo-MEET-400.jpg&amp;diff=70587</id>
		<title>File:Logo-MEET-400.jpg</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=File:Logo-MEET-400.jpg&amp;diff=70587"/>
		<updated>2024-01-10T09:22:20Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Logo-MEET-400&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto13r3:Configure_User_Presence_Sync_by_Connector_for_Microsoft365&amp;diff=68526</id>
		<title>Howto13r3:Configure User Presence Sync by Connector for Microsoft365</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto13r3:Configure_User_Presence_Sync_by_Connector_for_Microsoft365&amp;diff=68526"/>
		<updated>2023-09-08T10:36:18Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;==Applies To==&lt;br /&gt;
This information applies to&lt;br /&gt;
V13r3&lt;br /&gt;
&lt;br /&gt;
==More Information==&lt;br /&gt;
&lt;br /&gt;
This article outlines a configuration scheme for Connector for Microsoft365 functionality.&amp;lt;br&amp;gt;&lt;br /&gt;
In Preparation you first will need to configure two Application in your Azure Portal (one for each direction). &amp;lt;br&amp;gt;&lt;br /&gt;
After that you will install the App in your Application Platform, and configure everything.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===System Requirements===&lt;br /&gt;
&lt;br /&gt;
* Licenses &#039;&#039;&#039;innovaphone Connector for Microsoft 365&#039;&#039;&#039; 1 x user&lt;br /&gt;
* &#039;&#039;&#039;account in Azure Portal of Microsoft&#039;&#039;&#039; (for technical communictaion, no permission role needed)&amp;lt;br&amp;gt;&lt;br /&gt;
** Must have a Teams License applied, more infos can be found  [https://learn.microsoft.com/en-us/azure/communication-services/quickstarts/eligible-teams-licenses here]&amp;lt;br&amp;gt;&lt;br /&gt;
** Must &#039;&#039;&#039;not&#039;&#039;&#039; have multi factor authentication activated&lt;br /&gt;
* Must have access from the internet to your App Platform&lt;br /&gt;
** This can be done by using a reverse proxy or other firewall&lt;br /&gt;
* The public endpoint &#039;&#039;&#039;must have &#039;&#039;&#039; a &#039;&#039;&#039;valid, public signed certificate&#039;&#039;&#039; (in order to make a trusted SSL connection from the Azure cloud to the Application Platform possible)&lt;br /&gt;
** A valid certificate is required in all involved network entities - at least in the App Platform and if used in the Reverse Proxy; to ensure transmission of MS365 HTTPS POST requests to the app service in order to send notifications.&lt;br /&gt;
* Admin account for Azure Portal (only necessary for granting needed permission for registered app during setup)&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
&lt;br /&gt;
===Configuration in Azure Portal===&lt;br /&gt;
====Create an App for syncing Teams to PBX====&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;In the Azure Portal of Microsoft you have to add an app registration&#039;&#039;&#039; &lt;br /&gt;
* &#039;&#039;&#039;You only have to give a name for the app&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:App_Registration_Connector_for_Microsoft365.png|thumb|none|600px|App Registration]]&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Switch to the authentication in the left&#039;&#039;&#039;-&lt;br /&gt;
* &#039;&#039;&#039;You only have to configure allow public client flow&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Authentication_Connector_for_Microsoft365.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Switch to api permissions on the left&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;You have to configure delegated permissions (User.Read.All and Presence.Read.All) as shown in the picture&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Grant access to the api permissions, if not possible you have to ask an admin&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:APIPermission_Connector_for_Microsoft365.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
With these configurations you can configure the Connector for Microsoft365&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Client ID as shown in the picture&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Tenant ID as shown in the picture&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;User&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Password&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Overview_Connector_for_Microsoft365.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
====Create an App for syncing PBX to Teams====&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;In the Azure Portal of Microsoft you have to add a new app registration&#039;&#039;&#039; &lt;br /&gt;
* &#039;&#039;&#039;In the picture you can see that we have 2 values after that which we can use for the configuration of the app&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Overview_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Switch to the authentication in the left&#039;&#039;&#039;-&lt;br /&gt;
* &#039;&#039;&#039;You only have to configure a client secret and save the value for the configuration of the app&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:Authentication_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Switch to api permissions on the left&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;You have to configure application permission (Presence.ReadWrite.All) as shown in the picture&#039;&#039;&#039;&lt;br /&gt;
* &#039;&#039;&#039;Grant access to the api permissions, if not possible you have to ask an admin&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
[[Image:APIPermission_Connector_for_Microsoft365_Sync_to_Teams.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
===Installing and configuring App Platform and PBX===&lt;br /&gt;
====Installing the connector app====&lt;br /&gt;
* First you need to install the connector app from the App Store:&lt;br /&gt;
[[Image:Microsoft365_install_app_1.png|thumb|none|600px]]&lt;br /&gt;
* Install the app by selecting&lt;br /&gt;
# All apps&lt;br /&gt;
# innovaphone AG&lt;br /&gt;
# innovaphone myApps Connector for Microsoft 365&lt;br /&gt;
# select the current Version &lt;br /&gt;
# Click install&lt;br /&gt;
[[Image:Microsoft365_install_app_2.png|thumb|none|600px]]&lt;br /&gt;
====Creating an instance for the connector app====&lt;br /&gt;
* For creating an Instance, in the AP Manager you need to &lt;br /&gt;
# select &#039;&#039;&#039;innovaphone myApps Connector for Microsoft 365&#039;&#039;&#039;&lt;br /&gt;
# click &#039;&#039;&#039;add&#039;&#039;&#039;&lt;br /&gt;
[[Image:Microsoft365_create_instance_1.png|thumb|none|600px]]&lt;br /&gt;
* Insert the following information and save&lt;br /&gt;
# The technical Instance Name (we suggest microsoft365)&lt;br /&gt;
# Your Domain (This should be the domain you have already configured in your PBX and your Application Platform)&lt;br /&gt;
# define a password for the communication between the PBX and the app instance&lt;br /&gt;
# define a password for the communication between the app instance and the database&lt;br /&gt;
&#039;&#039;All other fieds should be filled automatically&#039;&#039;&lt;br /&gt;
[[Image:Microsoft365_create_instance_2.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
====Creating the PBX app object using the PBX Manager Plugin====&lt;br /&gt;
* Open the PBX Manager and &lt;br /&gt;
# select the &#039;&#039;&#039;AP &amp;lt;code&amp;gt;InstanceName&amp;lt;/code&amp;gt;&#039;&#039;&#039; Tile&lt;br /&gt;
# Click &#039;&#039;&#039;Add an app&#039;&#039;&#039;&lt;br /&gt;
[[Image:Microsoft365_pbx_manager_1.png|thumb|none|600px]]&lt;br /&gt;
* Specify the &#039;&#039;&#039;Name&#039;&#039;&#039; and the &#039;&#039;&#039;SIP&#039;&#039;&#039; (We suggest using &#039;&#039;&#039;&amp;lt;code&amp;gt;microsoft365&amp;lt;/code&amp;gt;&#039;&#039;&#039; for this technical names)&lt;br /&gt;
[[Image:Microsoft365_pbx_manager_2.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
====Add the admin app to a user or a template====&lt;br /&gt;
To be able to configure the connector app, you need users to have access to the admin app.&amp;lt;br&amp;gt;&lt;br /&gt;
You can achieve this by adding the app to a user, or to a template. &amp;lt;br&amp;gt;&lt;br /&gt;
In this Howto - as an example - we will add the app to the &amp;lt;code&amp;gt;Config Admin&amp;lt;/code&amp;gt; template. &amp;lt;br&amp;gt;&lt;br /&gt;
* In the PBX Manager &lt;br /&gt;
# select the &amp;lt;code&amp;gt;Templates&amp;lt;/code&amp;gt; tile &lt;br /&gt;
# click on the &amp;lt;code&amp;gt;Config Admin&amp;lt;/code&amp;gt; template&lt;br /&gt;
[[Image:Microsoft365_template_1.png|thumb|none|600px]]&lt;br /&gt;
* In the &amp;lt;code&amp;gt;Config Admin&amp;lt;/code&amp;gt; template&lt;br /&gt;
# open Apps&lt;br /&gt;
# Check the &amp;lt;code&amp;gt;app name&amp;lt;/code&amp;gt; checkbox&lt;br /&gt;
# Save the changes&lt;br /&gt;
[[Image:Microsoft365_template_2.png|thumb|none|600px]]&lt;br /&gt;
&lt;br /&gt;
====Configure the connector with the admin app====&lt;br /&gt;
Now your admins (designated groups or configured user) should have access to the connector admin app. &amp;lt;br&amp;gt;&lt;br /&gt;
* A user with access to the app can now see a new tile in the &#039;&#039;&#039;All Apps&#039;&#039;&#039; area&lt;br /&gt;
* The name depends on the configured &amp;lt;code&amp;gt;app name&amp;lt;/code&amp;gt; from the PBX Manager plugin&lt;br /&gt;
[[Image:Microsoft365_admin_app_1.png|thumb|none|600px]]&lt;br /&gt;
=====Synchronization from Teams to the PBX=====&lt;br /&gt;
* First you will need to configure the inbound syn from Teams to PBX&lt;br /&gt;
# &#039;&#039;&#039;Master PBX&#039;&#039;&#039; - Set the name of your Master PBX (Not full DNS name, really just only the PBX name)&lt;br /&gt;
# &#039;&#039;&#039;ClientIDSynctoPbx&#039;&#039;&#039; - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created Teams to PBX app&lt;br /&gt;
# &#039;&#039;&#039;TenantSynctoPbx&#039;&#039;&#039; - Please insert the Directory ID (Tenand) from Azure Portal from the in preparation created Teams to PBX app&lt;br /&gt;
# &#039;&#039;&#039;UserSynctoPbx&#039;&#039;&#039; - Please insert the email address (login) from the communication user you are going to use for the communication with the Azure Portal (the user has to have a Teams license and must not have MFA activated, does not need any permission)&lt;br /&gt;
# &#039;&#039;&#039;PasswordSynctoPbx&#039;&#039;&#039; - Inset the communication users password&lt;br /&gt;
# &#039;&#039;&#039;Notification URL&#039;&#039;&#039; - You need to specify the address Microsoft can send presence updates to.&lt;br /&gt;
## You need to make sure that you define a URL where you can reach your App Platform from the public internet &amp;lt;code&amp;gt;public.dns&amp;lt;/code&amp;gt;&lt;br /&gt;
## Next you need the domain you have configured in the app instance before (3.2.2) &amp;lt;code&amp;gt;your.domain&amp;lt;/code&amp;gt;&lt;br /&gt;
## Next you need the name of the instance you have configured before (3.2.2) &amp;lt;code&amp;gt;microsoft365&amp;lt;/code&amp;gt;&lt;br /&gt;
## The URL will always be terminated by &amp;lt;code&amp;gt;subscriptions&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;https://public.dns/your.domain/microsoft365/subscriptions&amp;lt;/code&amp;gt;&lt;br /&gt;
** After successful configuration and subscription the Microsoft services will connect to the specified &#039;&#039;Notification URL&#039;&#039; for presence and line state updates.&lt;br /&gt;
** For this to work it is important to make sure that the specified &#039;&#039;Notification URL&#039;&#039; is reachable from the Microsoft services, meaning from the public internet.&lt;br /&gt;
* Save your changes&lt;br /&gt;
[[Image:Microsoft365_admin_app_2.png|thumb|none|600px]]&lt;br /&gt;
&#039;&#039;&#039;It can take up to 10 Minutes until all check marks are green and the sync is working&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=====Synchronization from the PBX to Teams=====&lt;br /&gt;
* For the outbound synchronization you select from PBX to Teams in the admin app&lt;br /&gt;
# &#039;&#039;&#039;ClientIDSynctoTeams&#039;&#039;&#039; - Please insert the Application ID (Client ID) from Azure Portal from the in preparation created PBX to Teams app&lt;br /&gt;
# &#039;&#039;&#039;TenantSyncto Teams&#039;&#039;&#039; - Please insert the Directory ID (Tenand) from Azure Portal from the in preparation created PBX to Teams app&lt;br /&gt;
# &#039;&#039;&#039;ClientSecretSynctoTeams&#039;&#039;&#039; - Please insert the shared secret from the in preparation created PBX to Teams app&lt;br /&gt;
[[Image:Microsoft365_admin_app_3.png|thumb|none|600px]]&lt;br /&gt;
* For the sync direction from PBX to Teams the app itself needs visibility permissions (presence, on-the-phone) for the users who are should be synced to Teams. The configuration tag is visibility for each user object.&lt;br /&gt;
&lt;br /&gt;
==Related Articles==&lt;br /&gt;
[[Reference13r3:Concept_App_Service_Connector_for_Microsoft_365|Concept App Service Connector for Microsoft 365]]&lt;br /&gt;
&lt;br /&gt;
[[Category:Howto|{{PAGENAME}}]]&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68154</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68154"/>
		<updated>2023-07-07T09:52:45Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Contact */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
ContactName&lt;br /&gt;
&lt;br /&gt;
Severo Ochoa 11&lt;br /&gt;
&lt;br /&gt;
28521 Rivas-Vaciamadrid, Madrid – Spain&lt;br /&gt;
&lt;br /&gt;
Tel:&lt;br /&gt;
&lt;br /&gt;
Fax:&lt;br /&gt;
&lt;br /&gt;
Mail: [mailto:sales@virtualcable.net sales@virtualcable.net]&lt;br /&gt;
&lt;br /&gt;
[http://www.virtualcable.net www.virtualcable.net]&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68153</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68153"/>
		<updated>2023-07-07T09:52:15Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Contact */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Virtual Cable&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ContactName&lt;br /&gt;
&lt;br /&gt;
Severo Ochoa 11&lt;br /&gt;
&lt;br /&gt;
28521 Rivas-Vaciamadrid, Madrid – Spain&lt;br /&gt;
&lt;br /&gt;
Tel:&lt;br /&gt;
&lt;br /&gt;
Fax:&lt;br /&gt;
&lt;br /&gt;
Mail: [mailto:sales@virtualcable.net sales@virtualcable.net]&lt;br /&gt;
&lt;br /&gt;
[http://www.virtualcable.net www.virtualcable.net]&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68152</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68152"/>
		<updated>2023-07-07T09:50:45Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Contact */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Virtual Cable&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
ContactName&lt;br /&gt;
&lt;br /&gt;
Severo Ochoa 11&lt;br /&gt;
&lt;br /&gt;
28521 Rivas-Vaciamadrid, Madrid – Spain&lt;br /&gt;
&lt;br /&gt;
Tel:&lt;br /&gt;
&lt;br /&gt;
Fax:&lt;br /&gt;
&lt;br /&gt;
Mail: [mailto:sales@virtualcable.net sales@virtualcable.net]&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68151</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68151"/>
		<updated>2023-07-07T09:50:11Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Contact */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Virtual Cabñe&lt;br /&gt;
ContactName&lt;br /&gt;
Severo Ochoa 11&lt;br /&gt;
28521 Rivas-Vaciamadrid, Madrid – Spain&lt;br /&gt;
Tel:&lt;br /&gt;
Fax:&lt;br /&gt;
Mail: [mailto:sales@virtualcable.net sales@virtualcable.net]&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68150</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68150"/>
		<updated>2023-07-07T09:49:00Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Contact */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
CompanyName&lt;br /&gt;
ContactName&lt;br /&gt;
Street&lt;br /&gt;
ZIP City Country&lt;br /&gt;
Tel:&lt;br /&gt;
Fax:&lt;br /&gt;
Mail: contactname@companyname&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68149</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68149"/>
		<updated>2023-07-07T09:48:24Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
===== Contact =====&lt;br /&gt;
Severo Ochoa 11&lt;br /&gt;
28521 Rivas-Vaciamadrid, Madrid – Spain&lt;br /&gt;
&lt;br /&gt;
[mailto:sales@virtualcable.net sales@virtualcable.net]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
CompanyName&lt;br /&gt;
ContactName&lt;br /&gt;
Street&lt;br /&gt;
ZIP City Country&lt;br /&gt;
Tel:&lt;br /&gt;
Fax:&lt;br /&gt;
Mail: contactname@companyname&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68148</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68148"/>
		<updated>2023-07-07T09:46:22Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* About Virtual Cable */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Severo Ochoa 11&lt;br /&gt;
28521 Rivas-Vaciamadrid, Madrid – Spain&lt;br /&gt;
&lt;br /&gt;
[mailto;sales@virtualcable.net]&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
CompanyName&lt;br /&gt;
ContactName&lt;br /&gt;
Street&lt;br /&gt;
ZIP City Country&lt;br /&gt;
Tel:&lt;br /&gt;
Fax:&lt;br /&gt;
Mail: contactname@companyname&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
	<entry>
		<id>https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68147</id>
		<title>Howto:UDS - Virtual Cable - 3rd Party Product</title>
		<link rel="alternate" type="text/html" href="https://wiki.innovaphone.com/index.php?title=Howto:UDS_-_Virtual_Cable_-_3rd_Party_Product&amp;diff=68147"/>
		<updated>2023-07-07T09:45:40Z</updated>

		<summary type="html">&lt;p&gt;H.daroca: /* About Virtual Cable */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;!-- replace CompanyLogo by real logo-name. Do not change size &amp;amp; alignment. Upload image by pressing red link --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg||200px|right]]&lt;br /&gt;
&lt;br /&gt;
==Product Name==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- replace CompanyName &amp;amp; ProductName by real names and add URL to productpage --&amp;gt;&lt;br /&gt;
[https://virtualcable.net/soluciones-vdi/ &#039;&#039;&#039;Virtual Cable UDS&#039;&#039;&#039;]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Certification Status==&lt;br /&gt;
&amp;lt;!-- do not remove comment. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Referralprod.PNGThis product is listed due to a customer testimonial.  No tests have been conducted by innovaphone. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Testing of this product has been finalized 29th February, 2020. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Category==&lt;br /&gt;
&amp;lt;!-- Do not change this section and do not remove comments. Will be done by innovaphone upon document check --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Category:3rdParty product categorie to be filled by innovaphone --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&amp;lt;!-- --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Vendor==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give some introducting words about the vendor itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Place optional company logo. Don&#039;t change logo size. --&amp;gt;&lt;br /&gt;
&amp;lt;!--File:CompanyLogo.png  File:[[Image:charLogo.jpg|150px]] --&amp;gt;&lt;br /&gt;
[[Image:Virtualcable-logo.jpg|150px]]&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Virtual Cable&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
===== About Virtual Cable =====&lt;br /&gt;
[http://www.virtualcable.net Virtual Cable] is a company specialising in the &#039;&#039;&#039;digital transformation&#039;&#039;&#039; of the workplace. The company develops, supports and markets UDS Enterprise, software for virtualisation of desktops, applications and remote access to physical equipment. Its team of experts has designed customised VDI solutions for each sector to provide a unique user experience that is fully adapted to the needs of each user profile. Virtual Cable&#039;s professionals have more than 30 years of experience in IT and software development and more than 15 years in virtualisation technologies. Millions of Windows and Linux virtual desktops are deployed every day with UDS Enterprise worldwide.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Severo Ochoa 11&lt;br /&gt;
28521 Rivas-Vaciamadrid, Madrid – Spain&lt;br /&gt;
sales@virtualcable.net&lt;br /&gt;
&lt;br /&gt;
==Description==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give description about the product, benefits, other information to mention to understand main product purpose --&amp;gt;&lt;br /&gt;
&amp;lt;!-- place optional product logo or functional overwiew. --&amp;gt;&lt;br /&gt;
In this compatibility test the product of the company Innovaphone called myApps is tested specifically for the use of Softphone technology.&lt;br /&gt;
In this test, connections will be made to all types of UDS services from a virtual desktop to an RDS application via RDP or HTML5 as well as the correct redirection of the different devices such as a webcam, USB, etc.&lt;br /&gt;
&amp;lt;!-- Some formattings WikiMedia supports:&lt;br /&gt;
==Title2==&lt;br /&gt;
===Title3===&lt;br /&gt;
xxx fat text&lt;br /&gt;
* - list item&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&amp;lt;!-- File:ProductLogo.png --&amp;gt;&lt;br /&gt;
&amp;lt;!-- some text --&amp;gt;&lt;br /&gt;
&amp;lt;!--Benefits at a glance:--&amp;gt;&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
* Bullet-point&lt;br /&gt;
--&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Functions==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give functional description about the product. Use formattings if needed --&amp;gt;&lt;br /&gt;
This section describes the tests carried out both locally and with the UDSEnterprise solution.&lt;br /&gt;
MyApps has access to its solution through a web browser or from the applications available for Windows, Linux, Android, ...&lt;br /&gt;
The tests were successful, we will focus all the tests on the use of myApps together with UDS Enterprise.&lt;br /&gt;
&lt;br /&gt;
[[File:Vdi-innovaphone.png]]&lt;br /&gt;
&lt;br /&gt;
==Use Cases==&lt;br /&gt;
&amp;lt;!-- Optional topic. Delete item if not needed --&amp;gt;&lt;br /&gt;
Through UDS we will be able to deploy different services:&lt;br /&gt;
&lt;br /&gt;
* VDIs:&lt;br /&gt;
By creating UDS machines or using virtual machines, the innovaphone myApps application can be installed on different operating systems.&lt;br /&gt;
&lt;br /&gt;
The connection to these VDI desktops can be made via many transports - from RDP to HTML5.&lt;br /&gt;
&lt;br /&gt;
The tests focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDP: a connection that can be made on a local network or through the UDS tunnel for WAN access.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of a camera/webcam and microphone. a/webcam and microphone so as far as this transport and myApps service is concerned it works perfectly detecting these devices.&lt;br /&gt;
&lt;br /&gt;
HTML5: our transport, which is carried out in the web browser itself, has the limitation of the guacamole technology of not being able to redirect the webcam, so the experience of use could only be measured using only the microphone, which can be redirected in both calls and video calls.&lt;br /&gt;
&lt;br /&gt;
* Virtual apps Windows:&lt;br /&gt;
RDS service gives us the possibility to install the myApps application and in the sessions of each user who starts the application with their specific user.&lt;br /&gt;
&lt;br /&gt;
The RDS tests have focused on the transports:&lt;br /&gt;
&lt;br /&gt;
RDS: through this transport we will be launching the myApps application on the RDS server. In the eyes of any user, it will open another application without knowing that it is actually launching that application from the RDS server without the need to consume resources on their local device.&lt;br /&gt;
&lt;br /&gt;
This transport allows the redirection of webcam and microphone being the use of these satisfactory and correct.&lt;br /&gt;
&lt;br /&gt;
HTML5 RDS: the same as the HTML5 transport, this is an RDS connection embedded in the browser and as another tab of the browser, the application will be launched from the applications. In case the UDS platform has 2 or more applications that use this transport, we can have the different applications inside the browser.&lt;br /&gt;
&lt;br /&gt;
==Version==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt;&lt;br /&gt;
&amp;lt;!-- Give used versions for testing of both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present or outdated innovaphone FW is used, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Product versions used for interop testing:&lt;br /&gt;
&amp;lt;!-- replace 3rd-Pty-Product by real name --&amp;gt;&lt;br /&gt;
* 3rd-Pty-Product Version XXX&lt;br /&gt;
&amp;lt;!-- adjust used innovaphone FW, if applied add further applications (e.g. TAPI &amp;amp; Versions) --&amp;gt;&lt;br /&gt;
* innovaphone V13r3sr6&lt;br /&gt;
&lt;br /&gt;
==Configuration==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Describe configuration steps to be done for both innovaphone and 3rd-pty product --&amp;gt;&lt;br /&gt;
&amp;lt;!-- If not present, no certificate will be given at all --&amp;gt;&lt;br /&gt;
&amp;lt;!-- you may either list the config steps by adding text &amp;amp; pictures, or provide the URL to a PDF-formatted config document. Ideally the document is hosted by the 3rd-party-supplier itself --&amp;gt;&lt;br /&gt;
&amp;lt;!-- in any case you must be aware of the fact that any questions concerning configuration issues will be directly forwarded by innovaphone to you as manufacturer --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Summary==&lt;br /&gt;
&amp;lt;!-- Optional topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Anything to mention which does not fit to above topics. To be deleted if not needed --&amp;gt;&lt;br /&gt;
Screenshots of the different services&lt;br /&gt;
&lt;br /&gt;
USe of VDIs (Windows in this case)&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot1.png]]&lt;br /&gt;
&lt;br /&gt;
In addition, it should be noted that with the RCC Softphone app we can receive calls normally but we can also indicate that the remote VDI machine receives and notifies us of incoming calls and when answering we would not be using this VDI directly but we can indicate a local device or any device we want to make the call through it without having to make use of the VDI or remote desktop (e.g. landline phone configured with innovaphone).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Windows&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot2.png]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
USE of VirtualApp Browser&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshoot3.png]]&lt;br /&gt;
&lt;br /&gt;
==Contact==&lt;br /&gt;
&amp;lt;!-- Mandatory topic. --&amp;gt; &lt;br /&gt;
&amp;lt;!-- Give contact details for potential interests. You may give personal or general contact data. --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
CompanyName&lt;br /&gt;
ContactName&lt;br /&gt;
Street&lt;br /&gt;
ZIP City Country&lt;br /&gt;
Tel:&lt;br /&gt;
Fax:&lt;br /&gt;
Mail: contactname@companyname&lt;/div&gt;</summary>
		<author><name>H.daroca</name></author>
	</entry>
</feed>