----

----

----

| 1.1 Overview |
|--------------|

| 1.2 Preamble and Effective Date |
|---------------------------------|

| 1.3 Scope of Agreement |
|------------------------|

| a. | This Agreement shall only apply to Amdocs’ resale to [**] of the Software and provision of Services described herein and in Appendix A for the Virtual Probe Solution (vprobe), subject to the terms and conditions of this Agreement and the EULA and pursuant to and in conformance with Statements Of Work (each an “Order”) submitted by Amdocs or its Affiliates.  The applicable fee for the Material and Services is specified in Appendix B.  Amdocs Affiliates may issue Orders under this Agreement.  Radcom shall not reject any Order for Material or Services described in Appendix A unless the Order includes: |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 1. | Delivery Dates to which Radcom has not agreed, prior to the placement of the Order, and which Radcom is unable to meet; or |
|--------|----|----------------------------------------------------------------------------------------------------------------------------|

|   | 2. | Terms and conditions to which Radcom has not agreed, prior to placement of the Order, and which are objectionable to Radcom; or |
|--------|----|---------------------------------------------------------------------------------------------------------------------------------|

|   | 3. | Prices contrary to those established under this Agreement. |
|--------|----|------------------------------------------------------------|

| b. | If Radcom rejects an Order, Radcom, shall give Amdocs written notice stating Radcom’s reasons for rejecting the Order and the modifications, if any, that would make the Order acceptable to Radcom. Radcom shall furnish Materials that materially conform to the Specifications established under this Agreement or as otherwise set forth in an Order.  If Radcom is unable to tender conforming Material, Radcom shall not tender non-conforming Material; the Parties agree non-conforming tenders are not an accommodation to Amdocs.  All Delivery Dates are firm, and time is of the essence. |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

----

----

----

| a. | requires as a condition of use, that such Viral Open Source Software or other software combined with such Viral Open Source Software be: |
|----|------------------------------------------------------------------------------------------------------------------------------------------|

| b. | as a condition of use by [**], affect or purport to affect any [**] intellectual property right not originating exclusively in such Viral Open Source Software; or |
|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| c. | impede or restrict [**]’s ability to use the corresponding Materials as contemplated in the Specifications and Documentation. |
|----|-------------------------------------------------------------------------------------------------------------------------------------|

----

| 3.2 Notices |
|-------------|

| a. | Each Party giving or making any notice, consent, request, demand, or other communication (each, a “Notice”) pursuant to this Agreement must give the Notice in writing and use one of the following methods, each of which for purposes of this Agreement is a writing: in person; first class mail with postage prepaid; Express Mail, Registered Mail, or Certified Mail (in each case, return receipt requested and postage prepaid); internationally recognized overnight courier (with all fees prepaid); facsimile transmission; or email.  If Notice is given by facsimile transmission or e-mail, it must be confirmed by a copy sent by any one of the other methods.  Each Party giving Notice shall address the Notice to the appropriate person (the “Addressee”) at the receiving Party at the address listed below: |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| b. | A Notice is effective only if the Party giving notice has complied with the foregoing requirements of this Section and the Addressee has received the Notice.  A Notice is deemed to have been received as follows: |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 1. | If a Notice is delivered by first class mail, five (5) days after deposit in the mail; |
|--------|----|----------------------------------------------------------------------------------------|

|   | 2. | If a Notice is furnished in person, or sent by Express Mail, Registered Mail, or Certified Mail, or internationally recognized overnight courier, upon receipt as indicated by the date on the signed receipt; |
|--------|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 3. | If a Notice is sent by e-mail or facsimile transmission, upon successful transmission to the receiving machine, if such Notice is sent in time to allow it to be accessible by the Addressee before the time allowed for giving such notice expires, and a confirmation copy is sent by one of the other methods. |
|--------|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| c. | The addresses and telephone numbers to which notices or communications may be given to the Addressees of either Party may be changed by written notice given by such Party to the other pursuant to this Section. |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| 3.3 Term of Agreement |
|-----------------------|

| a. | This Agreement is effective on upon final signature (the “Effective Date”) and, unless terminated as provided in this Agreement, shall remain in effect for a term ending [**] years from the Effective Date  (the “Initial Term”). |
|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| b. | After the Initial Term, Amdocs shall have the option to extend the term for an additional period of [**] months by giving Radcom written notice at least [**] days prior to the expiration of the Initial Term.  The termination or expiration of this Agreement shall not affect the obligations of either Party to the other Party pursuant to any Order previously executed hereunder, and the terms and conditions of this Agreement shall continue to apply to such Order as if this Agreement were still in effect.  Likewise, termination, or expiration of the General Agreements shall not affect the obligations of either Party to the other Party pursuant to this Agreement, and the terms and conditions of the General Agreements shall continue to apply to this Agreement as if the General Agreements were still in effect. |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| a. | Radcom has tested and certified to Amdocs that Radcom has identified no Critical faults. |
|----|------------------------------------------------------------------------------------------|

| b. | [**] has received from Amdocs of all software, complete media, and documentation from Radcom. |
|----|-----------------------------------------------------------------------------------------------|

| c. | All emergency patches must be officially released by Radcom.  |
|----|--------------------------------------------------------------------|

| d. | The content of delivered software must be compatible with previous releases and remain consistent through the life of the core software. |
|----|------------------------------------------------------------------------------------------------------------------------------------------|

| e. | Radcom shall comply with the following policy regarding OS patch testing related to ongoing releases: Radcom will notify Amdocs of the patch releases Radcom plans to test prior to test execution. Amdocs will confirm within [**] working days whether releases have been accepted by [**] (ITO/CSO). If [**] have rejected a patch release, Amdocs will advise and Radcom will verify against the previous accepted version. Radcom will test one OS and one database patch version for each release. |
|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| f. | Included in the GA release is the associated final Documentation associated with each of the applicable target released components planned for deployment, provided that further updates to the Documentation may be made and provided to [**] later on. |
|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| g. | Release notes have been provided by Radcom to Amdocs identifying major features expected in the release and any known issues (minor faults) that may be encountered during testing. |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| h. | Associated training materials compiled by Radcom technical subject matter experts are complete and available for use by [**].  [**] pre-requisites are identified, documented, and met. This includes any additional software that must be obtained to satisfy requirements for the target release by Radcom. |
|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| i. | Any GA requirement may be waived (in writing in [**] sole discretion) if there is a specific documented requirement for a non-GA release by [**]. |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------|

----

| a. | If installation services are provided for the Software for or during the FFA, it shall be considered complete and ready for [**]’s consideration only after testing by Radcom in material compliance with both [**] and Radcom installation Specifications and procedures.  Upon completion of the initial Installation, Radcom will submit to Amdocs (who shall then submit promptly to [**]) a “Notice of Completion”. If found by [**] to be materially in compliance with such installation Specifications and procedures, upon notice by [**], Amdocs will advise Radcom and the Software will be granted General Acceptance by Amdocs and, if not in compliance, then additional rounds of tests will be conducted until compliance is achieved. The Software shall be deemed Accepted upon the earliest occurrence of the following events: (i) a “Notice of Completion” was issued by Radcom, and Amdocs did not raise any material deviations from the installation Specifications and procedures, by the lapse of the period set for said tests as agreed by the Parties as part of the Project Plan; and/or (ii) if completion of Installation is delayed for an extended period of time due to an act and/or omission of [**], Amdocs and Radcom agree to achieve a mutually agreed resolution; and/or (iii) the Radcom Software is no longer deployed in a limited capacity; and/or (iv) there are no Critical and no more than [**] Major Errors. There will be an Evaluation Period after First Field Application to evaluate performance of the Software. |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| b. | If the Software meets the requirements as set forth in Appendix A for General Acceptance, Amdocs shall be deemed as Accepting the relevant Software component. |
|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------|

| c. | Radcom, at its expense, shall correct defects or other issues impeding such General Acceptance within [**] working days, or as may be otherwise agreed to by the Parties, from receipt of Amdocs’ receipt of [**]’s notification and shall notify Amdocs that such corrections have been made. Amdocs shall require that [**] repeat the appropriate acceptance tests, and the above procedure shall continue until General Acceptance is achieved. General Acceptance shall be deemed to occur upon the earlier occurrence of the following events: (i) there are no Critical Errors and no more than [**] Major Errors; and/or (ii) Amdocs was notified on the remedy of the corrections, and failed to raise any feedback within [**] working days of said notification. |
|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| 4.3.1 | Lab and FFA Process |
|-------|---------------------|

----

|   | (a) | FFA Project Plan with relevant milestones and resource allocation. |
|--------|-----|--------------------------------------------------------------------|

|   | (b) | An Acceptance Test Plan (ATP), which highlights the relevant Test Objects to be validated. These Test Objects will cover the various functionalities of the Supplier solutions. |
|--------|-----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | (c) | The lab test environment to be set up for the validation. |
|--------|-----|-----------------------------------------------------------|

|   | (d) | Establish a regular lab meeting schedule and method of documenting validation status and progress. |
|--------|-----|----------------------------------------------------------------------------------------------------|

|   | (e) | The scope of testing may include but is not limited to feature/functionality verification, negative tests, monitoring of other network elements, load/capacity tests, interoperability/interworking tests for D1 and other platforms, end-to-end performance evaluation, application tests, and user interface testing. |
|--------|-----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | (f) | If so requested by [**] from Amdocs, Amdocs may mandate that a release be tested on an entire market/region before GA can be granted, and the Parties will agree as part of the FFA project plan on a per release basis. |
|--------|-----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| 4.3.2 | [**] Product Acceptance Milestones |
|-------|------------------------------------|

| 4.3.3 | Ready for Acceptance (RFA) Milestone |
|-------|--------------------------------------|

|   | · | Amdocs and Radcom have agreed to jointly-developed Acceptance Test Plans (ATPs) with [**] input accepted. |
|--------|--------|-----------------------------------------------------------------------------------------------------------|

|   | · | All known “Critical” issues (found during Radcom testing period) have been resolved or have an agreed upon resolution plan. |
|--------|--------|-----------------------------------------------------------------------------------------------------------------------------------------|

----

|   | · | Amdocs and Radcom have had an Entry RFA meeting and, upon [**]’s agreement, agree to proceed to RFA. |
|--------|--------|------------------------------------------------------------------------------------------------------------|

|   | · | Radcom has provided all required product documentation, including but not limited to |
|--------|--------|--------------------------------------------------------------------------------------|

|   | o | System load and product verification test plans and results, as needed to determine that RFA entry criteria are met. |
|--------|---|----------------------------------------------------------------------------------------------------------------------|

|   | o | Release notes and system impact document where all impacts and changes to Software, backend, and interfaces are identified. |
|--------|---|-----------------------------------------------------------------------------------------------------------------------------|

|   | o | Key documents where changes with impacts to [**] 3rd party applications (ex. IT systems) and D1 Interworking (other suppliers’ nodes and systems) are identified. |
|--------|---|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | o | Response to Amdocs, with respect to [**] security checklist and [**] approval/acceptance |
|--------|---|------------------------------------------------------------------------------------------|

|   | · | Radcom will hold a knowledge transfer workshop that will provide [**] lab personnel with sufficient details regarding product architecture, operation, and implementation. Where possible, the information should include simulation results or knowledge gained from testing in Radcom’s lab. Knowledge transfers sessions’ topics shall include, but are not limited to, feature implementation, feature testing/simulation, delta training, etc. This may be in a customized format specifically addressing the current project, or Radcom may make use of existing training courses, so long as project timeline constraints are met, at no cost and with no minimum attendance requirements. Workshops will be scheduled for a mutually agreed timeframe to the [**] lab and Radcom as lab entry criteria, and to provide knowledge transfer to meet project requirements.  Every effort will be made to schedule workshops on-site while appropriate Radcom personnel are present. |
|--------|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | · | All tests specified in the ATPs have been completed, with any exceptions noted. |
|--------|--------|---------------------------------------------------------------------------------|

|   | · | All known priority “Critical” issues remaining after the RFA phase have been resolved and all priority “Major” issues have an agreed upon resolution plan. Priority “Critical” issues have an acceptable and approved work around. |
|--------|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | · | Amdocs, [**] and Radcom have had an Exit RFA meeting and agreed to proceed on to the RFS stage. |
|--------|--------|-------------------------------------------------------------------------------------------------|

| 4.3.4  | Ready for Service (RFS) Milestone |
|-------------|-----------------------------------|

|   | · | All tests specified in the ATPs have been completed, with any exceptions noted. |
|--------|--------|---------------------------------------------------------------------------------|

|   | · | All known “Critical” issues remaining after the RFA phase have been resolved and all “Major” priority issues have an agreed upon resolution plan. |
|--------|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | · | [**], Amdocs and Radcom have had an Entry RFS meeting and agree to proceed. |
|--------|--------|-----------------------------------------------------------------------------|

|   | · | Engineering support from [**], Amdocs or Radcom are available to monitor performance and issues related to the overall solution to be tested. |
|--------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------|

----

|   | · | [**], Amdocs and Radcom have had a kick off meeting with [**] Operations, ATS and other relevant teams. |
|--------|--------|---------------------------------------------------------------------------------------------------------|

|   | · | Required Operational Training for the FFA has been held prior to proceeding to the field. Content of the training shall be agreed between Amdocs and Radcom. |
|--------|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | · | The exit criteria to be met for RFS are: |
|--------|--------|------------------------------------------|

|   | o | All tests specified in the ATPs have been completed, with any exceptions noted. |
|--------|---|---------------------------------------------------------------------------------|

|   | o | All new “Critical” priority issues found during the RFS phase have been resolved. All “Major” issues have a resolution plan acceptable to Amdocs. |
|--------|---|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | o | All major feature functionality has been proven to work satisfactorily |
|--------|---|------------------------------------------------------------------------|

|   | o | Software is benchmarked and the result is compared to performance with the prior software version and there is no degradation in features, functionality or capacity, unless any such degradation is agreed with Amdocs prior to FFA and is noted in Radcom’s documentation. |
|--------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | o | System is declared stable for a mutually agreed soak period and with normal usage.  The soak period starts after the last changes are implemented and lasts for a minimum of [**] weeks. All FFA documentation is completed and released, including FFA result document. |
|--------|---|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | o | Updated MOP, Test Plans, and other FFA related documents that have been updated during the FFA should be provided to Amdocs. |
|--------|---|------------------------------------------------------------------------------------------------------------------------------|

|   | o | A complete list of all cases failed during the FFA periods has been provided to Amdocs. This should be a detailed list which explains the nature of the problem for which the case was failed, and the nature of the fix. |
|--------|---|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | o | A complete list of all patches applied during the FFA, and which cases those fixed, if applicable.  |
|--------|---|----------------------------------------------------------------------------------------------------------|

| 4.3.5 | FFA Support |
|-------|-------------|

| 4.3.6 | Software Efficiency and Capacity Requirements |
|-------|-----------------------------------------------|

----

| 1. | Critical:  Critical system functionality is not operational or not capable of producing critical deliverables (which have been pre-defined in Appendix A as critical) and there are no workarounds available.  The problem/defect has one or more of the following characteristics: |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | a. | Data corruption such that physical or logical data is unavailable or incorrect. |
|--------|----|---------------------------------------------------------------------------------|

|   | b. | System hangs.  The system becomes non responsive indefinitely or there is severe performance degradation, causing unreasonable wait time for resources or response, as if the system is hanging. |
|--------|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | c. | System crashes repeatedly. Database process or background processes fail and continue to fail after restart attempts. |
|--------|----|-----------------------------------------------------------------------------------------------------------------------|

|   | d. | Critical functionality (which has been pre-defined in Appendix A or otherwise by the Parties in writing as critical) is not available.  The application cannot continue because a vital feature is inoperable. |
|--------|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | e. | Resource limitation (e.g., disk space) prevents a user from doing work without an agreed-upon workaround. |
|--------|----|-----------------------------------------------------------------------------------------------------------|

|   | f. | Security vulnerability beyond [**] control that results in unauthorized access to systems, crashing of systems or data corruption, and which cannot be avoided by [**]. |
|--------|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| 2. | Major:  Major system functions are unavailable or unusable.  An agreed-upon workaround is available, and operations can continue in a restricted fashion.  The problem/defect has one or more of the following characteristics: |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | a. | Reoccurring Errors causing the system to fail, but restart or recovery is possible. |
|--------|----|-------------------------------------------------------------------------------------|

|   | b. | Severely degraded performance. |
|--------|----|--------------------------------|

|   | c. | Limited access to data to perform the job. |
|--------|----|--------------------------------------------|

|   | d. | Missing a message capture per requirements (no error message at all) when a major error occurs. |
|--------|----|-------------------------------------------------------------------------------------------------|

|   | e. | Incorrect response to a command for a major system function. |
|--------|----|--------------------------------------------------------------|

|   | f. | Security vulnerability with a workaround that mitigates such vulnerability. |
|--------|----|-----------------------------------------------------------------------------|

|   | g. | Some important functionality is unavailable, yet the system can continue to operate in a restricted fashion. |
|--------|----|--------------------------------------------------------------------------------------------------------------|

| 3. | Minor:  A defect/problem that does not rise to the level of either Critical or Major. |
|----|-------------------------------------------------------------------------------------------------|

|   | a. | Radcom shall furnish, [**], Documentation for the Software and other Material delivered hereunder, including any and all succeeding changes, updates and upgrades. |
|--------|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | b. | Documentation shall include user instructions, engineering guidelines, installation information, system manuals and training material in electronic form, Radcom’s customer facing written specifications, all written material defined in the table below associated with Software and other information that is normally delivered by Radcom regarding the Software and/or Material.  Engineering/capacity management guidelines shall include sufficient information and insight from Radcom to enable Amdocs to assist [**] in capacity management of the Software under this Agreement.  Capacity management guidelines shall enable [**] to determine the engineered capacity for the system and identify the key capacity indicators that should be monitored and trended to recognize when the system resources are nearing exhaust. Radcom will provide the following to Amdocs, in order to enable [**] to capacity manage the monitoring system: |
|--------|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | · | Capacity limits of the v-probe solution |
|--------|--------|-----------------------------------------|

----

|   | · | Call model factors that were used to produce the stated capacity |
|--------|--------|------------------------------------------------------------------|

|   | · | A list of KCIs that should be used to monitor the stated capacity triggers |
|--------|--------|----------------------------------------------------------------------------|

|   | · | A mechanism to obtain the KCI data |
|--------|--------|------------------------------------|

|   | · | MOP for installation and any making any changes to the Software. This MOP shall provide guidelines to install Software, Upgrades and Updates. |
|--------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------|

|   | a. | Ownership and Use of Rights and Items. |
|--------|----|----------------------------------------|

----

|   | b. | License Grant to Excluded Materials. |
|--------|----|--------------------------------------|

----

|   | c. | Further Acts and Obligations. |
|--------|----|-------------------------------|

|   | d. | Reservation of Rights and Limited License. |
|--------|----|--------------------------------------------|

|   | e. | Notwithstanding anything in the General Agreement to the contrary, the Section of the General Agreement entitled “Title to Work” shall not apply to this Agreement. |
|--------|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | a. | Radcom and Amdocs shall make available a minimum [**] user training sessions, and [**] admin training sessions, in multi-person classes, up to [**] each, at an [**]-designated site, at a date, time and location to be proposed by Amdocs and [**] and reasonably agreed to by Radcom and Amdocs.  This will be provided at no cost. |
|--------|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

|   | b. | User training materials and admin training materials will be reasonably agreed upon by the Parties and be provided to the identified participants at least [**] week prior to the scheduled training, at no additional cost. |
|--------|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | c. | Radcom will make available to [**], at the detailed below published Radcom rates (less any applicable discount to which [**] is entitled), additional training material and courses to include instruction on functions, features and usability tailored to the specific group receiving the training. Radcom has a professionally-developed in house training curriculum for Radcom products that offer student guides that are designed to work in conjunction with the instructor’s presentation.  Each student enrolled in the class will receive a current copy of the student guide. |
|--------|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| Training Course                   | Cost                 | Description                                                            |
|-----------------------------------|----------------------|------------------------------------------------------------------------|
| Training-Basic                    |  US$ [**]  | [**]                                                                   |
| [**]                              |
| Training-Adv                      | US$ [**]             | [**]                                                                   |
| [**]                              |
| Administrator/Operations Training | US$ [**]             | [**] ·         [**]. |

----

----

| a. | Upon discovery of anything indicating a reasonable certainty that Software and/or Services will not be Delivered by the scheduled Delivery Date, Radcom shall notify Amdocs and provide the estimated length of delay. The Parties shall work jointly toward resolving the delayed Delivery and to agree on a revised Delivery Date.  Amdocs will use reasonable efforts to obtain agreement from [**] on an extended Delivery Date and if such an extended date is agreed, will align the Radcom Delivery Date to the date agreed with [**].  If the Parties reach agreement on an extended Delivery Date  and Radcom fails to meet the extended Delivery Date, then Amdocs may (i) exercise its right to recover Liquidated Damages specified hereunder, to the extent [**] has exercised its right to recover Liquidated Damages from Amdocs (ii) further extend the Delivery Date, and/or (iii) if such delay amounts to a material breach, terminate the applicable Order, but only after the cap of the Liquidated Damages mentioned below has been reached and only in the event [**] has terminated the Applicable order with Amdocs, under this section. Notwithstanding any terms to the contrary in this Agreement or the General Agreements, the effective date of termination of the Amdocs Order with Radcom shall be the same as the effective date of termination of the corresponding scope of the [**] order with Amdocs. No payments, progress or otherwise, made by Amdocs to Radcom after any scheduled Delivery Date shall constitute a waiver of Liquidated Damages. Delivery Dates shall be extended as and to the extent Radcom is unable to meet the original Delivery Date due to causes outside of Radcom’s control.  Such extension shall be proportionate to the delay caused by factors outside Radcom’s and/or Amdocs’ control, and in such events, the Liquidated Damages shall not apply.  |
|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| b. | Notwithstanding the above paragraph, in the event of Radcom’s failure to meet a Delivery Date, Amdocs shall be entitled to recover amounts as liquidated damages, and not as a penalty. For the first [**] days of delay, no liquidated damages will apply. Thereafter, liquidated damages of [**] % percent of the price of delayed Software and/or Services shall apply for each week up to [**] % of the delayed Software or Services price. |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| a. | Amdocs shall require in its agreement with [**] that [**] shall not provide or otherwise make available the Software in any form to any unaffiliated third party, except as provided in this Agreement, ,, the EULA or in an Order accepted by Radcom. |
|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| b. | Amdocs shall require in its agreement with [**] that [**] shall take appropriate action, by instruction, agreement or otherwise with the persons permitted access to the Software and Documentation, to satisfy the obligations pursuant to its agreement with Amdocs with respect to use, protection and security of the Software and Documentation. |
|----|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| c. | Amdocs shall provide in its agreement with [**] that  [**]’s  rights of disclosure under its agreement with Amdocs shall include the right to provide the Software and related Documentation to [**]’s agents and contractors anywhere in the world who have a reasonable need for it in connection with for the performance of services for [**]  under its agreement with Amdocs , provided that the Software and related Documentation may not be provided to a third party for the purpose of allowing that third party to develop or participate in the development of a product or service that competes with Radcom’s products. |
|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| a. | Radcom will use commercially reasonable efforts to notify Amdocs and [**] in writing (which may be via email) of all Updates for Software licensed hereunder to which Amdocs will be entitled for the purpose of providing them to [**], at least [**] prior to the availability of that Update. |
|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| b. | each new Update of Software (provided under a Support and Maintenance agreement) will be subject to [**] policies but for that particular Update only. |
|----|--------------------------------------------------------------------------------------------------------------------------------------------------------|

| c. | The Parties will seek to identify future Software Updates through the Radcom/Amdocs/[**] roadmap planning sessions and/or on-going communication exchanges.  The Parties will seek to jointly identify and document an annual (calendar year) inventory of future Software Updates to be included as part of that year’s Software releases to be made available as part of Support and Maintenance (the “Annual Software Feature List”). |
|----|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| a. | With respect to any Updates provided to Amdocs for [**] hereunder, RADCOM acknowledges and agrees that as per Amdocs agreement with [**], [**] will have the right to remove same and replace it with the previous version if such new version will degrade or impair [**]’s network.  If Amdocs wishes to resell licenses for any new features or functionality of Software that are not licensed to [**] as part of an Update and are licensed separately, then Amdocs and Supplier will negotiate in good faith on a license fee or payment for such feature or functionality. |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| 6.0 | Warranties, Indemnities and Liabilities for Software Licenses, Services and related Maintenance |
|-----|-------------------------------------------------------------------------------------------------|

| 7.0 | Escrow/Source Code |
|-----|--------------------|

| 8.0 | General Provisions |
|-----|--------------------|

| 9.0 | Additional Appendices |
|-----|-----------------------|

----

| 10.0 | Execution of Agreement |
|------|------------------------|

| IN WITNESS WHEREOF, the Parties have caused this Agreement to be executed as of the date thelast Party signs. |
|---------------------------------------------------------------------------------------------------------------|
| Amdocs Software Systems Limited.         |              | Radcom Ltd.                        |   |
|-----------------------------------------------|-------------------|------------------------------------|--------|
| By:                                           | /s/ Philip Butler |                               | By:    | /s/ David Ripstein |   |
|  Printed Name: Philip Butler        |              |  Printed Name: David Ripstein |   |
| Title: Director and Assistant Secretary  |              | Title: President & CEO         |   |
| Date: December 30, 2015                       |              | Date: December 30, 2015            |   |

----

| Document Version | Scope Items |
|------------------|-------------|
| V4               | [**]        |

----

| Appendix B: Fees |
|------------------|

| 1.     License |
|------------------------------------|

|  2.     In the event that based on a material breach by RADCOM of this Supplement Agreement or the General Agreements, which was not cured by RADCOM within [**] days of receipt of notice from Amdocs, Amdocs is in a material breach of its applicable agreement with [**] and as a result, Amdocs is contractually obligated to pay [**] any amounts attributable to licenses, Radcom will promptly indemnify Amdocs up to [**] for any amounts paid to [**].  |
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 3.     Additional Features                                                                                                                                                                                                                                                                                                                                                                                                                                                  |

|  An additional license payment for Additional Features (as outlined in Appendix D) is not due until the requested Features are delivered and [**]. RADCOM may invoice the corresponding amount listed in Appendix D1 for each additional feature delivered upon [**] of that additional feature. For clarity the amount for all Additional Features as outlined in Appendix D shall not exceed [**].  |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|         4.     Paid-For Development and Upgrades                                                                                                                                                                                                                                                                                                    |

|        Any feature functionality that constitutes Paid-For Development shall be subject to the terms of Section 4.6 of the Agreement.  |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| · | Provide a timely response to open issues and action items as raised by Radcom |
|--------|-------------------------------------------------------------------------------|

| · | Provide physical access into [**] premises to Radcom employees, including outside of standard business hours. |
|--------|---------------------------------------------------------------------------------------------------------------|

| · | Provide physical office environment for Radcom engineers on site (Desk, chairs, power, internet connection) |
|--------|-------------------------------------------------------------------------------------------------------------|

| · | 24x7 Remote access to all servers and clients running Radcom Software (Windows applications as well as command line interfaces). At least 15 concurrent remote connections. Open the Remote access to multiple TCP/UDP ports (list of ports will be provided by Amdocs) |
|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Ensure that Software will receive required traffic 24x7 from [**], including simulated and live traffic |
|--------|---------------------------------------------------------------------------------------------------------|

| · | Responsible to provide the required hardware |
|--------|----------------------------------------------|

| · | Provide full description of network elements |
|--------|----------------------------------------------|

| · | Provide full description of traffic (shape, type, protocols, scenarios, correlation etc.) |
|--------|-------------------------------------------------------------------------------------------|

| · | Provide full details of network sizing and expected growth |
|--------|------------------------------------------------------------|

| · | Provide Network Time Protocol (NTP) servers |
|--------|---------------------------------------------|

| · | Provide access to DNS servers |
|--------|-------------------------------|

| · | Provide access to DHCP servers |
|--------|--------------------------------|

| · | Provide access to SMTP servers |
|--------|--------------------------------|

| · | Provide SNMP access |
|--------|---------------------|

| · | Provide network inventory Enrichment data – IP addresses, types and names for all network elements,  sites, markets, sub-markets, APNs, Charging codes, Realms, MCC/MNC codes, Cell Global Identifier (CGI) values and names, Type Approval Code (TAC) – UE manufacturer / Model mapping. |
|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Assign the required HW resources to the virtual machines (compute, network, storage) according to Supplier's sizing |
|--------|---------------------------------------------------------------------------------------------------------------------|

| · | Assign the require HW performance according to product requirements provided by Supplier |
|--------|------------------------------------------------------------------------------------------|

| · | Assign IP addresses to the virtual machines. |
|--------|----------------------------------------------|

| · | Provide IP/VLAN connectivity between all Software components, within sites and between sites as well as between Software and test PCs as well as [**] client PCs. |
|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Open all ports between Software components in Firewall |
|--------|--------------------------------------------------------|

| · | Allocate qualified personnel who shall work with Supplier |
|--------|-----------------------------------------------------------|

| · | Provide technical focal point from [**] for support. |
|--------|-----------------------------------------------------------|

| · | Provide at least three (3) Windows client PCs/VMs per site for running MaveriQ OAM applications, with internet access |
|--------|-----------------------------------------------------------------------------------------------------------------------|

| · | Provide at least three (3) User Equipment units for testing purposes, with the ability to perform test calls for scenarios required in the project scope, including phones, SIM cards, etc |
|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Provide detailed documentation, KPI samples, XDR samples, XML samples for [**] and on-going updates in advance of any changes in the interface of the production environment. |
|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| · | Provide detailed documentation, samples, application access and testing environment to APIs for [**] data and on-going updates in advance of any changes in the interface of the production environment |
|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Provide detailed documentation, KPI samples, XDR samples, XML samples for [**] and on-going updates in advance of any changes in the interface of the production environment |
|--------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Provide detailed documentation samples, application access and testing environment to APIs for [**] and on-going updates in advance of any changes in the interface of the production environment |
|--------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Provide detailed documentation, samples, application access and testing environment for [**] APIs that Supplier is required to integrate with (e.g. [**]’s User Authentication platform) and on-going updates in advance of any changes in the interface of the production environment |
|--------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Provide detailed definitions and calculation methodology descriptions for new KPIs required by [**] |
|--------|-----------------------------------------------------------------------------------------------------|

| · | Provide test plan & test case documents for required testing procedures, at least 4 weeks before the start date of the test session |
|--------|-----------------------------------------------------------------------------------------------------------------------------------------|

| · | Provide sample pcap trace files and key files from [**] network for protocols and interfaces required in the project, for testing & validation, including on-going updates in advance of any changes in the interfaces/protocols in the production environment |
|--------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| · | Provide timely information & answers to Supplier, including Supplier’s technical questions with regards to [**] network, network elements, interfaces, protocols, call flows, platforms and 3rd party solutions that interact with Supplier’s solution. |
|--------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

| Appendix D - Additional Features [**] |
|---------------------------------------|

----

| Appendix D-1 Additional Features Pricing [ |
|--------------------------------------------|

----

| Appendix K Offshore Locations |
|-------------------------------|

| Country(ies) where services are authorized by [**] to be performed (physical location address is also required if the Services involve Information Technology-related work or if a “virtual” or “work-from-home” address is authorized) | City(ies) where services will be performed for [**]                           | Services to be performed at approved Physical Location | Name of Supplier / Supplier Affiliate, and/or Subcontractor performing the services |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------|-------------------------------------------------------------|-------------------------------------------------------------------------------------|
| Israel                                                                                                                                                                                                                                                          | 24 Raoul Wallenberg Street,Tel-Aviv 69719                                     | Tel Aviv                                                    | Research & Development (R&D), PS, M&S                                   | Radcom |
| Brazil                                                                                                                                                                                                                                                          | Al. Mamoré, 503 – 13o andar salaAlphaville – Barueri/SP | Alphaville                                                  | PS, M&S                                                                         | Radcom |
| India                                                                                                                                                                                                                                                           | Level 4, Rectangle 1,Commercial Complex D-4,Saket, New Delhi - 110017         | New Delhi                                                   | PS, M&S                                                                         | Radcom |

----

| Appendix M - Change Control Process and Forms |
|-----------------------------------------------|

| A. | If Amdocs is the Party submitting the request, Amdocs shall complete Form A and describe in reasonable detail the change it is proposing, and any effects on other Specifications or on the delivery schedule of which it is aware.  Radcom shall strive to respond to such request as soon as reasonably practical, but no later than ten (10) working days.  Radcom’s response shall be using Form B.  Subsequent communication shall use Form A and Form B, respectively, until the Parties either agree upon the terms pursuant to which the proposed change will be made, or agree that the proposed change will not be made and agree to close the proposed Change Order.  An agreement to proceed with the proposed change must be documented by using Form E. |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| B. | If Radcom is the Party submitting the request, Radcom shall complete Form C and describe in reasonable detail the change it is proposing, and the effects, if any, on other Specifications, schedule, and cost.  [**] shall strive to respond to such request as soon as reasonably practical, but no later than ten (10) working days.  [**]’s response shall be using Form D.  Subsequent communication shall use Form C and Form D, respectively, until the Parties either agree upon the terms pursuant to which the proposed change will be made, or agree that the proposed change will not be made and agree to close the proposed Change Order.  An agreement to proceed with the proposed change must be documented by using Form E. |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| C. | The rights and obligations of both Parties in connection with this Agreement, including any Order, shall not be changed, until a proposed Change Order is agreed to by executing Form E.  Until both Parties have executed Form E, each Party shall continue to perform its obligations in accordance with the Agreement and the Order(s) placed under the Agreement. |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

| D. | In the event Form E contains terms that are different than those set forth in the Agreement or the Order(s), the terms contained in Form E shall apply. |
|----|---------------------------------------------------------------------------------------------------------------------------------------------------------|

| E. | The Change Control Log, included as Form F, shall be used by the Parties to track and monitor all proposed changes. |
|----|---------------------------------------------------------------------------------------------------------------------|

| F. |   The standard [**] feature request form will be used to initiate a request for new features. |
|----|---------------------------------------------------------------------------------------------------------|

----

|   | 1. | Proposed Specification Changes - [Identify the Specification(s), including where the Specification(s) is described in the Order, and summarize in reasonable detail the proposed changes to such Specification(s).] |
|--------|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 2.  | Effective Date For Proposed Change: |
|--------|----------|-------------------------------------|

|   | 3. | Summarize Expected Or Possible Impact On Other Specifications Or Schedule |
|--------|----|---------------------------------------------------------------------------|

|   | 4. | Specify Any Key Assumptions, Additional Terms, Or Other Important Information |
|--------|----|-------------------------------------------------------------------------------|

----

----

|   | 1. | Proposed Specification Changes [Reiterate and summarize Supplier’s understanding of the proposed changes to the Specification(s)] |
|--------|----|-----------------------------------------------------------------------------------------------------------------------------------------|

|   | 2. | Effective Date For Proposed Change [Indicate the date the change can be implemented.] |
|--------|----|--------------------------------------------------------------------------------------------|

|   | 3. | Summarize Expected Or Possible Impact On Other Specifications Or Schedule  [Indicate the impact on other Specifications, schedule of delivery, and cost/budget, if any.] |
|--------|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 4. | Specify Any Key Assumptions, Additional Terms, Or Other Important Information |
|--------|----|-------------------------------------------------------------------------------|

----

----

|   | 1. | Proposed Specification Changes - [Identify the proposed Specification(s) and describe in reasonable detail the proposed changes.] |
|--------|----|-----------------------------------------------------------------------------------------------------------------------------------|

|   | 2. | Effective Date For Proposed Change: |
|--------|----|-------------------------------------|

|   | 3. | Summarize Expected Or Possible Impact On Other Specifications Or Schedule  [Indicate the impact on other Specifications, schedule of delivery, and cost/budget, if any.] |
|--------|----|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 4. | Specify Any Key Assumptions, Additional Terms, Or Other Important Information |
|--------|----|-------------------------------------------------------------------------------|

----

----

|   | 1. | Proposed Specification Changes [Reiterate and summarize Amdocs’ understanding of the proposed changes to the Specification(s)] |
|--------|----|--------------------------------------------------------------------------------------------------------------------------------------|

|   | 2. | Effective Date For Proposed Change [Indicate the proposed effective date of the change.] |
|--------|----|-----------------------------------------------------------------------------------------------|

|   | 3. | Summarize Expected Or Possible Impact On Other Specifications Or Schedule  [Indicate the impact on other Specifications, schedule of delivery, and cost/budget, if any Amdocs expects may occur as a result of Radcom’s proposed change.] |
|--------|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 4. | Specify Any Key Assumptions, Additional Terms, Or Other Important Information  [Indicate on what basis Amdocs would be willing to agree to Radcom’s proposed change order.] |
|--------|----|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

----

----

|   | 1. | Agreed Upon Change To Specification(s): [Identify Specification that will be changed.] |
|--------|----|----------------------------------------------------------------------------------------|

|   | 2. | Date Scope Change Effective:[State the date the change will be effective.] |
|--------|----|----------------------------------------------------------------------------|

|   | 3. | Describe Scope Change, including any Specifications:  [Describe the agreed upon change in full detail.] |
|--------|----|-------------------------------------------------------------------------------------------------------------------|

|   | 4. | Revised price, payment schedule, and delivery schedule, if any, of the proposed change: [State any changes to the original delivery schedule, original price, and payment schedule.] |
|--------|----|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|

|   | 5. | Additional Terms and Conditions:  [State any terms and conditions that apply to the proposed change.] |
|--------|----|-----------------------------------------------------------------------------------------------------------------|

----

| Amdocs Software System Limited                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |   | Radcom, Ltd.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |   |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------|
| By:                                                                                   |   | By:                                                                                   |   |
| Printed Name:                                                                                                                                                                        |   | Printed Name:                                                                                                                                                                        |   |
| Title:                                                                                               |   | Title:                                                                                               |   |
| Date:                                                                                                     |   | Date:                                                                                                     |   |

----

| Change Order Number | Change Component | Priority(High, Med., Low) | Description of Change | Level of Effort | Comments | Status | Status Date |
|---------------------|------------------|---------------------------|-----------------------|-----------------|----------|--------|-------------|
|                |             |                      |                  |            |     |   |        |
|                |             |                      |                  |            |     |   |        |
|                |             |                      |                  |            |     |   |        |
|                |             |                      |                  |            |     |   |        |
|                |             |                      |                  |            |     |   |        |
|                |             |                      |                  |            |     |   |        |
|                |             |                      |                  |            |     |   |        |
|                |             |                      |                  |            |     |   |        |

----

----

| Appendix Q - Software Enhancement Notification Form (SEN) |
|-----------------------------------------------------------|

----

----

----

----

----

----

----

----

----

----

----

|   |
|--------|