Technical Connection. Party A shall appoint certain special persons to promptly eliminate technical failure in case of any failure in the technical interface between both Parties. Party A shall expressly notify Party B of the proper access to transactions and countermeasures to accidents, as well as Party A's contact information etc.
Technical Connection. 2.1. The connection to the SDN is made via a link to the SDX or SDN-MPLS. On connection via SDN-MPLS, CPE equipment is set up to handle security rules.
2.2. At the connected party, the CPE equipment must be placed in such a way that is protected and covered by the connected party's own relevant IT security policies for e.g. operational security, network security and physical access control.
2.3. The connected party accepts that MedCom or the operation supplier can interrupt or restrict SDN traffic to and from the connected party without notice in the event that the connected party's link to the SDN is abused. MedCom or the operation supplier must immediately notify the connected party in writing of the interruption and state the reason. Abuse means attempts to gain unauthorised access to either equipment or data (hacking/cracking) or intentional network disruptions (Denial of Service). Reopening of the traffic must be made at the request of the connected party when the connected party has effectively rectified the cause of the interruption.
Technical Connection. To perform the VoIP Services, each Party must bear the costs related to investment, provisioning and maintenance of the connecting facility located within its network territory. • To perform the VoIP Services, each Party must bear the costs related to investment, provisioning and maintenance of third party Public Internet transport located outside its respective network territory. • The VoIP Services will be handed over to BICS with IP connectivity. Connections can be made over the Public Internet and the used IP addresses will allow being routed using Public Internet routing. • BICS determines in which manner directly or indirectly it routes the received VoIP traffic pursuant to the First Class VoIP or Business Class routing plan. BICS is not obliged to convey Call Line Identification (CLI). In case First Class VoIP routing is used by the Customer, BICS will execute in good faith and with its best endeavours the use of routes which are supporting the transmission of CLI, as mentioned below in the characteristics of this routing product. In no event will a Party provide the other with access to end-user’s management systems. • The number of simultaneously usable sessions supporting the VoIP traffic sent by the Customer to BICS will be fixed at 150 sessions. If the Customer exceeds this number of simultaneously usable sessions, the calls will be rejected. ■ FIRST CLASS VOIP ROUTING CHARACTERISTICS • First Class VoIP quality is a very high quality for International VoIP Outgoing Calls. The aim of this product is to enable traffic termination at retail quality. • The First Class VoIP routed calls shall be carried over the best available quality routes. Therefore BICS shall use its best efforts to route as such. • The First Class VoIP routed calls shall be preferentially routed on direct routes to the destination operators. A transcoding free direct VoIP route will have preference on a direct TDM route. • If BICS chooses to use a hub inside the First Class VoIP routing, only the best available alternative routes will be implemented. Such routes must provide a quality at least comparable to the direct route. • BICS is responsible for in-depth testing of each First Class VoIP route before implementation. • BICS shall on an on-going basis monitor the performance of the implemented First Class VoIP routes. • BICS guarantees to take immediate action when the quality of the First Class VoIP routes is insufficient. • BICS ensures 24/24 hours pro-active quality monito...
Technical Connection. 4.1 Connection to SDN is established by installing an SDN SD-WAN box(es) locally at the connected party's premises.
4.2 The connected party is responsible for configuring their own network to route traffic to SDN through the SDN SD-WAN box(es).
4.3 The SD-WAN box(es) must be placed at the connected party's premises in a manner that is protected and covered by the connected party's relevant technical and organisa- tional measures, including operational security, network security, physical security, and access control.
Technical Connection. 3.1 Party A provides technical documentations describing the methods and details of parameters to connect VTC Pay for Party B in order to support Party B to make surveys and modify systems to be able to offer Products and services and to match Party B’s connection standards.
3.2 Party B undertakes not to disclose, provide, or integrate specifications provided by Party A to any website other than Party B’s merchants’ online sales website without the prior written consent of Party A.
3.3 Party B will be responsible for investments in hardware, software, and communication lines to ensure continuous connectivity.
Technical Connection. The Participant/User shall be obliged to establish the technical connection to the Corporate Banking Portal only through the Corporate Banking Portal access channels (for example Internet address) notified to the Customer by the Bank. The Customer shall be responsible for maintaining appropriate data backup for his own systems and for taking sufficient precautions against viruses and other harmful programs (for example Trojans, worms, etc.) and keeping them constantly up to date. The Bank’s apps may be obtained only from app providers which the Bank has notified to the Customer. The Customer shall take responsibility for complying with the country-specific provisions for the use of the Internet.
