innovaphone wiki - User contributions [en]

Howto13r1:Restore an App Platform

2024-08-13T09:05:02Z

Lm ulm pk: little typo

==Applies To==
This information applies to

*Innovaphone App Platform
*any device running a PBX in V13 or up

==Preparation==
* To restore the App Platform you need the ''administrative password'' which was created during the initial installation or which you may have changed yourself afterwards.
* Furthermore you'll need the PBX config and the ''.dump files'' of every App which is created by the backup process of the Devices App.

==Restore PBX==
At first we need to restore the PBX. Therefore we need to change the admin password of the device to its original state. Go to Advanced Admin UI to [[Reference13r1:General/Admin|Admin]] and configure the ''emergency password'' as admin password. Afterwards you can upload the PBX config from the backup folder and reboot the PBX.
*Hint : keep in mind that by restoring on another hardware, may involve change in the configuration ''(e.g: local gateway registration with mac address)'' and licenses need to be uploaded as well.

==Restore Applications==

===Restore Manager===
To restore a Application Platform you need set up an empty one at first. Just go to http://store.innovaphone.com/release/download.htm and choose App Platform and download it.

After the successful installation you can browse to the IP of the App Patform and use the password "pwd" to login.

At first we are going to restore the configuration of the App ''Manager''. Click on Manager and then restore at the top. A dialogue will open which allows you to select the ''manager.dump'' file. You need to upload it this file.

[[Image:app_manager_restore.png]]

===Restore all Apps===
After that we need to reinstall all needed apps individually from the store.

[[Image:restore_install_app.png]]

To restore the specific app configuration click on the app in the left menu and then choose restore in the top menu. Then upload the ''.dump file'' of the app from the backup folder and upload it.
*Hint : Special care for the Files application service, it contains 2 instances ''files'' and ''backup-files'', do not forget to restore both instances

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

Howto7:ACD with Voicemail XML Script and external Database or Application

2022-11-04T13:21:50Z

Lm ulm pk:

This article describes how to setup a simple automated call distribution by using custom voicemail XML script and an external database or a CRM application.

==Applies To==
This information applies to

* innovaphone PBX, V7

==More Information==
A frequently asked feature for incoming call centers is ability to connect incoming customer calls to their respective personal point of contact(an agent or agent group). The relationship of customer calling number and responsible agent is stored in the external database or CRM application. For this purpose a custom XML voicemail script can be used to perform a query from innovaphone PBX to an external application via HTTP.

The voicemail command <code>exec url</code> executes an HTTP GET CGI-request. The URL is supposed to contain arbitrary script variables. The remote CGI script shall return a short voicemail script comprising <code>assign</code> elements.

The call distribution is intentional designed so that the first free agent gets the most calls.

Please note, that the scripts are exemplary and free and can be modified to fulfill your special requirements.

===Configuration===
The outline for the following configuration scenario shall be as follows:
*Create a file with XML script listed below and named "acd.xml".
*Additionally place the text files with numbers of agents and voicemail box in this folder.
*Create a new voicemail object in the PBX with URL <code>http://127.0.0.1/drive/CF0/acd.xml?$_pbxfwd=true</code>.

Contents of acd.xml:
<code xml>
<?xml version="1.0" encoding="utf-8" ?>
<voicemail xmlns="http://www.innovaphone.com/xsd/voicemail6.xsd">
<function define="Main">

<pbx-getcallinfo out-cgpn="$cgpn" out-cdpn="$cdpn" out-leg2="$leg2" />


<assign out="$forward" value="999"/>


<exec url="http://172.16.0.17/query.php?cgpn=$cgpn"/>


<pbx-fwd e164="$forward" out-cause="$cause" barge-in="false" />


<store-get root="" name="silence.$coder" out-url="$ctrl" />
<pbx-prompt url="$ctrl" sec="1" repeat="true"/>
<pbx-disc/>

</function>
</voicemail>
</code>

A very simple server side code example based on PHP:
<code php>
<?php

//just for test: if CGPN is 235, forward to 103
//implement your db query etc. here instead
if ($_GET['cgpn'] == "235") $forward = "103";

echo "<?xml version=\"1.0\" encoding=\"utf-8\"?>\r\n";
echo "<voicemail xmlns=\"http://www.innovaphone.com/xsd/voicemail6.xsd\">\r\n";
echo " <assign out=\"\$forward\" value=\"$forward\"/>\r\n";
echo "</voicemail>\r\n";
?>
</code>

The response of the PHP script should be as follows(if CGPN is 235):
<code xml>
<?xml version="1.0" encoding="utf-8"?>
<voicemail xmlns="http://www.innovaphone.com/xsd/voicemail6.xsd">
<assign out="$forward" value="103"/>
</voicemail>
</code>

===Known Problems===

*Don't forget to provide additional option to the script URL, since it is required for the executing of call forwards: <code>?$_pbxfwd=true</code>

== Related Articles ==
[[Howto:How_to_Configure_the_innovaphone_Voicemail|How to Configure the innovaphone Voicemail]]

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

Howto7:ACD with Voicemail XML Script and external Database or Application

2022-11-04T13:19:06Z

Lm ulm pk:

User:Lm ulm pk

2022-03-28T14:31:47Z

Lm ulm pk: New page: <div style="height:400px;width:400px;display: flex;justify-content: center;align-items: center;color:#626866;background:#91BD2A"> [https://www.priokom.de/ priokom.de] </div>

<div style="height:400px;width:400px;display: flex;justify-content: center;align-items: center;color:#626866;background:#91BD2A">
[https://www.priokom.de/ priokom.de]

</div>

Howto:Simple caller notification Voicemail XML Script

2022-03-28T07:22:22Z

Lm ulm pk:

{{Template:3rd Party Input}}
==Applies To==
This information applies to

* innovaphone PBX, V6 SR1 and later
* innovaphone Voicemail
* innovaphone phones, including softphone and bria softphone


==More Information==
This article explains how a simple caller notification could be set up by using a modified voicemail script.
The Calling Party will get a simple notification without the possibility to leave a message.
The most popular example is a caller notification, that he is calling beyond working hours.

===System Requirements===
* Running innovaphone PBX V6 SR1 and later
* Installed compact flash card or external WebServer with webdav funtionatilty
* Running innovaphone Voicemail

===Configuration===
* Create a new folder called ''notify'' on the CF card
* Copy files from the [[Howto:Simple_caller_notification_Voicemail_XML_Script#Download | download page]] to this new folder named ''notify''
* Configure a VM object which points to the modified vm.xml script (for example http://127.0.0.1/DRIVE/CF0/notify/prompt-or-record.xml)
** From V13 on you can upload files to the AP-Platform via the Files-app to get access to them via webdav.<br>Read here howto accomplish it http://wiki.innovaphone.com/index.php?title=Howto:Record_an_announcement_by_phone#Using_V13_Files-app_as_storage_location

* Calling the VM object will allow you to record the notification - this will be saved as ''announcement.g711a''
* A call diverted to the VM object will play the announcement and quit the call



===Known Problems===
A simple call to the VM object can delete/overwrite the announcement. To provide this, you may delete the extension number after recording and make the call divertion depending on the NAME of the VM object.


== Download ==
*[http://wiki.innovaphone.com/index.php?title=Howto:Wiki_Sources#notify Download] the complete file package of scripts and files described in this article.

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

Howto:Simple caller notification Voicemail XML Script

2022-03-28T07:19:02Z

Lm ulm pk: ext V13 install

{{Template:3rd Party Input}}
==Applies To==
This information applies to

* innovaphone PBX, V6 SR1 and later
* innovaphone Voicemail
* innovaphone phones, including softphone and bria softphone


==More Information==
This article explains how a simple caller notification could be set up by using a modified voicemail script.
The Calling Party will get a simple notification without the possibility to leave a message.
The most popular example is a caller notification, that he is calling beyond working hours.

===System Requirements===
* Running innovaphone PBX V6 SR1 and later
* Installed compact flash card or external WebServer with webdav funtionatilty
* Running innovaphone Voicemail

===Configuration===
* Create a new folder called ''notify'' on the CF card
* Copy files from the [[Howto:Simple_caller_notification_Voicemail_XML_Script#Download | download page]] to this new folder named ''notify''
* Configure a VM object which points to the modified vm.xml script (for example http://127.0.0.1/DRIVE/CF0/notify/prompt-or-record.xml)
** From V13 on you can upload files to the AP-Platform via the Files-app to get access to them via webdav.<br>Read here howto accomplish it {http://wiki.innovaphone.com/index.php?title=Howto:Record_an_announcement_by_phone#Using_V13_Files-app_as_storage_location}

* Calling the VM object will allow you to record the notification - this will be saved as ''announcement.g711a''
* A call diverted to the VM object will play the announcement and quit the call



===Known Problems===
A simple call to the VM object can delete/overwrite the announcement. To provide this, you may delete the extension number after recording and make the call divertion depending on the NAME of the VM object.


== Download ==
*[http://wiki.innovaphone.com/index.php?title=Howto:Wiki_Sources#notify Download] the complete file package of scripts and files described in this article.

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

Howto:DE - Deutsche Telekom - DeutschlandLAN SIP Trunk SIP-Provider (2016)

2021-04-08T11:24:19Z

Lm ulm pk: /* Configuration */

== Summary ==
{{Template:SIP_TEST_STATUS_complete|update=March 11th, 2020|url=https://geschaeftskunden.telekom.de/startseite/festnetz-internet/tarife/333506/deutschlandlan-sip-trunk.html|productname=DeutschlandLAN_SIP_Trunk|providername=Deutsche_Telekom}}
<internal>Provider SBC: unknown</internal>

=== {{SIP_TEST_ISSUES_MR_TITLE}} ===
{{SIP_TEST_ISSUES_MR_INTRO}}
; EARLY MEDIA INBOUND : {{SIP_TEST_FACT_EARLY MEDIA INBOUND}}
; FAX T38 : {{SIP_TEST_FACT_FAX T38}}
; FAX T38ANDAUDIO : {{SIP_TEST_FACT_FAX T38ANDAUDIO}}
; REVERSE MEDIA : {{SIP_TEST_FACT_REVERSE MEDIA}}
; SIP INFO : {{SIP_TEST_FACT_SIP INFO}}

<small>{{SIP_TEST_FACTS_LIST}} [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_180_RINGING_FAILS|180_RINGING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_BASIC_CALL_FAILS|BASIC_CALL]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLIR_FAILS|CLIR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLNS_ONNET_FAILS|CLNS_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CLNS_FAILS|CLNS]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_FAILS|CONN_NR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_DTMF_FAILS|DTMF]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_EARLY_MEDIA_INBOUND_FAILS|EARLY_MEDIA_INBOUND]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_AUDIO_FAILS|FAX_AUDIO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38_FAILS|FAX_T38]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38ANDAUDIO_FAILS|FAX_T38ANDAUDIO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_FAX_T38_ONNET_FAILS|FAX_T38_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711A_ONNET_FAILS|G711A_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711A_FAILS|G711A]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711U_ONNET_FAILS|G711U_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G711U_FAILS|G711U]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G722_ONNET_FAILS|G722_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G722_FAILS|G722]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G729_ONNET_FAILS|G729_ONNET]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_G729_FAILS|G729]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_HOLD_RETRIEVE_FAILS|HOLD_RETRIEVE]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_IP_FRAGMENTATION_FAILS|IP_FRAGMENTATION]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_LARGE_SIP_MESSAGES_FAILS|LARGE_SIP_MESSAGES]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_MOBILITY_FAILS|MOBILITY]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_OPUS_NB_FAILS|OPUS_NB]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_OPUS_WB_FAILS|OPUS_WB]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_RALERT_DISC_FAILS|RALERT_DISC]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_302_FAILS|REDIR_302]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_DIVHDR_FAILS|REDIR_DIVHDR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REDIR_HISTHDR_FAILS|REDIR_HISTHDR]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_REVERSE_MEDIA_FAILS|REVERSE_MEDIA]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SIP_INFO_FAILS|SIP_INFO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_INCOMING_FAILS|SRTP_INCOMING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_INTERNAL_FAILS|SRTP_INTERNAL]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SRTP_OUTGOING_FAILS|SRTP_OUTGOING]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_BLIND_FAILS|XFER_BLIND]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_ALERT_FAILS|XFER_CONS_ALERT]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_EXT_FAILS|XFER_CONS_EXT]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_XFER_CONS_FAILS|XFER_CONS]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_ICE_FAILS|SDP_ICE]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_RTCP_MUX_FAILS|SDP_RTCP_MUX]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_SDP_VIDEO_FAILS|SDP_VIDEO]], [[Template:SIP_TEST_FACT_DESCRIPTION_TEST_CONN_NR_DIFF_FAILS|CONN_NR_DIFF]]</small>

== Test Results ==
{{SIP_TEST_TESTRESULT_ONLYMR_INTRO}}
=== {{SIP_TEST_RESULTS_MR_TITLE}} ===
; Registration : {{Template:SIP_Profile_Test_Registration_TCP_no_UDP}}

; NAT Traversal : {{Template:SIP_Profile_Test_NAT_a_no_c}}

; DTMF (RFC2833) : {{Template:SIP_Profile_Test_DTMF_RFC2833_yes}}

; Session Timer : {{Template:SIP_Profile_Test_EXPIRES_no}}

; Redundancy : {{Template:SIP_Profile_Test_REDUNDANCY_yes_FAILOVER_no|timeout= 240 seconds}}

; Correct signalling of Ringing-state : {{Template:SIP_Profile_Test_RINGING_yes}}

; CLIR : {{Template:SIP_Profile_Test_CLIR_yes}}

; Clip No Screening (CLNS) : {{Template:SIP_Profile_Test_CLNS_yes}} {{Template:SIP_Profile_Test_CLNS_clns_302_optional}}

; COLP : {{Template:SIP_Profile_Test_COLP_out_yes_in_no}} {{Template:SIP_Profile_Test_COLP_diff_yes}}

; Early-Media : {{Template:SIP_Profile_Test_EARLY_MEDIA_INBOUND_no}}

; Fax : {{Template:SIP_Profile_Test_AUDIOFAX_PSTN_yes}}
: {{Template:SIP_Profile_Test_T38_PSTN_no_onnet_yes_fallback_no}}

; Codecs : supported to/from PSTN: G711A
: supported onnet (VoIP to VoIP): G711A, G711U, G722 and G729

; IP-Fragmentation : {{Template:SIP_Profile_Test_FRAGMENTATION_yes}}

; Large SIP messages : {{Template:SIP_Profile_Test_LARGE_MESSAGES_yes}}

; Reverse Media Negotiation : {{Template:SIP_Profile_Test_REV_MEDIA_NEG_no}}

; Mobility Calls : {{Template:SIP_Profile_Test_MobilityCall_no_with_MediaRelay}}

; SRTP : {{Template:SIP_Profile_Test_SRTP_no}}

; Call Transfer : {{Template:SIP_Profile_Test_CALL_TRANSFER_ok}}

==Configuration==
Use profile ''DE-Deutsche_Telekom-DeutschlandLAN_SIP_Trunk'' in ''Gateway/Interfaces/SIP'' to configure this SIP provider.

Please note the following configuration hints:
* <nowiki>Dialling of subscriber numbers not possible, 'Dialing Location' must be configured without 'Area Code'</nowiki>

: {{SIP_TEST_V13_HINT}}

(V13 sr24)
Sometime it may occur on outgoing calls that called numbers are shown as 0 when the partner has picked up the phone.
Setting 'Call Presentation Restricted' für RS1-> SIP1 may be a solution here.

== Disclaimer ==
{{SIP_TEST_PREFACE}}

[[Category:Compat|{{PAGENAME}}]]
[[Category:3rdParty SIP Provider|{{PAGENAME}}]]

Howto:Maintaining a Phone Directory in the PBX

2018-02-22T11:48:35Z

Lm ulm pk: /* Known Problems */

==Applies To==
This information applies to

* PBX, all platforms, V7 and later



==More Information==

===Problem Details===
A shared phone directory for all users is a common requirement in PBX systems. Although there are sophisticated solutions based on LDAP services available (e.g. [[Howto:ESTOS_MetaDirectory%2C_iCE_Information | Metadirectory]]), some customers ask for a small and easy solution which is implemented directly in the PBX and does not require any external components. Here is how to do it.
===System Requirements===
The goal is to make the global phone book available in the phone's directory client for outgoing calls and for reverse identification of incoming calls. You will need a PBX and you will need to configure the phone's external LDAP client accordingly. The solution will also work with the LDAP [[Reference8:Administration/PBX/Objects/Directory_Search | Directory Search ]] object.

===Configuration===
The idea is to configure directory entries as normal user objects. These will be looked up by the phone's directory client. Unfortunately, all these numbers obviously start with the trunk access prefix (usually <code>0</code>) and would thus conflict with your trunk object. The solution is to create a separate [[Reference8:Administration/PBX/Objects/Node|node]] for phone book entries (say <code>telbook</code> for example). This eliminates the conflict as there will be no trunk object in this node. All phone book entries must be configured with the <code>node</code> property set to <code>telbook</code> then.

==== Node ====
To create the [[Reference8:Administration/PBX/Objects/Node|node]], you need to:
* Add a ''Node'' entry with:
* ''Name'' set to e.g. <code>telbook</code>
* '' Long Name'' set to e.g. <code>telbook</code>
* ''Number'' to a available number in the dialing plan. The actual number is not used for the phonebook
* Check the ''Hide from LDAP'' check-mark so the node doesn't appear in LDAP searches.
Rest can be left default.

==== Entries ====
To add an entry, you would create a user [[Reference7:Administration/PBX/Objects|object]] and configure it as follows
* Set ''Long Name'' to some unique id, e.g. <code>_Donald mob</code> (In our example we have used the _ (underscore) as first letter becuase then we got all these object at the end of the PBX-Object listing.)
* Set ''Display Name'' to the name you want to appear in the phone display (e.g. <code>Donald Duck, Metro-Goldwyn-Mayer</code>)
* Set ''Number'' to the number to dial (including trunk prefixes, e.g. <code>007031730090</code>)
* Set ''Node'' to the phone book node you created (e.g. <code>telbook</code>)
* Leave ''PBX'' empty
* Check the ''Hide from LDAP'' check-mark

==== LDAP Server Account ====
On the PBX used to query the directory, you will need to add an appropriate [[Reference:Configuration/LDAP/Server | LDAP account ]] as follows
* add a new LDAP account, named e.g. <code>telbook-access</code>
* add just any password you like, e.g. <code>ipxxx</code>
* make sure you un-check the ''Write-Access'' check-mark

==== Telephone LDAP Directory Client ====
On the client side, you need to configure the LDAP directory client in <code>Configuration / Registration x / Directories</code> accordingly. Here it goes:
* You may want to clear the ''enable'' check-mark in the ''PBX'' box if you want the phone to display phone book entries only. However, leaving it checked will nicely show a merged list of PBX extensions and phone book entries
* You need to check the ''enable'' check-mark in the ''External LDAP Server'' box
* Set ''Server'' to the IP address of your PBX
* Set ''Port'' to 389
* Set ''Username'' and ''Password'' to the credentials of the LDAP server account created previously (e.g. <code>telbook-access</code> and <code>ipxxx</code>)
* Set ''Search Base'' to <code>cn=PBX0</code>
* Set ''Mode'' to <code>basic</code>
* Set ''Object Filter'' to <code>(node=telbook)</code>
* Set ''Name Attributes'' to <code>dn</code>
* Set ''Number Attributes'' to <code>e164</code>
[[Image:Local-LDAP-complete_setup.PNG]]

''*The Write checkmark at the LDAP Server is not necessary anymore.''

The LDAP phone settings can also be set in the DHCP server:

<pre>-mode basic -addr 192.168.0.1 -dn telbook-access -pw ipxxx -base cn=PBX0 -obj (node=telbook) -attr dn -phone e164 </pre>

==== Administrative Access ====
Maintenance of the phone book now requires admin rights in the PBX. However, this maintenance is usually delegated to personel that should not have modify rights on the system's overall configuration. To work around that problem, you would create a special PBX user (say <code>telbook-admin</code>) with limited access rights. You need to
* Create a new ''User'' object
* Set ''Long Name'' and ''Name'' and to the desired name (e.g. <code>telbook-admin</code>)
* Leave ''Number'' empty
* Set ''Password'' to the desired password
* Set ''Node'' to you standard node, but ''not'' to the node you are using for the phone book (e.g. to <code>root</code>, not <code>telbook</code>)
* Leave ''PBX'' empty

On that user object, you would set special access rights. To do so, you open the ''Rights'' dialogue (by clicking the <code>+</code> sign in the ''Rights'' column) and
* Select ''Administration of all Objects'' from the drop-down list
* Set ''Limit to Node'' to your phone book node (e.g. <code>telbook</code>)
* Leave ''Limit to PBX'' empty

The person in charge of the directory administration can now log in to the PBX using this restricted account and safely edit all entries with no risk of doing harm to the rest of the configuration.
[[Image:Local-LDAP-admin-user.png]]

==Known Problems==

* The number of contacts we can have inside the PBX depends on the Hardware/Device we are using for PBX, since all have different capacities for the number of Objects that can be created inside. You can find the recommended number of objects in the [[Howto:How_to_implement_large_PBXs#Recommended__number_of_users_supported| Large PBX article]].

* To maintain a ldap-research from a DECT-gateway with an incoming call you better don't configure the dialing location in the LDAP directory search of the Master. Configuring the dialing location will restructure the ldap-research to a form you can not set as number in the telbook (s.a.) (pbx 12r2 sr3)



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

Reference11r2:PBX/Objects/Gateway

2016-08-29T09:42:31Z

Lm ulm pk:

The ''Gateway'' PBX object is used to register a gateway with the PBX. A Gateway object in contrast to a User object allows additional dialing digits to be sent. Also for incoming calls the incoming calling party number is passed on.

== Gateway Object specific Configuration ==

;Enblock Count: If this number of digits is dialed after the number of the Gateway object itself, the call is sent out as enblock call. This is useful to connect to gateway which are not capable of overlap receiving.

;Enblock as Diverting No: If this checkmark is set, the called party number is transmitted as diverting leg2 information. As called party number the number of the gateway object is sent or no number if the Prefix checkmark is set. This is useful with Microsoft Exchange since this expects the number of the mailbox as diverting number.

;Prefix: If this checkmark is set, the number of the Gateway object itself is removed from the called party number for outgoing calls and added to the calling party number for incoming calls

;Domain: Route calls with matching domain part in the destination to this object.

;Loop Detect: If checked outgoing calls are blocked if a call with identical source and destination addresses already exists.

;International Match: If a call is received with an international calling party number, it is compared to this number. If there is a match (head match) this number is removed from the calling party number, so that only additional digits remain. If the calling party number does not match, it is removed completely. e.g. on an incoming call from a registration on this Gateway object the CGPN I49703173009123 will be mapped to 123.

;National Match: Same as 'International Match' only for national calling party number. e.g. on an incoming call from a registration on this Gateway object the CGPN N703173009123 will be mapped to 123.

;Subscriber Match: Same as 'International Match' only for subscriber calling party number. e.g. on an incoming call from a registration on this Gateway object with the CGPN S73009123 will be mapped to 123.

;Internal Destination: If this checkmark is set, all calls from devices registered at this object are marked as Internal (Numbering plan set to private). This is usefull if systems are registered to this object, which cannot send calls with the private numbering plan but should be regarded as internal (e.g. voicemail systems).

The device registering with a gateway object is normally expected to send local extension numbers as calling party number (i.e. extensions local to the PBX and 'behind' the gateways own number). However, if it sends these numbers as full numbers (that is, including the various prefixes such as county code, are code, trunk, etc.), these can be stripped using the next 3 fields:

;No Inband Disconnect: If this checkmark is set, a call disconnect with inband information will not be forwarded to the endpoint registered to the user, but the call will be cleared immediatelly without the inband information beeing sent..

;Fax License: TBD.

;Filter: The filter configured here restricts the numbers which may be called by through this object.

== Multiple Gateway Registrations ==

If multiple Gateways are registered to a Gateway object, Gateways registered to the same device config are used round-robin. The gateways registered to different devices are used in the sequence of the configured devices.

== Call Diversions ==
;CFU: If configured a CFU is executed, so calls to the Gateways object are diverted.
;CFB: A CFB is executed if a call is rejected with ''User Busy'' by remote destination
;CFNR: A CFNR is executed if a call is rejected because of a local problem (''no channel'', ''no gatway registered'', ...)

Howto:Get Access to Gateways if the Assistant doesn't boot the Device

2016-07-07T11:58:27Z

Lm ulm pk:

==Applies To==
concerns
* IP 811, V11, V12 (at least observed here)



==More Information==
A gateway should reboot after ending the setup-assistant. Sometimes that will not happen.
I have seen such behavior at a IP811 after uploading the last v12 rc1 after the factory
reset, i.e. pressing the reset-button long until the led flashes green and quick, wait
until led turns red and powercyle the device.

A manual reboot (powercyle) won't help here. The Assistant will be shown again.

A booting with sending a !boot (<nowiki>http://<ip of gateway>/!boot</nowiki> ) ends in an nonreacting http-Server.
It is still there but has no content.

Dealing with the !tftp mode and gwload to update firmware or bootcode doesn't help either.

But you can get access to part of the gateway's webgui when calling

'''<nowiki>http://<ip of gateway>/CMD0/mod_cmd.xml?cmd=xml-modes&menu=maintenance.xml&xsl=tab.xsl&help=Maintenance</nowiki>'''
in your webbrowser.
This will show the part of the gui where you can deal with firmware bootcode and config.

Downloading the config, editing the config in the line with

'''config change HTTP0 /home SETUP/wizard.xml'''

to

'''config change HTTP0'''

and upload it to the gateway with a reboot afterwards will lead to a reacting WebGui.

I couldn't find an appropriate '''!mod cmd syntax''' for it but it may exist.

== Related Articles ==

*[[Howto:How to Reset IPXXX (V10...)]]
*[[Howto:How to Reset IPXXX]]

Howto:Get Access to Gateways if the Assistant doesn't boot the Device

2016-07-07T11:57:42Z

Lm ulm pk:

==Applies To==
concerns
* IP 811, V11, V12 (at least observed here)



==More Information==
A gateway should reboot after ending the setup-assistant. Sometimes that will not happen.
I have seen such behavior at a IP811 after uploading the last v12 rc1 after the factory
reset, i.e. pressing the reset-button long until the led flashes green and quick, wait
until led turns red and powercyle the device.

A manual reboot (powercyle) won't help here. The Assistant will be shown again.

A booting with sending a !boot (<nowiki>http://<ip of gateway>/!boot</nowiki> ) ends in an nonreacting http-Server.
It is still there but has no content.

Dealing with the !tftp mode and gwload to update firmware or bootcode doesn't help either.

But you can get access to part of the gateway's webgui when calling

'''<nowiki>http://<ip of gateway>/CMD0/mod_cmd.xml?cmd=xml-modes&menu=maintenance.xml&xsl=tab.xsl&help=Maintenance</nowiki>'''
in your webbrowser.
This will show the part of the gui where you can deal with firmware bootcode and config.

Downloading the config, editing the config in the line with

'''config change HTTP0 /home SETUP/wizard.xml'''

to

'''config change HTTP0'''

and upload it to the gateway with a reboot afterwards will lead to a reacting WebGui.

I couldn't find an appropriate '''!mod cmd syntax''' for it but it may exist.

== Related Articles ==

*[[Howto:How to Reset IPXXX (V10...)]]
*[[Howto:How to Reset IPXXX]]

Howto:How to Reset IPXXX

2016-07-07T11:54:44Z

Lm ulm pk: /* More Information */

==Summary==
Different Reset Options of IPXXX

==Applies To==
This information applies to

* All innovaphone products with the latest boot code.


==More Information==
Different options resetting innovaphone devices.

* bringing to Factory default
* bringing to TFTP mode for GWLoad
* clearing config
* explaining the LED behavior

Additional Information for the following table, TFTP-Mode or TFTP-Mode + FACTORY RESET for the phones IP110, IP150, IP200, IP202, IP230, IP240

Seperating the phone from the power, press the Key/Button, keep on pressing the Key/Button, plug in the PSU or ethernet cable (in case of PoE), watch the status of the device (table: visual display), release the Key/Button after time shown in the table. If you want to reanimate this devices now with GWLoad, do not powercycle the device again. If the factory reset was successful the device is now in the defined TFTP-Mode and ready for GWLoad. If you just wanted to factory reset the device you can do a powercycle for sure.

If the factory reset was not successful please contact rma@innovaphone.com

or look at [[Howto:Get Access to Gateways if the Assistant don't boot the device.]]

{| border=1
!Device (visual display)
!Reset Button/Key
!Button pressed
!Clear Config
Firmware
Boot code update
!Pressing Button to TFTP without deleting config in seconds ca.
!Pressing Button to factory reset in seconds ca.
!GWLoad- / TFTP-Mode
!Firmware starting
!Firmware ready
!Firmware Error
|----
|IP21
(all LED's)
|Button
|ready: <5s blink, >5s constant flash

line1 + line2 + door + aux constant flash / link + act off

with plugged in ethernet cable 100M + link: <3s off, >3s normal operating state
|...

ready fast blink, line1 + line2 + door + aux off link + 100M normal operating

|3
|25
|all LED’s are constant flashing

link is blinking
|ready + line1/2 + door + aux + 100M (if link)

permanent for ca. 5s

link blinking
|ready + 100M (if link)

link blinking
|
|----
|IP400
(all LED’s)
|Button
|PPP+Tel.1+Tel.2: <5s blink, [5;8] constant flash, >8 ready + link + act constant flash

without ethernet cable plugged in: <8s off, 8s one blink, >8s off
|
|3
|25
|ready + link + act flashing constant
|<8 ready + PPP + tel1 + tel2 constant flash,

[3;10] link + act. uncoordinated flashing

>10s ready + link (if link) constant act. blinking
|ready + 100M (if link)

link blinking
|
|----
|IP3000
(all LED’s)
|Button
|<6s PRI1+PRI2+S/T+ready blink, [6;10] PRI1 + PRI2 + S/T + ready constant flash,

act + speed + link off

>10s PRI1 + PRI2 + S/T constant flash, ready + act + speed + link off

with ethernet cable plugged in: act + speed + link normal working state
|fast blink (green)
|3
|25
|all LED’s flashing permanent

ready off

link blinking
|>2 link + speed constant flashing, act blinking

<5s PRI1 + PRI2 + S/T constant flash

>5s ready constant flash, (if link) link + speed constant flashing, act blinking
|ready constant flash, (if link) link + speed constant flashing, act blinking
|blinking (green)
|----
|IP800/IP6000/IPx010
(red/green/orange ready LED )
|Button
|<6 slow gn blink

[6;10] constant red

[10;13] fast gn blink

<13 constant orange
|fast blink (green)
|3
|15 (IP800)

15-20 (IP6000/IPx010)
|constant orange
|red
|green
|blinking (red)
|----
|IP1200
|Button
|<2s alarm red constant flash, ready off

[2;7] alarm off, ready slow blink green

[7;13] alarm off, ready fast blink green

>13s alarm off, ready 2 Hz blink green
|fast blink
|3
|10
|slow flash ca. 2 Hz
|<2s alarm red constant flash

ready green constant flash

power orange constant flash

[2;4] alarm off, ready off, power orange

>4s alarm off, ready constant green flash, power constant green flash
|ready constant green flash and power constant orange flash
|alarm (red)
|----
|IP1202
|Button
|<3s LED off

[3;10] LED blink fast blue 1 sec

>10s LED blink fast blue 1 sec,
than blink slow blue until factory reset completed,
than constant yellow/amber
|fast blink in blue
|3
|10
|constant yellow/amber
|LED red until firmware lstarted

LED blink fast red until ethernet link up

LED blink fast blue until Air Sync established

LED constant blue if Air Sync OK

|LED constant blue
|LED constant red
|----
|IP200/IP202
(red handset)
|alt key
|slow blink
|slow blink
|3
|5
|constant flash
|slow blink
|off
|constant flash
|----
|IP200A/IP210
(red handset)
|alt key
|slow blink
|fast blink
|3
|15
|slow flash
ca. 2 Hz
|on
|off
|blinking
|----
|IP110
(LED’s in F1 key)
|save key
|slow blink
|F1 off
|3
|10 - 15
|slow flash
ca. 2 Hz
|constant F1 flash
|off
|blinking
|----
|IP111
(MWI LED)
|home key
|
|
|
|
|
|
|
|
|----
|IP112
(MWI LED)
|home key
|
|
|
|
|
|
|
|
|----
|IP230
(menu key)
|menu key
|slow blink
|fast blink
|3
|10
|slow flash
ca. 2 Hz
|on
|off
|blinking
|----
|IP240
(menu key)
|menu key
|slow blink
|fast blink
|3
|10
|slow flash
ca. 2 Hz
|on
|off
|blinking
|----
|IP241
(menu key)
|alt key
|slow blink
|fast blink
|3
|10
|slow flash
ca. 2 Hz
|on
|off
|blinking
|----
|IP222
(MWI LED)
|ESC key
|slow blink
|fast blink
|3
|15
|slow flash
ca. 2 Hz
|on
|off
|blinking
|----
|IP232
(MWI LED)
|ESC key
|slow blink
|fast blink
|3
|15
|slow flash
ca. 2 Hz
|on
|off
|blinking

|}

== Related Articles ==
* [[Howto:How to use gwload]]
* [[Howto:How_to_Reset_IPXXX_(V10...)]]

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

Howto:How to Reset IPXXX (V10...)

2016-07-07T11:54:20Z

Lm ulm pk: /* More Information */

==Summary==
Different Reset Options of IPXXX

==Applies To==
This information applies to

* All innovaphone IP-Phones and -Gateways with V10 boot code or higher



==More Information==

Options for resetting innovaphone devices and LED pattern are described

If the factory reset was not successful please contact rma@innovaphone.com

or look at [[Howto:Get Access to Gateways if the Assistant don't boot the device.]]

===Reset options===
There are different options for resetting innovaphone devices, they can be selected by holding reset for a specific time.

{| border=1
!Time reset button pressed
!Action
!Remark
!..
|-
| <1s
| Reset to normal firmware
| This is the "short" reset
|-
| 1s..3s
| Reset to mini firmware
| This reset allows to recover from a bad firmware or a config causing problems with the normal firmware
|-
| 3s..6s
| Reset to TFTP mode for GWLoad
| Deprecated, use the minifirmware whenever possible for recovery.
|-
| >6s
| Reset to factory default, enter TFTP mode for GWLoad
|
|}

Please note: a ''Reset to factory default'' will '''erase all content from a ''Flash Disk''''' (<code>/DRIVE/FLASH</code>). However, it will not touch the content of a CF-Card or SSD (<code>/DRIVE/CF0</code>).

===LED-Patterns===

On the Gateways the ready LED can be red, green or orange.
On the Phones the MWI LED or the F1 LED on IP110 is used as ready LED during startup.

{| border=1
!State
!Gateway LED-Pattern
!Phone LED-Pattern and Display
!Remark
|-
| Reset pressed
| Ready LED is blinking green 3 times per second
| MWI or F1 LED is blinking 3 times per second
| After 2 seconds and after 6s the on time of the LED is 666ms instead of 333ms.
|-
| Firmware or Minifirmware starting
| Ready LED is red
| MWI or F1 LED is red
| Firmware starting takes a few seconds
|-
| Firmware running
| Ready LED is green<br>Ready LED is blinking red
| MWI or F1 LED depending on the phone state
| If the ready LED is blinking red a hardware module could not be initialized, a trace shows more details.
|-
| Minifirmware running
| Ready LED is blinking green for 900ms on and red for 100ms
| Minifirmware message is shown on the Display
|
|-
| Firmware update
| Ready LED is fast flashing green, 25 times per second
| Firmware update message is shown on the Display
| Do not interrupt a firmware update!
|-
| TFTP mode
| Ready LED is orange
| MWI or F1 LED is blinking green every 2seconds for 40ms
| TFTP mode is deprecated, use minifirmware for recovery whenever possible
|-
| Clear config
| Ready LED is fast flashing green, 25 times per second
| MWI or F1 LED is fast flashing red, 25 times per second
| Reseting to factory default needs up to 60 seconds, especially on devices with large flash like IP6010
|}

IP1202 uses a 3 color LED and uses instead of green on the other gateway blue.
When the firmware is running some more states are signaled with the LED:
* LED blink fast red until ethernet link up
* LED blink fast blue until Air Sync established
* LED constant blue if Air Sync OK

===Keys===

On the gateway the reset button is a dedicated button.
On the phones one of the keys functions during poweron as reset button. During normal operation the key works not as reset button.
That means to activate the reset you need to poweron the phone (or trigger a reset on the webinterface) while pressing the phones reset key.

{| border=1
!Phone
!Key
!Remark
|-
| IP110
| Save-Key
|-
| IP111<br>IP112
| Home-Key
|-
| IP200 <br>
| Alt-Key
|-
| IP230<br>IP240<br>IP241
| Menu-Key
|-
| IP222<br>IP232
| ESC-Key
|}

== Related Articles ==
* [[Howto:How to use gwload]]
* [[Howto:How_to_Reset_IPXXX]]

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

Howto:Get Access to Gateways if the Assistant doesn't boot the Device

2016-07-07T11:53:00Z

Lm ulm pk: New page: ==Applies To== concerns * IP 811, V11, V12 (at least observed here) <!-- Keywords: enter keywords, foreign translations and/or synoyms not appearing in the article here for better search ...

==Applies To==
concerns
* IP 811, V11, V12 (at least observed here)



==More Information==
A gateway should reboot after ending the setup-assistant. Sometimes that will not happen.
I have seen such behavior at a IP811 after uploading the last v12 rc1 after the factory
reset, i.e. pressing the reset-button long until the led flashes green and quick, wait
until led turns red and powercyle the device.

A manual reboot (powercyle) won't help here. The Assistant will be shown again.

A booting with sending a !boot (<nowiki>http://<ip of gateway>/!boot</nowiki> ) ends in an nonreacting http-Server.
It is still there but has no content.

Dealing with the !tftp mode and gwload to update firmware or bootcode doesn't help either.

But you can get access to part of the gateway's webgui when calling

'''<nowiki>http://<ip of gateway>/CMD0/mod_cmd.xml?cmd=xml-modes&menu=maintenance.xml&xsl=tab.xsl&help=Maintenance</nowiki>'''
in your webbrowser.
This will show the part of the gui where you can deal with firmware bootcode and config.

Downloading the config, editing the config in the line with

'''config change HTTP0 /home SETUP/wizard.xml'''

to

'''config change HTTP0'''

and upload it to the gateway with a reboot afterwards will lead to a reacting WebGui.

I couldn't find an appropriate '''!mod cmd syntax''' for it but it may exist.

== Related Articles ==

*[[Howto:How to Reset IPXXX (V10...)]]
*[[Howto:How to Reset IPXXX]]