https://wiki.innovaphone.com/api.php?action=feedcontributions&feedformat=atom&user=TE-SYSTEMS+GmbH 2026-05-10T02:24:53Z User contributions MediaWiki 1.42.3 https://wiki.innovaphone.com/index.php?title=Howto8:AgenTel_-_Voxtron_-_3rd_Party_Product&diff=18026 2010-06-29T09:30:12Z

<p>TE-SYSTEMS GmbH: /* Version */</p> <hr /> <div>[[Image:Template-COMPAT_01.gif|right]]<br /> <br /> <br /> ==Product name==<br /> [http://www.voxtron.com/dnn514/Default.aspx?tabid=61#agenTel agenTel]<br /> <br /> ==Certification Status==<br /> &lt;!-- by inno<br /> - uncomment one of the stati below <br /> - update date below<br /> --&gt;<br /> {{Template:Compat Status &quot;certified&quot;|certificate=AgenTel - Voxtron - 3rd Party Product_-_Desc-agenTel-cert.pdf}}<br /> <br /> Testing of this product has been finalized May 10th, 2006.<br /> <br /> ==Category==<br /> <br /> {{Category:RecProd Call Center Applications}}<br /> [[Category:RecProd|{{PAGENAME}}]]<br /> [[Category:RecProd Call Center Applications|{{PAGENAME}}]]<br /> <br /> ==Functions==<br /> Call Center Solution incl. ACD- and IVR-System, Statistics, Wallboard, VoiceMail and SMS<br /> <br /> ==Version==<br /> AgenTel 5.1 SP3<br /> <br /> Axxium 5 SP6<br /> <br /> [[Howto:XCAPI|XCAPI]] 2.2.62.0<br /> <br /> ==Vendor==<br /> [http://www.voxtron.com/de/default.asp Voxtron Europe N.V.]<br /> <br /> ==Description==<br /> Call Center functionality within your reach - use efficient call center technology without investing into cost-intensive systems.<br /> <br /> Route your incoming calls in an intelligent and efficient way, straight to the right person.<br /> <br /> agenTel is a software-based inbound call center solution that offers you the opportunity to use call center technology in a cost-efficient way. No need to invest in expensive call center software, intended for very large groups of agents.<br /> <br /> Voxtron's agenTel is a flexible and easy-to-use solution that fulfils the need of companies that want to route their incoming calls in an intelligent and efficient way, straight to the right person. agenTel is aimed at helping companies achieve a high degree of quality in customer interaction via telephone and develop and manage profitable customer relationships over time.<br /> <br /> Before the call is connected to an agent, specific information about the caller such as calling number (CLIP), customer number, etc., is collected. In addition, the choices made by the caller in the predefined menu (e.g. language preference) are collected. All this data is used to decide how to route the call. When nobody is able to answer the call immediately, the caller can leave a voice-mail message. In this way, agenTel can answer your calls 24 hours a day, 7 days a week, without having to maintain staff around the clock. You can personalize the waiting time to a large extent, with music and messages chosen for that particular customer.<br /> <br /> ==Pricing==<br /> 450 € per employee and IVR-/ACD channel<br /> <br /> ==Contact==<br /> &lt;!-- by vendor:<br /> - add name, address, phone, fax, email, web of primary recommended sales contact<br /> if suitable, you may consider specifying several contacs, depending on your sales structure <br /> (e.g. by country or vertical market)<br /> --&gt;<br /> <br /> {|<br /> | colspan=99 | Voxtron GmbH<br /> |-<br /> | Tel: || +49 238298974-0<br /> |-<br /> | Mail: || [mailto:verkauf@voxtron.de verkauf@voxtron.de]<br /> |-<br /> | Internet: || [http://www.voxtron.com/dnn514.de/Default.aspx?tabid=122 Voxtron contact page]<br /> |}<br /> <br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:Teleserver_Mobile_Pro_-_Speech_Design_-_3rd_Party_Product&diff=18025 2010-06-29T09:29:58Z

<p>TE-SYSTEMS GmbH: /* Version */</p> <hr /> <div>[[Image:Template-COMPAT_01.gif|right]]<br /> <br /> <br /> ==Product name==<br /> [http://www.speech-design.com/en/products/teleserver-mobile-pro/overview/ SPEECH DESIGN Teleserver Mobile Pro]<br /> <br /> ==Certification Status==<br /> &lt;!-- by inno<br /> - uncomment one of the stati below <br /> - update date below<br /> --&gt;<br /> {{Template:Compat Status &quot;certified&quot;|certificate=Teleserver_Mobile_Pro_-_Speech_Design_-_3rd_Party_Product_-_Desc-mobilepro-cert.pdf}}<br /> <br /> Testing of this product has been finalized November 28th, 2005.<br /> <br /> ==Category==<br /> <br /> {{Category:RecProd Solutions for Mobile Extensions}}<br /> [[Category:RecProd|{{PAGENAME}}]]<br /> [[Category:RecProd Solutions for Mobile Extensions|{{PAGENAME}}]]<br /> <br /> ==Functions==<br /> The Teleserver Mobile Pro is a Mobility Solution (Fix-Mobile-Convergence). That enables Mobile Phones for use with existing PBXs.<br /> <br /> ==Version==<br /> Version (TUI) 3.00 E09<br /> <br /> [[Howto:XCAPI|XCAPI]] 2.2.46<br /> <br /> ==Vendor==<br /> [http://www.speech-design.com/en/ SPEECH DESIGN GmbH]<br /> <br /> ==Description==<br /> Use your mobile with internal extension functions (transfer, consultation, hold/retrieve and conference)<br /> <br /> * One-Number-Service (reachable with on number)<br /> * Voice Mail-Funktion (one voicemailbox for all voice messages)<br /> * use as &quot;DECT&quot; (unlimited GSM coverage)<br /> * record mobile calls<br /> * saving of costs (especially to foreign countries)<br /> <br /> ==Competitive Analysis==<br /> * open system, connectivity with many PBXs and unlimited ability to upgrade<br /> * easy to use with almost any mobile phone<br /> * Voicemail and Recording functions<br /> <br /> ==Remarks==<br /> <br /> [[Media:Teleserver_Mobile_Pro-Speech_Design-3rd_Party_Product-report.pdf | Testreport Teleserver Mobile Pro]]<br /> <br /> ==Pricing==<br /> About 250 Euro per User.<br /> <br /> ==Contact==<br /> <br /> {|<br /> | colspan=99 | Sales Saleshotline<br /> |-<br /> | Tel: || +49 (0) 89-89458-165<br /> |-<br /> | Mail: || [mailto:sales@speech-design.de sales@speech-design.de ]<br /> |-<br /> | Internet: || http://www.speech-design.com/en/<br /> |}<br /> <br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:IXI-UMS_Unified_Messaging_Server_-_Servonic_-_3rd_Party_Product&diff=18024 2010-06-29T09:29:41Z

<p>TE-SYSTEMS GmbH: /* Version */</p> <hr /> <div>[[Image:Template-COMPAT_01.gif|right]]<br /> <br /> <br /> ==Product name==<br /> [http://www.servonic.com/DE_servonicFrame.php3?URL1=/products/EN_um-index.php3 IXI-UMS Unified Messaging Server (Full Version)]<br /> <br /> ==Certification Status==<br /> &lt;!-- by inno<br /> - uncomment one of the stati below <br /> - update date below<br /> --&gt;<br /> {{Template:Compat Status &quot;certified&quot;|certificate=IXI-UMS Unified Messaging Server_-_Servonic_-_3rd_Party_Product_-_Desc-ixiums-cert.pdf}}<br /> <br /> Testing of this product has been finalized March 7th, 2005.<br /> <br /> ==Category==<br /> <br /> {{Category:RecProd CTI and UMS applications}}<br /> [[Category:RecProd|{{PAGENAME}}]]<br /> [[Category:RecProd CTI and UMS applications|{{PAGENAME}}]]<br /> <br /> ==Functions==<br /> Unified Messaging Server with FaxVoice MailSMS (Short Messaging Service)mobile access<br /> <br /> ==Version==<br /> IXI-UMS Unified Messaging Server 5.51<br /> <br /> [[Howto:XCAPI|XCAPI]] 2.0.15<br /> <br /> ==Vendor==<br /> [http://www.servonic.com/ serVonic Telekommunikationslösungen GmbH]<br /> <br /> ==Description==<br /> IXI-UMS is a unified messaging server software, that can be installed on Windows operating systems. The software consists of the components Kernel for the outward communication, Connectors for the integration into messaging systems like Microsoft Exchange (2003, 2000, 5.5), Lotus Notes/Domino, SMTP-based mail systems, SAP R/3 and the IXI-UMS services Fax, Voice, SMS; mobile access and MWI. The IXI-UMS services can be used out of the available groupware system, e.g. Microsoft Exchange, also without IXI-UMS client installation. Moreover, IXI-UMS Client Tools with fax printer driver, Auto fax as well as mail merge fax (based on the MS WinWord mail merge letter feature) are available. All the mail clients that support MAPI are supported, e.g. Outlook, Outlook Express, Netscape, Lotus Notes or other suitable SMTP-based mail systems. In Outlook and Lotus Notes, there is an additional fax-button and SMS-button. With IXI-UMS, the user has all sorts of messages at his disposal - in the messaging interface he is used to. Therewith, participants can send and receive faxes (fax group 3), use a voice box feature and send and receive short messages (SMS) with the service SMS (Short Messaging Service). IXI-UMS furthermore supports MWI (Message Waiting Indication). Therewith, the incoming of new messages in the inbox can be indicated at feature-added telephones. All sorts of messages (e-mails, faxes, short messages and voice mails) can be enquired by mobile phone with IXI-UMS. The client/server-architecture of the IXI-UMS software and the Kernel/Connector-concept provide a perfect integration into the groupware-systems. IXI-UMS does not require a separate data storage and a separate user maintenance. The data can be maintained e.g. in the Active Directory with or without schema-extension, a separate mail store is not necessary (Single Store architecture).<br /> <br /> ==Competitive Analysis==<br /> Connection with conventional PBX's via ISDN CAPI and with IP-based PBX's via H.323.Solution also runs with CITRIX MetaFrame, Windows Terminal Server.Basically: No extra client, client always is the client of the respective messaging system (e.g. Notes, Outlook, Netscape, others). Furthermore, there are professional Client Tools (enlargements to the Notes- or Outlook-Client). Professional rendering at the IXI-UMS Server, installation as a pure server-solution, without Client Tools. Or/and installation of the Client Tools or mixed installation. Very flexible. The effort for training and installation remains low. Completely and seamlessly integrated into the respective messaging platform via current standards - IXI-UMS directly works with their data bases and their administration. NO replication, neither of the data content, nor of the administrative data or parts of them. Slim solution with Single Store architecture. Maintenance of the data e.g. in the Active Directory possible with or without schema-extension. High stability. For extremely high demands on availability: Parallel operation. Modular and scalable for large and small projects. Transparent pricing structure, excellent price/performance ratio<br /> <br /> ==Pricing==<br /> Price graded according to the number of users, channels, connectors and services.<br /> <br /> ==Contact==<br /> Peter Muschkiet<br /> <br /> Tel: +49 8142 4799-15<br /> <br /> Mail: [mailto:p.muschkiet@servonic.de p.muschkiet@servonic.de]<br /> <br /> Internet: http://www.servonic.com/ <br /> <br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:Colloquium.IP_-_TE_Systems_-_3rd_Party_Product&diff=18023 2010-06-29T09:29:24Z

<p>TE-SYSTEMS GmbH: /* Version */</p> <hr /> <div>[[Image:Colloquium.IP_-_TE_Systems_-_3rd_Party_Product_1.PNG|right]]<br /> <br /> <br /> ==Product name==<br /> Colloquium.IP<br /> <br /> ==Certification Status==<br /> &lt;!-- by inno<br /> - uncomment one of the stati below <br /> - update date below<br /> --&gt;<br /> {{Template:Compat Status &quot;certified&quot;|certificate=Colloquium.IP_-_TE_Systems_-_3rd_Party_Product_-_Desc-colloquium-cert.pdf}}<br /> <br /> Testing of this product has been finalized July 12th, 2004.<br /> <br /> ==Category==<br /> <br /> {{Category:RecProd_IP_Voice_Conferencing_Systems}}<br /> [[Category:RecProd|{{PAGENAME}}]]<br /> [[Category:RecProd_IP_Voice_Conferencing_Systems|{{PAGENAME}}]]<br /> <br /> ==Functions==<br /> Scalable conference server,<br /> web interface,<br /> control (mute, disconnect, record)<br /> <br /> ==Version==<br /> TE-SYSTEMS ISDN Voice Build 331<br /> CAPI-DLL 1.3.2.0<br /> [[Howto:XCAPI|XCAPI]] 1.2.15.0<br /> <br /> ==Vendor==<br /> [http://www.te-systems.de/ TE-SYSTEMS GmbH]<br /> <br /> ==Description==<br /> <br /> '''Colloquium.IP - feature-set'''<br /> <br /> * Comfortable creation of conferences<br /> <br /> New conferences can be established using a webinterface. Date and time of the conference are defined and the participants to be invited are entered. The invitation of the participants takes place automatically through an email. By assigning a unique conference-id number the access of unauthorized participants is prevented.<br /> <br /> * Simple access by phone from everywhere<br /> <br /> The invited participants simply dial up the phone number of the conference server at the time of the conference, enter the assigned conference-id number and are immediately switched into the conference.<br /> <br /> * Optional conference control via webinterface<br /> <br /> As an option there is the possiblity to control the conference by an operator. He can manage various features of the conference and the participants over a web interface. Participants can be muted oder disconnected. Conferences can be recorded, or the number of participants be limited. After termination of a conference, it can be played back with the assigned conference-id number as many times as desired.<br /> <br /> ==Contact==<br /> <br /> {|<br /> | colspan=99 | Oliver Körber<br /> |-<br /> | colspan=99 | TE-SYSTEMS GmbH<br /> |-<br /> | Tel: || 0800-TESYSTEMS (83 797 83)<br /> |-<br /> | Mail: || [mailto:koerber@te-systems.de koerber@te-systems.de]<br /> |-<br /> | Internet: || http://www.te-systems.de/<br /> |}<br /> <br /> == Related Articles ==<br /> <br /> * [http://www.te-systems.de Vendor Site (German)]<br /> <br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:Colima_CTI_Office,_ACD_Server_-_Colima_-_3rd_Party_Product&diff=18022 2010-06-29T09:29:02Z

<p>TE-SYSTEMS GmbH: /* Version */</p> <hr /> <div>[[Image:Template-COMPAT_01.gif|right]]<br /> <br /> <br /> ==Product name==<br /> [http://www.colima.de/products/ACD/ACD_Server_Home.htm colima CTI Office, colima ACD Server]<br /> <br /> ==Certification Status==<br /> &lt;!-- by inno<br /> - uncomment one of the stati below <br /> - update date below<br /> --&gt;<br /> {{Template:Compat Status &quot;certified&quot;|certificate=Colima_CTI_Office,ACD_Server_-_Colima_-_3rd_Party_Product_-_Desc-colima-cert.pdf‎}}<br /> <br /> Testing of this product has been finalized April 18th, 2005.<br /> <br /> ==Category==<br /> <br /> {{Category:RecProd Call Center Applications}}<br /> [[Category:RecProd|{{PAGENAME}}]]<br /> [[Category:RecProd Call Center Applications|{{PAGENAME}}]]<br /> <br /> ==Functions==<br /> ACD, CTI, VoiceMail, Fax, Integrations-APIs<br /> <br /> ==Version==<br /> Version Colima Server 3.20 <br /> <br /> CAPI Server 5.09<br /> <br /> [[Howto:XCAPI|XCAPI]] 2.1.13.0<br /> <br /> ==Vendor==<br /> [http://www.colima.de/ colima communications GmbH]<br /> <br /> ==Description==<br /> '''Colima contact center solutions:''' <br /> * automated call distribution (ACD)<br /> * computer-telephony-integration (CTI)<br /> * VoiceMail- and Faxserver all in one<br /> * high scalability, easy to use, easy handling and administration over comfortable web frontends<br /> * large scale statistics and realtime reports<br /> * multi-client capable, multi location capable<br /> * full redundancy<br /> * itegration APIs for Lotus Notes, Outlook, SAP, Remedy, Tivoli, KHK aso.<br /> <br /> ==Competitive Analysis==<br /> * Easy to use<br /> * High flexibility<br /> * No script editing required: workflow changes on the fly with no failures<br /> * Optimal cost/performance ratio<br /> * Full smart migration support (works with every PBX)<br /> * Industy neutral<br /> <br /> ==Pricing==<br /> Starting at 5.000,- €<br /> <br /> ==Contact==<br /> &lt;!-- by vendor:<br /> - add name, address, phone, fax, email, web of primary recommended sales contact<br /> if suitable, you may consider specifying several contacs, depending on your sales structure <br /> (e.g. by country or vertical market)<br /> --&gt;<br /> <br /> {|<br /> | colspan=99 | Matthias Friedrichs<br /> |-<br /> | Tel: || +49 (3943) 2628-31<br /> |-<br /> | Fax: || +49 (3943) 2628-32<br /> |-<br /> | Mail: || [mailto:mf@colima.de mf@colima.de ]<br /> |-<br /> | Internet: || http://www.colima.de/<br /> |}<br /> <br /> == Related Articles ==<br /> <br /> [http://www.colima.de/ vendor homepage (German)]<br /> <br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:IXI-UMS_sometimes_delivers_faxes_as_voicemails&diff=18021 2010-06-29T09:28:33Z

<p>TE-SYSTEMS GmbH: /* Applies To */</p> <hr /> <div>==Applies To==<br /> This information applies to<br /> <br /> * IXI-UMS (innovaphone edition) with VOIP-CAPI or [[Howto:XCAPI|XCAPI]] up to Kernel version 5.51 (newer versions are available but not tested yet - we will test them asap and let you know if there are any changes)<br /> <br /> ==More Information==<br /> <br /> Sometimes faxes are received as voicemails by IXI-UMS where you only hear the &quot;beep&quot; of the caller. This is mainly because of a timing problem. Some older faxes (analog faxes) do wait until the called party sends the fax tone and then sends it's fax tone itself. IXI waits for the calling party to send the fax tone for the first few seconds - when it the sends the tone, the callong fax answers but will be rejected, because the tone came to late.<br /> <br /> You have an easy possibility to overcome this issue: Simply go into the IXI Kernel Configuration, then again IXI-UMS Kernel Configuration, then &quot;DDI Mapping&quot; - there press &quot;add&quot; and type in the extension which should receive faxes only and select &quot;fax&quot; as service.<br /> <br /> This is a good way to receive all faxes, but has the drawback that now a combined number for Voicemail and Fax is not possible anymore! (So you better use that &quot;hack&quot; only if you have a global fax box, which you want to make sure will receive faxes sent to it.<br /> <br /> == Related Articles ==<br /> <br /> [[Howto:IXI-UMS_Unified_Messaging_Server_(Full_Version)|IXI-UMS (Full Version)]]<br /> <br /> [[Howto:Requirements_for_a_Server_to_install_and_run_IXI_UMS | IXI-UMS Server Requirements]]<br /> <br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Problem|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto7:ACHAT_-_Authensis_-_Call_Center_Application_Testreport&diff=18020 2010-06-29T09:28:15Z

<p>TE-SYSTEMS GmbH: /* XCAPI */</p> <hr /> <div>==Summary==<br /> The ACHAT ACD and call center solution consists of following modules:<br /> *Voice Route! module distributes all incoming calls<br /> *Work Route provides CTI functions and call information to call agents<br /> *Control Route shows informations about call distribution to supervisors<br /> *Voice4 as 3rd party module provides extended IVR functions<br /> <br /> Most tested scenarios except some CTI functions are supported by ACHAT and were successfully passed.<br /> <br /> ==Certification Status==<br /> <br /> &lt;!-- {{Template:Compat Status &quot;tested&quot;}} --&gt;<br /> &lt;!-- {{Template:Compat Status &quot;in progress&quot;}} --&gt;<br /> {{Template:Compat Status &quot;certified&quot;|certificate=ACHAT_-_Authensis_-_3rd_Party_Product_-_Desc-achat-cert.pdf}}<br /> &lt;!-- {{Template:Compat Status &quot;tested&quot;}} --&gt;<br /> &lt;!-- {{Template:Compat Status &quot;rejected&quot;}} --&gt;<br /> <br /> Testing of this product has been finalized December 10th, 2008.<br /> <br /> ==Version==<br /> work-route, control-route, admin-route:<br /> 8.03<br /> <br /> CSTA-Adapter:<br /> 2.24.0.0<br /> <br /> SOAP to CSTA Converter:<br /> 1.93.0.1<br /> <br /> ACHAT Server:<br /> 8.0.2<br /> <br /> X-CAPI:<br /> 3.3.36.0<br /> <br /> Ansagenserver:<br /> 1.17.4.6<br /> <br /> <br /> innovaphone Firmware:<br /> 6.00 sr2-hotfix6 08-60900.77<br /> 7.00 hotfix1 08-70300.06<br /> <br /> ==Test Setup==<br /> <br /> [[Image:ACHAT Authensis Testreport Testscenario.png]]<br /> <br /> <br /> ; M1 : Phone on Master PBX<br /> ; A1 : Agent 1 Phone<br /> ; A2 : Agent 2 Phone<br /> ; S1 : Phone on Slave PBX<br /> ; E1 : External Phone<br /> <br /> <br /> ===Connection to innovaphone PBX===<br /> SOAP to CSTA connector is a part of ACHAT and is used by ACHAT to monitor Waiting Queues and Agents.<br /> <br /> Media connection to the PBX is handled by X-CAPI and used by IVR module of ACHAT.<br /> <br /> ==Test Results==<br /> <br /> <br /> <br /> ===Basic Call===<br /> <br /> {| border=&quot;1&quot; <br /> !Tested feature<br /> !Result<br /> |----<br /> |E1 call service waiting queue, then talk to A1 || OK <br /> |----<br /> |S1 call service waiting queue, then talk to A1 || OK <br /> |----<br /> |M1 call service waiting queue, then talk to A1 || OK <br /> |}<br /> <br /> ===Call transfer===<br /> <br /> {| border=&quot;1&quot; <br /> !Tested feature<br /> !Result<br /> |----<br /> |E1 transfered with consultation by A1 to S1 || OK <br /> |----<br /> |E1 blind transfered by A1 to S1 || OK <br /> |----<br /> |If call in previous test not answered fallback to agent or watingqueue. || N/A <br /> |----<br /> |E1 transferred by A1 to A2 and back to waiting queue || OK<br /> |----<br /> |E1 blind transferred by A1 to A2 || OK<br /> |----<br /> |E1 transferred by A1 to M1 and back to waiting queue || OK<br /> |----<br /> |E1 blind transferred by A1 to M1 || OK<br /> |----<br /> |S1 transferred by A1 to E1 and back to waiting queue || OK<br /> |----<br /> |S1 blind transferred by A1 to E1 || OK<br /> |}<br /> <br /> ===Calls to Users with active Call Forward===<br /> {| border=&quot;1&quot; <br /> !Tested feature<br /> !Result<br /> |----<br /> |Agent calls user with call forward to service queue<br /> |OK<br /> |}<br /> <br /> ===CTI Functions of Call agent application===<br /> The ACHAT ''work-route'' application for call agents enables basic CTI functions.<br /> <br /> {| border=&quot;1&quot; <br /> !Tested feature<br /> !Ok?<br /> |-<br /> |Initiate outgoing call || OK<br /> |-<br /> |Accept incoming call || OK<br /> |-<br /> |End call || OK<br /> |-<br /> |Initiate consultation call || OK<br /> |-<br /> |End consultation call and switch back || OK<br /> |-<br /> |Swap between active call and call on hold || OK<br /> |-<br /> |Put on hold || OK<br /> |-<br /> |Conference || NOK<br /> |}<br /> <br /> 3-party conference is not available via CTI and usage of this function will disable the active call for CTI.<br /> <br /> ===IVR===<br /> IVR functions provided by 3rd party product Voice4 from TE-SYSTEMS. <br /> <br /> {| border=&quot;1&quot; <br /> !Tested feature<br /> !Ok?<br /> |-<br /> |Call to IVR announcement || OK<br /> |-<br /> |DTMF || OK<br /> |}<br /> <br /> ==Other Features==<br /> <br /> ===Directory===<br /> <br /> LDAP directory as phonebook is not supported.<br /> <br /> ==Configuration==<br /> <br /> ===innovaphone configuration===<br /> <br /> ACHAT server and innovaphone PBX are maintaining two active connections:<br /> <br /> *SOAP is used for call center application functions<br /> *H.323 registration of XCAPI for IVR functions<br /> <br /> Object names of waiting queues for announcement and busy counter in V7 PBX have to accomplish following requirements:<br /> *announce wqiting queue name have to begin with &quot;ansage&quot;<br /> *busy counter waiting queue have to begin with &quot;besetzt&quot;<br /> <br /> Upper/lower case is ignored.<br /> <br /> ====SOAP====<br /> SOAP configuration of the PBX is performed as usual: User Object placed in PBX group with active flag was used to init SOAP session. All Agents User Objects and Wating Queue objects are placed in this group.<br /> <br /> ====XCAPI====<br /> [[Howto:XCAPI|XCAPI]] was registered on user object on the PBX. No special configuration steps were performed.<br /> <br /> === 3rd party product configuration ===<br /> ACHAT is always installed and configured by Authensis technician.<br /> <br /> == Related Articles ==<br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:How_many_space_is_needed_to_store_MRS_voicemails%3F&diff=18019 2010-06-29T09:27:34Z

<p>TE-SYSTEMS GmbH: /* Performance */</p> <hr /> <div>== Summary==<br /> <br /> Performance and usability details for the MRS Voicemail system.<br /> <br /> ==More Information==<br /> ===HDD Requirements===<br /> <br /> Voicemails are stored with 8 bit, 8 kHz in .wav format. The bandwith is about 0,5 MByte per minute which is 30 MByte per hour.<br /> <br /> ===Performance===<br /> <br /> A fax traffic of 120 faxes shouldn’t be a problem fort he MRS. Depending on the connection of the MRS, with XCAPI or with built in T38, it’s limited by the [[Howto:XCAPI|XCAPI]].<br /> <br /> But 120 fax are also no problem for the XCAPI.<br /> <br /> ===Configurations===<br /> <br /> The MRS is able to recognize the diverting party number. That means that diverted calls are redirected to the mailbox of the diverting user.<br /> <br /> [[Category:Faq|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:How_to_connect_a_SPEECH_DESIGN_Teleserver_Mobile_Pro_to_an_innovaphone_PBX&diff=18018 2010-06-29T09:27:02Z

<p>TE-SYSTEMS GmbH: /* System Requirements */</p> <hr /> <div>SPEECH DESIGN has developed a Mobile Extension Solution which is certified with innovaphone PBXs. Here is the howto for the successful connection.<br /> <br /> ==Applies To==<br /> This information applies to<br /> <br /> * PBX, V5.01<br /> <br /> Build 05-5874 and later.<br /> <br /> ==More Information==<br /> ===Problem Details===<br /> ===System Requirements===<br /> [[Howto:XCAPI|XCAPI]] Version 2.2.46<br /> ISDN Voice III, build 337<br /> Teleserver Mobile Pro Version (TUI) 3.00 E 09<br /> innovaphone PBX<br /> <br /> ===Installation===<br /> The Teleserver will come preinstalled, just enter the several configurations and configure the options shown below.<br /> <br /> ===Configuration===<br /> ====innovaphone PBX====<br /> Create a new PBX Object and enter the values for the XCAPI registration. Choose “Location” as objecttype and enter an name (h323 alias), number and long name.<br /> <br /> ====XCAPI====<br /> In the XCAPI configuration set the following parameter:<br /> * Controller -&gt; Type -&gt; H323 -&gt; Tab: e164 Mapping<br /> ** enable both checkboxes<br /> ** enter “00” for international prefix<br /> ** enter “0” for national prefix<br /> * Controller -&gt; Type -&gt; H323 -&gt; Gatekeeper<br /> ** enter GK IP Address<br /> ** enter own extension or h323 alias (same as in PBX)<br /> * Controller -&gt; Type -&gt; Number filtering<br /> ** create one empty entry in “numbers from applications” and “numbers from network” with type “Telephone Number (e164)”<br /> <br /> ====SPEECH DESIGN Teleserver Mobile Pro====<br /> Log into the webinterface of the Teleserver Mobile Pro and configure the system parameters first. Enter your areacode and subscriber number as mentioned in the Teleserver Manual.<br /> <br /> Configure Users and function numbers as described by SPEECH DESIGN.<br /> <br /> == Related Articles ==<br /> [[Howto:Teleserver_Mobile_Pro_-_Speech_Design_-_3rd_Party_Product]]<br /> <br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> [[Category:Howto|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:MWI&diff=18017 2010-06-29T09:26:21Z

<p>TE-SYSTEMS GmbH: /* More Information */</p> <hr /> <div>==Summary==<br /> <br /> With the innovaphone phones you can use the MWI (Message Waiting Indication) feature via H.323.<br /> <br /> ==Applies To==<br /> This information applies to<br /> <br /> * all innovaphone IP phones with V6<br /> * all innovaphone V6 PBX<br /> * in a special scenario to all V5 innovaphone PBX<br /> <br /> ==More Information==<br /> The innovaphone Pbx is able to get an MWI message from the application (e.g Servonic ixi-ums, Auxxum ,Voice Mail system, ...) and post it to the innovaphone IP phones.<br /> <br /> If you use V5 PBX and V6 phones there is no message center in the PBX. So the application must send the MWI Message via H.450.7 .<br /> <br /> For example the Middleware [[Howto:XCAPI|XCAPI]] (TE-SYSTEMS GmbH) is able to send the MWI information via H.450.7. But then the application has to send the MWI message to the Xcapi via CAPI. The Xcapi will take the Capi information and send it via H.450.7 direct to the phones.<br /> <br /> If you have an application sending h.450.7 messages directly to a V5 Pbx – then the h.323 setup message has to contain the destination phone number, as also the h.450.7 message. If not the Pbx will not know where to send the MWI message.<br /> <br /> Having V6 Pbx – there is an MWI object in the PBX. You can now send the MWI message from the application to the PBX in 2 ways.<br /> <br /> '''1. method'''<br /> <br /> Via a h.450.7 message to The PBX – the message center will keep the MWI /ON –OFF information even if the Phone reboots – the message center will give the information again to the Phone – the MWI information won´t get lost.<br /> <br /> '''2. method'''<br /> <br /> Via DTMF tones to the MWI message center:<br /> <br /> *extension1 – MWI On (extension of the MWI object in the PBX)<br /> *extension2 –MWI Off (extension of the MWI object in the PBX)<br /> <br /> The MWI object (message center) in the PBX will then send a h.450.7 message to the phone.<br /> <br /> ===Problem Details===<br /> With V5 Pbx – there is no message center and so if an MWI is activated on one IP phone and this phone is rebooted, the MWI Message is lost.<br /> <br /> ===System Requirements===<br /> You must have V6 on the IP phones, if you want to have the MWI Feature. If you do not need a message center, you can work with V5 PBX.<br /> <br /> ===Configuration===<br /> Having a V5 PBX you don´t need to configure the Pbx, only the V6 phones. There you must configure for the used registration, a MWI function key.<br /> <br /> Having a V6 PBX – you can use the message center – configure an Message Waiting Object with name and/or number. In the MWI function key at the phone configure also these number and name that where used in the message center account.<br /> <br /> In yor application use the number and name of the MWI Object (Message Center).<br /> <br /> [[Category:Howto|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=18008 2010-06-28T14:32:03Z

<p>TE-SYSTEMS GmbH: </p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> <br /> == SIP ==<br /> === Configuring the innovaphone gateway ===<br /> In this example, we are going to use one PBX gateway object (XCAPI-SIP-GW) and two gateways (XCAPI-SIP-GW and XCAPI-SIP-GW-PBX). Only one gateway will communicate with the XCAPI via SIP, the other gateway and the gateway object in the PBX are simply for routing purposes between the innovaphone gateway and the PBX.<br /> <br /> ==== Creating a Gateway Object in the PBX ====<br /> Log in to the PBX administration and create a new gateway object. The name of the object is &quot;XCAPI-SIP-GW&quot;, and the number is 93 in this case.<br /> <br /> [[Image:2-pbx-gw-object-gw-4-config.PNG]]<br /> <br /> GW4, which we will create later in the gateway configuration, will register itself with this object and enables PBX objects to connect to the gateway with prefix 93.<br /> <br /> [[Image:1-pbx-gw-object-gw-4.PNG]]<br /> <br /> ==== Creating the gateways towards the XCAPI and PBX ====<br /> In the gateway administration, we will create two gateways: GW3, which will connect to the XCAPI via SIP, and GW4, which will be used for the outbound routing from the PBX towards the XCAPI.<br /> <br /> [[Image:3-gw-3-4.PNG]]<br /> <br /> Edit the settings of GW3 to use SIP, Gateway without Registration mode, and enter the IP address of the XCAPI server as Domain. As codecs, we select ITU.T G.711 a-Law with a framesize of 20 ms, and enable T.38 as fax codec. All other settings can use the default values.<br /> <br /> [[Image:4-gw3-config.PNG]]<br /> <br /> Add another gateway (GW4), but this time, register it with the local PBX. You can do so by selecting H.323 as protocol and Register as Gateway as mode. Enter 127.0.0.1 as Address and the name XCAPI-SIP-GW and 93 as number in the Alias List. This causes this gateway to register with the previously created gateway object in the PBX. This gateway should use the same codec settings as the XCAPI gateway.<br /> <br /> [[Image:5-gw4-config.PNG]]<br /> <br /> ==== Routing to and from the XCAPI gateway ====<br /> Create routes from GW3 (XCAPI) to all desired destinations (PSTN, PBX, the XCAPI itself if needed). In this example, we use 0 as prefix for PSTN access, 1 for PBX access, and 93 to route calls back to the XCAPI itself (normally, this is only required for testing purposes).<br /> <br /> [[Image:6-from-gw3-routes.PNG]]<br /> <br /> PBX users can access the XCAPI via the XCAPI gateway object in the PBX configuration, but their calls will be routed to GW4 (XCAPI-SIP-GW-PBX). For XCAPI access, we have to add a route from GW4 to GW3 (XCAPI). In this example, we route calls beginning with 93 to the XCAPI gateway.<br /> <br /> [[Image:7-from-gw4-route.PNG]]<br /> <br /> Here is an overview of the routes to the XCAPI. Calls from the PSTN, the XCAPI and the PBX can access the XCAPI via prefix 93.<br /> <br /> [[Image:8-to-gw3-routes.PNG]]<br /> <br /> === XCAPI Configuration ===<br /> When the XCAPI configuration is started for the first time, there are no configured controllers. Use the link &quot;Click here to add a controller&quot; in the overview page to start the controller wizard.<br /> <br /> [[Image:controller-wizard-0.PNG]]<br /> <br /> ==== Add new VoIP controller ====<br /> On the welcome page of the controller wizard, select to add a new VoIP controller.<br /> <br /> [[Image:controller-wizard-1.PNG]]<br /> <br /> ==== Network Interface ====<br /> In the next dialog, select the network interface that you want to use for the SIP connection between the XCAPI and the innovaphone gateway.<br /> <br /> [[Image:controller-wizard-2.PNG]]<br /> <br /> ==== Select VoIP environment template ====<br /> From the list of predefined VoIP environments, select a generic SIP template.<br /> <br /> [[Image:controller-wizard-3.PNG]]<br /> <br /> ==== Provide SIP user information ====<br /> The XCAPI is connected as a SIP trunk (gateway mode), so it is not necessary to enter any user information.<br /> <br /> [[Image:controller-wizard-4.PNG]]<br /> <br /> ==== Default SIP domain ====<br /> As default SIP domain, please enter the IP address of the innovaphone gateway. Please do not use any configured DNS hostnames because of interoperability reasons.<br /> <br /> [[Image:controller-wizard-5.PNG]]<br /> <br /> ==== Registrar and Proxy ====<br /> It is not necessary to activate the registrar or proxy function.<br /> <br /> [[Image:controller-wizard-6.PNG]]<br /> <br /> ==== STUN ====<br /> STUN functionality is also not required.<br /> <br /> [[Image:controller-wizard-7.PNG]]<br /> <br /> ==== Description and channels ====<br /> Enter a meaningful description and the number of lines that the XCAPI can use to communicate with the innovaphone gateway simultaneously. In this example, we enter the prefix number (81893) of the XCAPI as the description. This way, we always know which number to dial if we want to call the XCAPI. 818 is the trunk number of the PSTN access while 93 is the prefix from the innovaphone gateway routing.<br /> <br /> [[Image:controller-wizard-8.PNG]]<br /> <br /> ==== Confirmation ====<br /> Check if all necessary information has been entered correctly (green symbols on the left) and confirm all data by clicking Finish.<br /> <br /> [[Image:controller-wizard-9.PNG]]<br /> <br /> <br /> The new controller appears in the XCAPI configuration. Save the changes and stop all running CAPI applications before restarting them.<br /> <br /> [[Image:controller-wizard-10.PNG]]<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=18007 2010-06-28T14:30:26Z

<p>TE-SYSTEMS GmbH: /* Routing to and from the XCAPI gateway */</p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> <br /> == SIP ==<br /> === Configuring the innovaphone gateway ===<br /> In this example, we are going to use one PBX gateway object (XCAPI-SIP-GW) and two gateways (XCAPI-SIP-GW and XCAPI-SIP-GW-PBX). Only one gateway will communicate with the XCAPI via SIP, the other gateway and the gateway object in the PBX are simply for routing purposes between the innovaphone gateway and the PBX.<br /> <br /> ==== Creating a Gateway Object in the PBX ====<br /> Log in to the PBX administration and create a new gateway object. The name of the object is &quot;XCAPI-SIP-GW&quot;, and the number is 93 in this case. [[Image:2-pbx-gw-object-gw-4-config.PNG]]<br /> <br /> GW4, which we will create later in the gateway configuration, will register itself with this object and enables PBX objects to connect to the gateway with prefix 93. [[Image:1-pbx-gw-object-gw-4.PNG]]<br /> <br /> ==== Creating the gateways towards the XCAPI and PBX ====<br /> In the gateway administration, we will create two gateways: GW3, which will connect to the XCAPI via SIP, and GW4, which will be used for the outbound routing from the PBX towards the XCAPI.<br /> <br /> [[Image:3-gw-3-4.PNG]]<br /> <br /> Edit the settings of GW3 to use SIP, Gateway without Registration mode, and enter the IP address of the XCAPI server as Domain. As codecs, we select ITU.T G.711 a-Law with a framesize of 20 ms, and enable T.38 as fax codec. All other settings can use the default values.<br /> <br /> [[Image:4-gw3-config.PNG]]<br /> <br /> Add another gateway (GW4), but this time, register it with the local PBX. You can do so by selecting H.323 as protocol and Register as Gateway as mode. Enter 127.0.0.1 as Address and the name XCAPI-SIP-GW and 93 as number in the Alias List. This causes this gateway to register with the previously created gateway object in the PBX. This gateway should use the same codec settings as the XCAPI gateway.<br /> <br /> [[Image:5-gw4-config.PNG]]<br /> <br /> ==== Routing to and from the XCAPI gateway ====<br /> Create routes from GW3 (XCAPI) to all desired destinations (PSTN, PBX, the XCAPI itself if needed). In this example, we use 0 as prefix for PSTN access, 1 for PBX access, and 93 to route calls back to the XCAPI itself (normally, this is only required for testing purposes).<br /> <br /> [[Image:6-from-gw3-routes.PNG]]<br /> <br /> PBX users can access the XCAPI via the XCAPI gateway object in the PBX configuration, but their calls will be routed to GW4 (XCAPI-SIP-GW-PBX). For XCAPI access, we have to add a route from GW4 to GW3 (XCAPI). In this example, we route calls beginning with 93 to the XCAPI gateway.<br /> <br /> [[Image:7-from-gw4-route.PNG]]<br /> <br /> Here is an overview of the routes to the XCAPI. Calls from the PSTN, the XCAPI and the PBX can access the XCAPI via prefix 93.<br /> <br /> [[Image:8-to-gw3-routes.PNG]]<br /> <br /> === XCAPI Configuration ===<br /> When the XCAPI configuration is started for the first time, there are no configured controllers. Use the link &quot;Click here to add a controller&quot; in the overview page to start the controller wizard. [[Image:controller-wizard-0.PNG]]<br /> <br /> ==== Add new VoIP controller ====<br /> On the welcome page of the controller wizard, select to add a new VoIP controller. [[Image:controller-wizard-1.PNG]]<br /> <br /> ==== Network Interface ====<br /> In the next dialog, select the network interface that you want to use for the SIP connection between the XCAPI and the innovaphone gateway. [[Image:controller-wizard-2.PNG]]<br /> <br /> ==== Select VoIP environment template ====<br /> From the list of predefined VoIP environments, select a generic SIP template. [[Image:controller-wizard-3.PNG]]<br /> <br /> ==== Provide SIP user information ====<br /> The XCAPI is connected as a SIP trunk (gateway mode), so it is not necessary to enter any user information. [[Image:controller-wizard-4.PNG]]<br /> <br /> ==== Default SIP domain ====<br /> As default SIP domain, please enter the IP address of the innovaphone gateway. Please do not use any configured DNS hostnames because of interoperability reasons. [[Image:controller-wizard-5.PNG]]<br /> <br /> ==== Registrar and Proxy ====<br /> It is not necessary to activate the registrar or proxy function. [[Image:controller-wizard-6.PNG]]<br /> <br /> ==== STUN ====<br /> STUN functionality is also not required. [[Image:controller-wizard-7.PNG]]<br /> <br /> ==== Description and channels ====<br /> Enter a meaningful description and the number of lines that the XCAPI can use to communicate with the innovaphone gateway simultaneously. In this example, we enter the prefix number (81893) of the XCAPI as the description. This way, we always know which number to dial if we want to call the XCAPI. 818 is the trunk number of the PSTN access while 93 is the prefix from the innovaphone gateway routing. [[Image:controller-wizard-8.PNG]]<br /> <br /> ==== Confirmation ====<br /> Check if all necessary information has been entered correctly (green symbols on the left) and confirm all data by clicking Finish. [[Image:controller-wizard-9.PNG]]<br /> <br /> <br /> The new controller appears in the XCAPI configuration. Save the changes and stop all running CAPI applications before restarting them. [[Image:controller-wizard-10.PNG]]<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=18006 2010-06-28T14:30:00Z

<p>TE-SYSTEMS GmbH: /* Creating the gateways towards the XCAPI and PBX */</p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> <br /> == SIP ==<br /> === Configuring the innovaphone gateway ===<br /> In this example, we are going to use one PBX gateway object (XCAPI-SIP-GW) and two gateways (XCAPI-SIP-GW and XCAPI-SIP-GW-PBX). Only one gateway will communicate with the XCAPI via SIP, the other gateway and the gateway object in the PBX are simply for routing purposes between the innovaphone gateway and the PBX.<br /> <br /> ==== Creating a Gateway Object in the PBX ====<br /> Log in to the PBX administration and create a new gateway object. The name of the object is &quot;XCAPI-SIP-GW&quot;, and the number is 93 in this case. [[Image:2-pbx-gw-object-gw-4-config.PNG]]<br /> <br /> GW4, which we will create later in the gateway configuration, will register itself with this object and enables PBX objects to connect to the gateway with prefix 93. [[Image:1-pbx-gw-object-gw-4.PNG]]<br /> <br /> ==== Creating the gateways towards the XCAPI and PBX ====<br /> In the gateway administration, we will create two gateways: GW3, which will connect to the XCAPI via SIP, and GW4, which will be used for the outbound routing from the PBX towards the XCAPI.<br /> <br /> [[Image:3-gw-3-4.PNG]]<br /> <br /> Edit the settings of GW3 to use SIP, Gateway without Registration mode, and enter the IP address of the XCAPI server as Domain. As codecs, we select ITU.T G.711 a-Law with a framesize of 20 ms, and enable T.38 as fax codec. All other settings can use the default values.<br /> <br /> [[Image:4-gw3-config.PNG]]<br /> <br /> Add another gateway (GW4), but this time, register it with the local PBX. You can do so by selecting H.323 as protocol and Register as Gateway as mode. Enter 127.0.0.1 as Address and the name XCAPI-SIP-GW and 93 as number in the Alias List. This causes this gateway to register with the previously created gateway object in the PBX. This gateway should use the same codec settings as the XCAPI gateway.<br /> <br /> [[Image:5-gw4-config.PNG]]<br /> <br /> ==== Routing to and from the XCAPI gateway ====<br /> Create routes from GW3 (XCAPI) to all desired destinations (PSTN, PBX, the XCAPI itself if needed). In this example, we use 0 as prefix for PSTN access, 1 for PBX access, and 93 to route calls back to the XCAPI itself (normally, this is only required for testing purposes). [[Image:6-from-gw3-routes.PNG]]<br /> <br /> PBX users can access the XCAPI via the XCAPI gateway object in the PBX configuration, but their calls will be routed to GW4 (XCAPI-SIP-GW-PBX). For XCAPI access, we have to add a route from GW4 to GW3 (XCAPI). In this example, we route calls beginning with 93 to the XCAPI gateway. [[Image:7-from-gw4-route.PNG]]<br /> <br /> Here is an overview of the routes to the XCAPI. Calls from the PSTN, the XCAPI and the PBX can access the XCAPI via prefix 93. [[Image:8-to-gw3-routes.PNG]]<br /> <br /> === XCAPI Configuration ===<br /> When the XCAPI configuration is started for the first time, there are no configured controllers. Use the link &quot;Click here to add a controller&quot; in the overview page to start the controller wizard. [[Image:controller-wizard-0.PNG]]<br /> <br /> ==== Add new VoIP controller ====<br /> On the welcome page of the controller wizard, select to add a new VoIP controller. [[Image:controller-wizard-1.PNG]]<br /> <br /> ==== Network Interface ====<br /> In the next dialog, select the network interface that you want to use for the SIP connection between the XCAPI and the innovaphone gateway. [[Image:controller-wizard-2.PNG]]<br /> <br /> ==== Select VoIP environment template ====<br /> From the list of predefined VoIP environments, select a generic SIP template. [[Image:controller-wizard-3.PNG]]<br /> <br /> ==== Provide SIP user information ====<br /> The XCAPI is connected as a SIP trunk (gateway mode), so it is not necessary to enter any user information. [[Image:controller-wizard-4.PNG]]<br /> <br /> ==== Default SIP domain ====<br /> As default SIP domain, please enter the IP address of the innovaphone gateway. Please do not use any configured DNS hostnames because of interoperability reasons. [[Image:controller-wizard-5.PNG]]<br /> <br /> ==== Registrar and Proxy ====<br /> It is not necessary to activate the registrar or proxy function. [[Image:controller-wizard-6.PNG]]<br /> <br /> ==== STUN ====<br /> STUN functionality is also not required. [[Image:controller-wizard-7.PNG]]<br /> <br /> ==== Description and channels ====<br /> Enter a meaningful description and the number of lines that the XCAPI can use to communicate with the innovaphone gateway simultaneously. In this example, we enter the prefix number (81893) of the XCAPI as the description. This way, we always know which number to dial if we want to call the XCAPI. 818 is the trunk number of the PSTN access while 93 is the prefix from the innovaphone gateway routing. [[Image:controller-wizard-8.PNG]]<br /> <br /> ==== Confirmation ====<br /> Check if all necessary information has been entered correctly (green symbols on the left) and confirm all data by clicking Finish. [[Image:controller-wizard-9.PNG]]<br /> <br /> <br /> The new controller appears in the XCAPI configuration. Save the changes and stop all running CAPI applications before restarting them. [[Image:controller-wizard-10.PNG]]<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-10.PNG&diff=18005 2010-06-28T14:28:19Z

<p>TE-SYSTEMS GmbH: Well done, we are up and running.</p> <hr /> <div>Well done, we are up and running.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-9.PNG&diff=18004 2010-06-28T14:27:49Z

<p>TE-SYSTEMS GmbH: All symbols on the left are green? You are almost done. Any red &quot;X&quot; symbol? Go back and check your input.</p> <hr /> <div>All symbols on the left are green? You are almost done. Any red &quot;X&quot; symbol? Go back and check your input.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-8.PNG&diff=18003 2010-06-28T14:26:56Z

<p>TE-SYSTEMS GmbH: In the comment, we add the phone number of the XCAPI controller so we don&#039;t have to look it up in the routing table. In this example, the XCAPI can be called via 81893 (+ unlimited digits) from the PSTN or via 93 (+ unlimited digits) from the PBX. This c</p> <hr /> <div>In the comment, we add the phone number of the XCAPI controller so we don't have to look it up in the routing table. In this example, the XCAPI can be called via 81893 (+ unlimited digits) from the PSTN or via 93 (+ unlimited digits) from the PBX.<br /> <br /> This controller is capable of running 30 lines of SIP simultaneously (depends on the licence).</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-7.PNG&diff=18002 2010-06-28T14:24:44Z

<p>TE-SYSTEMS GmbH: There is no need for STUN requests if the XCAPI and the innovaphone gateway are running in the same local subnet.</p> <hr /> <div>There is no need for STUN requests if the XCAPI and the innovaphone gateway are running in the same local subnet.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-6.PNG&diff=18001 2010-06-28T14:23:50Z

<p>TE-SYSTEMS GmbH: We do not need any registrar or proxy functionality because the XCAPI is connected as a SIP trunk.</p> <hr /> <div>We do not need any registrar or proxy functionality because the XCAPI is connected as a SIP trunk.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-5.PNG&diff=18000 2010-06-28T14:22:59Z

<p>TE-SYSTEMS GmbH: Enter the IP address of the innovaphone gateway as default SIP domain. This is the address where the XCAPI will send all SIP requests to. Please do not use any DNS hostnames in this case because of interoperability issues.</p> <hr /> <div>Enter the IP address of the innovaphone gateway as default SIP domain. This is the address where the XCAPI will send all SIP requests to.<br /> Please do not use any DNS hostnames in this case because of interoperability issues.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-4.PNG&diff=17999 2010-06-28T14:22:00Z

<p>TE-SYSTEMS GmbH: The XCAPI is connected as a SIP trunk, so we don&#039;t need any user information for authentication.</p> <hr /> <div>The XCAPI is connected as a SIP trunk, so we don't need any user information for authentication.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-3.PNG&diff=17998 2010-06-28T14:21:24Z

<p>TE-SYSTEMS GmbH: Select a generic SIP template from the list of predefined VoIP environments.</p> <hr /> <div>Select a generic SIP template from the list of predefined VoIP environments.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-2.PNG&diff=17997 2010-06-28T14:20:47Z

<p>TE-SYSTEMS GmbH: Select the network interface that will be used for the SIP connection between the XCAPI and the innovaphone gateway.</p> <hr /> <div>Select the network interface that will be used for the SIP connection between the XCAPI and the innovaphone gateway.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-1.PNG&diff=17996 2010-06-28T14:20:05Z

<p>TE-SYSTEMS GmbH: Add a new VoIP controller with the controller wizard.</p> <hr /> <div>Add a new VoIP controller with the controller wizard.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=17995 2010-06-28T14:19:25Z

<p>TE-SYSTEMS GmbH: /* XCAPI Configuration */</p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> <br /> == SIP ==<br /> === Configuring the innovaphone gateway ===<br /> In this example, we are going to use one PBX gateway object (XCAPI-SIP-GW) and two gateways (XCAPI-SIP-GW and XCAPI-SIP-GW-PBX). Only one gateway will communicate with the XCAPI via SIP, the other gateway and the gateway object in the PBX are simply for routing purposes between the innovaphone gateway and the PBX.<br /> <br /> ==== Creating a Gateway Object in the PBX ====<br /> Log in to the PBX administration and create a new gateway object. The name of the object is &quot;XCAPI-SIP-GW&quot;, and the number is 93 in this case. [[Image:2-pbx-gw-object-gw-4-config.PNG]]<br /> <br /> GW4, which we will create later in the gateway configuration, will register itself with this object and enables PBX objects to connect to the gateway with prefix 93. [[Image:1-pbx-gw-object-gw-4.PNG]]<br /> <br /> ==== Creating the gateways towards the XCAPI and PBX ====<br /> In the gateway administration, we will create two gateways: GW3, which will connect to the XCAPI via SIP, and GW4, which will be used for the outbound routing from the PBX towards the XCAPI. [[Image:3-gw-3-4.PNG]]<br /> <br /> Edit the settings of GW3 to use SIP, Gateway without Registration mode, and enter the IP address of the XCAPI server as Domain. As codecs, we select ITU.T G.711 a-Law with a framesize of 20 ms, and enable T.38 as fax codec. All other settings can use the default values. [[Image:4-gw3-config.PNG]]<br /> <br /> Add another gateway (GW4), but this time, register it with the local PBX. You can do so by selecting H.323 as protocol and Register as Gateway as mode. Enter 127.0.0.1 as Address and the name XCAPI-SIP-GW and 93 as number in the Alias List. This causes this gateway to register with the previously created gateway object in the PBX. This gateway should use the same codec settings as the XCAPI gateway. [[Image:5-gw4-config.PNG]]<br /> <br /> ==== Routing to and from the XCAPI gateway ====<br /> Create routes from GW3 (XCAPI) to all desired destinations (PSTN, PBX, the XCAPI itself if needed). In this example, we use 0 as prefix for PSTN access, 1 for PBX access, and 93 to route calls back to the XCAPI itself (normally, this is only required for testing purposes). [[Image:6-from-gw3-routes.PNG]]<br /> <br /> PBX users can access the XCAPI via the XCAPI gateway object in the PBX configuration, but their calls will be routed to GW4 (XCAPI-SIP-GW-PBX). For XCAPI access, we have to add a route from GW4 to GW3 (XCAPI). In this example, we route calls beginning with 93 to the XCAPI gateway. [[Image:7-from-gw4-route.PNG]]<br /> <br /> Here is an overview of the routes to the XCAPI. Calls from the PSTN, the XCAPI and the PBX can access the XCAPI via prefix 93. [[Image:8-to-gw3-routes.PNG]]<br /> <br /> === XCAPI Configuration ===<br /> When the XCAPI configuration is started for the first time, there are no configured controllers. Use the link &quot;Click here to add a controller&quot; in the overview page to start the controller wizard. [[Image:controller-wizard-0.PNG]]<br /> <br /> ==== Add new VoIP controller ====<br /> On the welcome page of the controller wizard, select to add a new VoIP controller. [[Image:controller-wizard-1.PNG]]<br /> <br /> ==== Network Interface ====<br /> In the next dialog, select the network interface that you want to use for the SIP connection between the XCAPI and the innovaphone gateway. [[Image:controller-wizard-2.PNG]]<br /> <br /> ==== Select VoIP environment template ====<br /> From the list of predefined VoIP environments, select a generic SIP template. [[Image:controller-wizard-3.PNG]]<br /> <br /> ==== Provide SIP user information ====<br /> The XCAPI is connected as a SIP trunk (gateway mode), so it is not necessary to enter any user information. [[Image:controller-wizard-4.PNG]]<br /> <br /> ==== Default SIP domain ====<br /> As default SIP domain, please enter the IP address of the innovaphone gateway. Please do not use any configured DNS hostnames because of interoperability reasons. [[Image:controller-wizard-5.PNG]]<br /> <br /> ==== Registrar and Proxy ====<br /> It is not necessary to activate the registrar or proxy function. [[Image:controller-wizard-6.PNG]]<br /> <br /> ==== STUN ====<br /> STUN functionality is also not required. [[Image:controller-wizard-7.PNG]]<br /> <br /> ==== Description and channels ====<br /> Enter a meaningful description and the number of lines that the XCAPI can use to communicate with the innovaphone gateway simultaneously. In this example, we enter the prefix number (81893) of the XCAPI as the description. This way, we always know which number to dial if we want to call the XCAPI. 818 is the trunk number of the PSTN access while 93 is the prefix from the innovaphone gateway routing. [[Image:controller-wizard-8.PNG]]<br /> <br /> ==== Confirmation ====<br /> Check if all necessary information has been entered correctly (green symbols on the left) and confirm all data by clicking Finish. [[Image:controller-wizard-9.PNG]]<br /> <br /> <br /> The new controller appears in the XCAPI configuration. Save the changes and stop all running CAPI applications before restarting them. [[Image:controller-wizard-10.PNG]]<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:Controller-wizard-0.PNG&diff=17994 2010-06-28T14:18:50Z

<p>TE-SYSTEMS GmbH: XCAPI configuration without VoIP controllers. Start the Controller Wizard to add a new controller.</p> <hr /> <div>XCAPI configuration without VoIP controllers. Start the Controller Wizard to add a new controller.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=17993 2010-06-28T14:18:06Z

<p>TE-SYSTEMS GmbH: </p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> <br /> == SIP ==<br /> === Configuring the innovaphone gateway ===<br /> In this example, we are going to use one PBX gateway object (XCAPI-SIP-GW) and two gateways (XCAPI-SIP-GW and XCAPI-SIP-GW-PBX). Only one gateway will communicate with the XCAPI via SIP, the other gateway and the gateway object in the PBX are simply for routing purposes between the innovaphone gateway and the PBX.<br /> <br /> ==== Creating a Gateway Object in the PBX ====<br /> Log in to the PBX administration and create a new gateway object. The name of the object is &quot;XCAPI-SIP-GW&quot;, and the number is 93 in this case. [[Image:2-pbx-gw-object-gw-4-config.PNG]]<br /> <br /> GW4, which we will create later in the gateway configuration, will register itself with this object and enables PBX objects to connect to the gateway with prefix 93. [[Image:1-pbx-gw-object-gw-4.PNG]]<br /> <br /> ==== Creating the gateways towards the XCAPI and PBX ====<br /> In the gateway administration, we will create two gateways: GW3, which will connect to the XCAPI via SIP, and GW4, which will be used for the outbound routing from the PBX towards the XCAPI. [[Image:3-gw-3-4.PNG]]<br /> <br /> Edit the settings of GW3 to use SIP, Gateway without Registration mode, and enter the IP address of the XCAPI server as Domain. As codecs, we select ITU.T G.711 a-Law with a framesize of 20 ms, and enable T.38 as fax codec. All other settings can use the default values. [[Image:4-gw3-config.PNG]]<br /> <br /> Add another gateway (GW4), but this time, register it with the local PBX. You can do so by selecting H.323 as protocol and Register as Gateway as mode. Enter 127.0.0.1 as Address and the name XCAPI-SIP-GW and 93 as number in the Alias List. This causes this gateway to register with the previously created gateway object in the PBX. This gateway should use the same codec settings as the XCAPI gateway. [[Image:5-gw4-config.PNG]]<br /> <br /> ==== Routing to and from the XCAPI gateway ====<br /> Create routes from GW3 (XCAPI) to all desired destinations (PSTN, PBX, the XCAPI itself if needed). In this example, we use 0 as prefix for PSTN access, 1 for PBX access, and 93 to route calls back to the XCAPI itself (normally, this is only required for testing purposes). [[Image:6-from-gw3-routes.PNG]]<br /> <br /> PBX users can access the XCAPI via the XCAPI gateway object in the PBX configuration, but their calls will be routed to GW4 (XCAPI-SIP-GW-PBX). For XCAPI access, we have to add a route from GW4 to GW3 (XCAPI). In this example, we route calls beginning with 93 to the XCAPI gateway. [[Image:7-from-gw4-route.PNG]]<br /> <br /> Here is an overview of the routes to the XCAPI. Calls from the PSTN, the XCAPI and the PBX can access the XCAPI via prefix 93. [[Image:8-to-gw3-routes.PNG]]<br /> <br /> === XCAPI Configuration ===<br /> When the XCAPI configuration is started for the first time, there are no configured controllers. Use the link in the overview page to start the controller wizard. [[Image:controller-wizard-0.PNG]]<br /> <br /> ==== Add new VoIP controller ====<br /> On the welcome page of the controller wizard, select to add a new VoIP controller. [[Image:controller-wizard-1.PNG]]<br /> <br /> ==== Network Interface ====<br /> In the next dialog, select the network interface that you want to use for the SIP connection between the XCAPI and the innovaphone gateway. [[Image:controller-wizard-2.PNG]]<br /> <br /> ==== Select VoIP environment template ====<br /> From the list of predefined VoIP environments, select a generic SIP template. [[Image:controller-wizard-3.PNG]]<br /> <br /> ==== Provide SIP user information ====<br /> The XCAPI is connected as a SIP trunk (gateway mode), so it is not necessary to enter any user information. [[Image:controller-wizard-4.PNG]]<br /> <br /> ==== Default SIP domain ====<br /> As default SIP domain, please enter the IP address of the innovaphone gateway. Please do not use any configured DNS hostnames because of interoperability reasons. [[Image:controller-wizard-5.PNG]]<br /> <br /> ==== Registrar and Proxy ====<br /> It is not necessary to activate the registrar or proxy function. [[Image:controller-wizard-6.PNG]]<br /> <br /> ==== STUN ====<br /> STUN functionality is also not required. [[Image:controller-wizard-7.PNG]]<br /> <br /> ==== Description and channels ====<br /> Enter a meaningful description and the number of lines that the XCAPI can use to communicate with the innovaphone gateway simultaneously. In this example, we enter the prefix number (81893) of the XCAPI as the description. This way, we always know which number to dial if we want to call the XCAPI. 818 is the trunk number of the PSTN access while 93 is the prefix from the innovaphone gateway routing. [[Image:controller-wizard-8.PNG]]<br /> <br /> ==== Confirmation ====<br /> Check if all necessary information has been entered correctly (green symbols on the left) and confirm all data by clicking Finish. [[Image:controller-wizard-9.PNG]]<br /> <br /> <br /> The new controller appears in the XCAPI configuration. Save the changes and stop all running CAPI applications before restarting them. [[Image:controller-wizard-10.PNG]]<br /> <br /> <br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:8-to-gw3-routes.PNG&diff=17992 2010-06-28T13:51:25Z

<p>TE-SYSTEMS GmbH: Various interfaces (PSTN, PBX) route to the XCAPI SIP trunk via prefix 93.</p> <hr /> <div>Various interfaces (PSTN, PBX) route to the XCAPI SIP trunk via prefix 93.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:7-from-gw4-route.PNG&diff=17991 2010-06-28T13:50:30Z

<p>TE-SYSTEMS GmbH: The route from GW4 (accessed by local PBX users via prefix 93) leads to GW3, the XCAPI SIP trunk.</p> <hr /> <div>The route from GW4 (accessed by local PBX users via prefix 93) leads to GW3, the XCAPI SIP trunk.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:6-from-gw3-routes.PNG&diff=17990 2010-06-28T13:49:27Z

<p>TE-SYSTEMS GmbH: Overview of the routes from GW3 (the XCAPI SIP trunk) to PSTN and PBX.</p> <hr /> <div>Overview of the routes from GW3 (the XCAPI SIP trunk) to PSTN and PBX.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:5-gw4-config.PNG&diff=17989 2010-06-28T13:48:19Z

<p>TE-SYSTEMS GmbH: GW4 uses H.323 to register with the gateway object in the local PBX.</p> <hr /> <div>GW4 uses H.323 to register with the gateway object in the local PBX.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:4-gw3-config.PNG&diff=17988 2010-06-28T13:47:38Z

<p>TE-SYSTEMS GmbH: Configuration of GW3, the SIP trunk towards the XCAPI.</p> <hr /> <div>Configuration of GW3, the SIP trunk towards the XCAPI.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:3-gw-3-4.PNG&diff=17987 2010-06-28T13:46:57Z

<p>TE-SYSTEMS GmbH: Overview of the gateways in the gateway administration. GW3 is connected to the XCAPI via SIP, GW4 is registered with the local PBX via H.323.</p> <hr /> <div>Overview of the gateways in the gateway administration. GW3 is connected to the XCAPI via SIP, GW4 is registered with the local PBX via H.323.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:1-pbx-gw-object-gw-4.PNG&diff=17986 2010-06-28T13:45:25Z

<p>TE-SYSTEMS GmbH: Configured gateway object in the PBX for routing calls from the PBX to the XCAPI SIP gateway. A local H.323 gateway (GW4) is registered with this object.</p> <hr /> <div>Configured gateway object in the PBX for routing calls from the PBX to the XCAPI SIP gateway. A local H.323 gateway (GW4) is registered with this object.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=17985 2010-06-28T13:44:26Z

<p>TE-SYSTEMS GmbH: /* Creating a Gateway Object in the PBX */</p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> <br /> == SIP ==<br /> === Configuring the innovaphone gateway ===<br /> In this example, we are going to use one PBX gateway object (XCAPI-SIP-GW) and two gateways (XCAPI-SIP-GW and XCAPI-SIP-GW-PBX). Only one gateway will communicate with the XCAPI via SIP, the other gateway and the gateway object in the PBX are simply for routing purposes between the innovaphone gateway and the PBX.<br /> <br /> ==== Creating a Gateway Object in the PBX ====<br /> Log in to the PBX administration and create a new gateway object. The name of the object is &quot;XCAPI-SIP-GW&quot;, and the number is 93 in this case. [[Image:2-pbx-gw-object-gw-4-config.PNG]]<br /> <br /> GW4, which we will create later in the gateway configuration, will register itself with this object and enables PBX objects to connect to the gateway with prefix 93. [[Image:1-pbx-gw-object-gw-4.PNG]]<br /> <br /> ==== Creating the gateways towards the XCAPI and PBX ====<br /> In the gateway administration, we will create two gateways: GW3, which will connect to the XCAPI via SIP, and GW4, which will be used for the outbound routing from the PBX towards the XCAPI. [[Image:3-gw-3-4.PNG]]<br /> <br /> Edit the settings of GW3 to use SIP, Gateway without Registration mode, and enter the IP address of the XCAPI server as Domain. As codecs, we select ITU.T G.711 a-Law with a framesize of 20 ms, and enable T.38 as fax codec. All other settings can use the default values. [[Image:4-gw3-config.PNG]]<br /> <br /> Add another gateway (GW4), but this time, register it with the local PBX. You can do so by selecting H.323 as protocol and Register as Gateway as mode. Enter 127.0.0.1 as Address and the name XCAPI-SIP-GW and 93 as number in the Alias List. This causes this gateway to register with the previously created gateway object in the PBX. This gateway should use the same codec settings as the XCAPI gateway. [[Image:5-gw4-config.PNG]]<br /> <br /> ==== Routing to and from the XCAPI gateway ====<br /> Create routes from GW3 (XCAPI) to all desired destinations (PSTN, PBX, the XCAPI itself if needed). In this example, we use 0 as prefix for PSTN access, 1 for PBX access, and 93 to route calls back to the XCAPI itself (normally, this is only required for testing purposes). [[Image:6-from-gw3-routes.PNG]]<br /> <br /> PBX users can access the XCAPI via the XCAPI gateway object in the PBX configuration, but their calls will be routed to GW4 (XCAPI-SIP-GW-PBX). For XCAPI access, we have to add a route from GW4 to GW3 (XCAPI). In this example, we route calls beginning with 93 to the XCAPI gateway. [[Image:7-from-gw4-route.PNG]]<br /> <br /> Here is an overview of the routes to the XCAPI. Calls from the PSTN, the XCAPI and the PBX can access the XCAPI via prefix 93. [[Image:8-to-gw3-routes.PNG]]<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=File:2-pbx-gw-object-gw-4-config.PNG&diff=17984 2010-06-28T13:44:02Z

<p>TE-SYSTEMS GmbH: Gateway object in the PBX for routing calls from the PBX to the XCAPI SIP gateway.</p> <hr /> <div>Gateway object in the PBX for routing calls from the PBX to the XCAPI SIP gateway.</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=17983 2010-06-28T13:42:54Z

<p>TE-SYSTEMS GmbH: </p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> <br /> == SIP ==<br /> === Configuring the innovaphone gateway ===<br /> In this example, we are going to use one PBX gateway object (XCAPI-SIP-GW) and two gateways (XCAPI-SIP-GW and XCAPI-SIP-GW-PBX). Only one gateway will communicate with the XCAPI via SIP, the other gateway and the gateway object in the PBX are simply for routing purposes between the innovaphone gateway and the PBX.<br /> <br /> ==== Creating a Gateway Object in the PBX ====<br /> Log in to the PBX administration and create a new gateway object. The name of the object is &quot;XCAPI-SIP-GW&quot;, and the number is 93 in this case. [[Image:2-pbx-gw-object-gw-4-config.PNG]]<br /> GW4, which we will create later in the gateway configuration, will register itself with this object and enables PBX objects to connect to the gateway with prefix 93. [[Image:1-pbx-gw-object-gw-4.PNG]]<br /> <br /> ==== Creating the gateways towards the XCAPI and PBX ====<br /> In the gateway administration, we will create two gateways: GW3, which will connect to the XCAPI via SIP, and GW4, which will be used for the outbound routing from the PBX towards the XCAPI. [[Image:3-gw-3-4.PNG]]<br /> <br /> Edit the settings of GW3 to use SIP, Gateway without Registration mode, and enter the IP address of the XCAPI server as Domain. As codecs, we select ITU.T G.711 a-Law with a framesize of 20 ms, and enable T.38 as fax codec. All other settings can use the default values. [[Image:4-gw3-config.PNG]]<br /> <br /> Add another gateway (GW4), but this time, register it with the local PBX. You can do so by selecting H.323 as protocol and Register as Gateway as mode. Enter 127.0.0.1 as Address and the name XCAPI-SIP-GW and 93 as number in the Alias List. This causes this gateway to register with the previously created gateway object in the PBX. This gateway should use the same codec settings as the XCAPI gateway. [[Image:5-gw4-config.PNG]]<br /> <br /> ==== Routing to and from the XCAPI gateway ====<br /> Create routes from GW3 (XCAPI) to all desired destinations (PSTN, PBX, the XCAPI itself if needed). In this example, we use 0 as prefix for PSTN access, 1 for PBX access, and 93 to route calls back to the XCAPI itself (normally, this is only required for testing purposes). [[Image:6-from-gw3-routes.PNG]]<br /> <br /> PBX users can access the XCAPI via the XCAPI gateway object in the PBX configuration, but their calls will be routed to GW4 (XCAPI-SIP-GW-PBX). For XCAPI access, we have to add a route from GW4 to GW3 (XCAPI). In this example, we route calls beginning with 93 to the XCAPI gateway. [[Image:7-from-gw4-route.PNG]]<br /> <br /> Here is an overview of the routes to the XCAPI. Calls from the PSTN, the XCAPI and the PBX can access the XCAPI via prefix 93. [[Image:8-to-gw3-routes.PNG]]<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=17982 2010-06-28T13:11:54Z

<p>TE-SYSTEMS GmbH: /* Introduction */</p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.3.161) into an existing environment of<br /> current innovaphone gateways (Version 6 and following). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX/gateway. At this point, we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the XCAPI Homepage (http://www.te-systems.de/community/index.php?L=0).<br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH https://wiki.innovaphone.com/index.php?title=Howto:XCAPI&diff=17981 2010-06-28T13:09:10Z

<p>TE-SYSTEMS GmbH: </p> <hr /> <div>{{Template:3rd Party Input}}<br /> ==Applies To==<br /> This information applies to<br /> <br /> * IP302, IP305, IP400, IP800, IP3000, IP6000<br /> <br /> Configuring the XCAPI with the innovaphone Gateways<br /> <br /> == Introduction ==<br /> <br /> This document is intended to support you with the integration of the XCAPI (version 3.2.20) into an existing environment of<br /> the innovaphone IP3000 (Version 6). In the following sections we describe the essential steps of configuration to allow for optimal cooperation of both the XCAPI and the innovaphone PBX. At this point we suppose that the innovaphone PBX, the hardware the XCAPI is running on and both the XCAPI and your CAPI applications are already installed properly. For some extended information on installation procedures please refer to the respective manuals. A short installation manual for the XCAPI is available at the<br /> XCAPI Homepage.<br /> <br /> <br /> <br /> == H.323 ==<br /> === Configuring the innovaphone PBX ===<br /> In order to establish communications between the XCAPI and the innovaphone PBX using the H.323 protocol, you need to create a new controller inside the XCAPI and set up a connection to the XCAPI inside the innovaphone PBX. First, we start to configure the innovaphone PBX. Please open the web based innovaphone PBX configuration interface. The XCAPI can be configured as a PBX<br /> object for assigning single MSNs or it can be configured as an external gateway, allowing the mapping of a route pattern with multiple extensions. In most cases, the second method should be preferred.<br /> <br /> <br /> <br /> ==== Configuring a VoIP Gateway ====<br /> To add the XCAPI as a new gateway, you have to choose the Gateway dialog out of the Administration menu. If you haven’t logged in as administrator yet, you need to do now for accessing this configuration dialog. Now you can configure a new gateway in the VoIP<br /> dialog. Click on an arbitrary '''GW Interface''' entry that is not configured yet. If you haven’t configured any gateway, please use GW1. A new window will open where you can configure the gateway settings. TechNote In this example we configure the new gateway as<br /> described:<br /> <br /> * The Name field should be set to a meaningful name. Here we enter the name XCAPI Gateway.<br /> * Please make sure that the Disable option is not active.<br /> * In the Protocol field we select the value H.323 as protocol for the communication between the XCAPI and the innovaphone PBX.<br /> * The Gatekeeper Address (primary) field has to be filled with the IP address of the computer the XCAPI is running on.<br /> * We recommend selecting a codec like G.711 a-Law or G.711 μ-Law for the internal communication between the XCAPI and the innovaphone PBX. Set both the General Coder Preference and the Local Network Coder to the appropriate codec that fits your VoIP environment. Set the Framesize ms of both codecs to the value of 20 ms. This is the default value for the XCAPI.<br /> * Activate the Enable T.38 option for fax functionality.<br /> * For best results, we recommend to activate the No Faststart and No H.245 tunneling options.<br /> <br /> All other options that were not mentioned should be left by the default settings. Depending on your environment<br /> some further settings could be necessary. Please refer the innovaphone PBX manual for detailed descriptions.<br /> Finally, please click the '''APPLY''' button to add the new gateway to your innovaphone PBX configuration.<br /> The IP address will be automatically assigned to the new added XCAPI Gateway after configuring the XCAPI.<br /> <br /> <br /> <br /> ==== Route Patterns ====<br /> Please select the Routes dialog from the Administration - Gateway menu for configuring a route pattern. Here you<br /> have to create one route for each direction, from ISDN to VoIP and the other way round.<br /> We start with the route from the ISDN interface to the XCAPI. Please click the small icon with the arrow<br /> pointing to the right. A new dialog will appear where you can set the route pattern and its direction. In the<br /> Description field, you may enter a meaningful description for this route. In this example, we enter the value ISDN –&gt; XCAPI Gateway.<br /> From the list of checkboxes to the left, select the incoming interface, i.e. the interface from where the calls<br /> for this route originate. We use the first PRI interface for the ISDN connection, so please activate the option PRI1.<br /> The two text areas that are connected with an arrow are used for the route pattern. The left text area describes the incoming number, whereas the right text area describes the outgoing number that is delivered to the XCAPI. If, for example, the ISDN interface can be<br /> reached using the trunk number ''123'' and you want to configure a pattern of numbers beginning with ''123100''<br /> and ending with ''123199'', simply enter ''1231'' in both fields. If you would like to truncate the trunk number from<br /> the route pattern, enter ''1231'' in the left field and ''1'' in the right field. This means that the route pattern can<br /> be reached when dialling any number beginning with ''1231'', but only the part of the extension beginning with<br /> the second ''1'' will be delivered to the XCAPI. From the list to the right, please select the Gateway<br /> we have configured earlier (GW1 XCAPI Gateway).<br /> <br /> Finally, confirm the settings with the '''APPLY''' button and close the window.<br /> <br /> <br /> <br /> === XCAPI Configuration ===<br /> Please start up the XCAPI configuration to create a new controller assigned to the innovaphone PBX. If you’ve just installed the XCAPI and start the configuration tool for the first time, the XCAPI Controller Wizard will pop up automatically. This will also happen if there’s no controller configured at all. To start up the XCAPI Controller Wizard on your own, just click the link labeled '''&lt;u&gt;Click here to add a controller&lt;/u&gt;''' on the overview page of the XCAPI configuration tool. On the first page of the Controller Wizard please select the Add Voice-over-IP controller (VoIP) option and continue by clicking on the '''NEXT''' button.<br /> <br /> Hint: You can best use the ControllerWizard by making the necessary adjustments in<br /> the dialogs presented to you, using the '''NEXT''' and '''BACK''' buttons to navigate. When showing the relevant dialogs of the ControllerWizard<br /> we won’t mention clicking '''NEXT''' to advance every time. Just assume you have to click '''NEXT''' after completing a dialog.<br /> <br /> <br /> <br /> ==== Network Interface ====<br /> On this page of the XCAPI Controller Wizard you can select the network adapter you want to bind to the<br /> XCAPI controller. Should you have any doubts here, please refer to the XCAPI Quick Start Guide for further details.<br /> <br /> <br /> <br /> ==== Voice-over-IP Environment ====<br /> The next dialog of the configuration tool shows a list of some common Voice-over-IP environments. Selecting<br /> one of those will configure the XCAPI with a selection of near-optimal presets for the kind of environment you<br /> have, sparing you quite a lot of manual configuration. Please select the innovaphone option here.<br /> <br /> <br /> <br /> ==== IP address and gatekeeper ID ====<br /> In this dialog you can provide the address of your innovaphone Gateway and enter a gatekeeper ID. Although it is recommended to let the system discover the IP address of the innovaphone device automatically you can provide the IP address of the innovaphone device and disable the automatic recovery. The gatekeeper ID may be left blank if you have provided the IP address of the innovaphone device or it is the only PBX (gatekeeper) in the network. In this example we disable the automatic recovery and provide the IP address of our innovaphone PBX device with the value ''192.168.1.205''. The left the innovaphone gatekeeper ID blank, as we use only one PBX<br /> (Gatekeeper) in our environment.<br /> <br /> <br /> <br /> ==== Local telephone number and alias name ====<br /> In this dialog you have to provide the telephone numberand the alias name that are configured at the innovaphone gateway. If no alias name is configured this field may be left blank. If an alias name is configured at the innovaphone PBX the alias name is required. In<br /> this example we enter the value ''123'' in the Telephone number field that describes a six-digit long number so the XCAPI and the connected CAPI applications can be reached with the range of numbers between ''123000'' and ''123999''.<br /> <br /> <br /> <br /> ==== Description and Channels ====<br /> That’s about all information that has to be configured with the XCAPI. The next-to-final dialog of the ControllerWizard<br /> allows configuring a meaningful description for the controller you’re going to create. This isn’t really used anywhere, so you can enter a text of your choice here. This dialog, however, also allows configuring the<br /> number of channels that the new controller will be able to provide. Please enter how many simultaneous connections<br /> the XCAPI should handle when communicating with the PBX.<br /> <br /> <br /> <br /> ==== Confirmation ====<br /> The final dialog of the Controller Wizard performs some checks on the configuration parameters you’ve<br /> made. If any errors are detected here, you can go back to the respective dialogs and correct the necessary input.<br /> If everything is correct please use the '''FINISH''' button in order to finally create the new controller.<br /> The controller you’ve just created now will appear on the overview page of the XCAPI configuration tool.<br /> As we’re now finished with all XCAPI-related configuration tasks, please save the changes you’ve made<br /> and exit the configuration tool.<br /> <br /> == Known Problems ==<br /> <br /> SIP to H.323 interworking has turned out to be a problem. [[Image:Xcapi_sip.png|thumb]]<br /> XCAPI does neither support Faststart nor Extended Faststart (EFC). XCAPI only supports capability exchange through H.245 procudures.<br /> <br /> One trick to get this working is to configure the gateway interface to media-relay and exclusive coder (gateway interface talking to XCAPI).<br /> <br /> But the recommended strategy is to configure the XCAPI to use SIP signaling. This eliminates the whole interworking problem.<br /> <br /> == Related Articles ==<br /> <br /> &lt;!--*[[Main_Page|wiki-innovaphone]]--&gt;<br /> <br /> * http://www.xcapi.de<br /> * http://www.te-systems.de<br /> <br /> [[Category:Faq|{{PAGENAME}}]]<br /> [[Category:Howto|{{PAGENAME}}]]<br /> [[Category:Compat|{{PAGENAME}}]]</div>

TE-SYSTEMS GmbH