US 7995589

I'll verify details against current sources, including any CAFC docket activity, while treating the patent number literally.

Let me check litigation history and any 2026 appellate activity more specifically.

US Patent 7,995,589 — Verification Summary

A note on methodology: I searched for the number exactly as given (7995589 / 7,995,589) and did not broaden to similar numbers. The authoritative source I relied on is the full-text record at patents.google.com/patent/US7995589/en and the issued-PDF front page at patentimages.storage.googleapis.com/.../US7995589.pdf.

---

Bibliographic data (high confidence)

Foreign family members: EP 1266516 B1, AU 2001245590 A1, WO 01/69899 A2.

---

Abstract (verbatim)

"A method and apparatus of communicating over a data network includes providing a user interface in a control system for call control and to display information relating to a call session. The control system communicates one or more control messages (e.g., Session Initiation Protocol or SIP messages) over the data network to establish a call session with a remote device in response to receipt of a request through the user interface. One or more commands are transmitted to a voice device associated with the control system to establish the call session between the voice device and the remote device over the data network. A Real-Time Protocol (RTP) link may be established between the voice device and the remote device."

---

Plain-language overview of the independent claims

The patent has four independent claims — 1, 11, 15, and 19 (claims 21–24 are dependent). The core inventive idea is split control and media: a computer ("control system") handles signaling (SIP) and the on-screen user interface, while a separate network telephone handles the actual audio/video media path (RTP) directly to the far end.

Claim 1 (method). Three steps: (a) put a user interface on a control system for setting up a session that carries audio and video; (b) the control system itself sends the network control messages (e.g., SIP) to establish the session with a remote device, triggered by a user request through that interface; and (c) the control system sends commands to a telephony device that is connected to the network and associated with the control system, so that the media session is set up between that telephony device and the remote device. In short: computer does the signaling, phone does the talking.

Claim 11 (method). Same architecture described as a workflow: the control system sends control messages to establish the session with the remote device (audio and video exchanged); sends commands to a network telephone; the session is established between the network telephone and the remote device; and information about the session is displayed on the control system. The distinguishing emphasis here is the displaying of session information on the controlling computer.

Claim 15 (system/apparatus). A system for controlling a user terminal on a data network, comprising: (a) a user interface with selectors for call control; (b) a controller that takes a request from the interface and generates messages to establish a call session with a remote device; and (c) an interface that transmits commands to the user terminal so a link is established between the user terminal and the remote device, with audio and video exchanged on that link.

Claim 19 (article of manufacture). A non-transitory machine-readable medium whose instructions cause a system to: provide a user interface showing call-session information; communicate control messages with a remote device to establish a multimedia (audio and video) session between a user terminal and the remote device; and control the user terminal during the call session.

Representative dependent claims: different message/command formats (cl. 2); RTP session (cl. 3, 22, 24); SIP messages (cl. 5, 13, 16, 20); storing the telephony device's IP address and port (cl. 6); receiving an indication from the telephony device to originate another call (cl. 7); GUI display (cl. 8, 12, 17); terminating via either interface or phone (cl. 9); displaying a caller/callee image (cl. 10, 18); call-control indicators (cl. 14).

---

Litigation history (relevant to your CAFC request)

• Genband US LLC v. Metaswitch Networks Corp. / Ltd., E.D. Tex. No. 2:14-cv-00033-JRG (filed Jan. 21, 2014). The '589 patent was one of seven asserted (also 6,772,210; 6,791,971; 6,885,658; 6,934,279; 7,047,561; 7,184,427; 7,990,984). A January 2016 jury found all asserted claims infringed and not invalid and awarded $8,168,400. Source: Genband US LLC v. Metaswitch Networks Corp., 861 F.3d 1378 (Fed. Cir. 2017).
• CAFC No. 2017-1148 — Genband v. Metaswitch, decided July 10, 2017, vacating and remanding the district court's denial of a permanent injunction on the ground that the "drive demand" causal-nexus standard may have been applied too stringently. Precedential; opinion. Note: this appeal turned on injunctive relief standards, not on the validity or construction of the '589 claims.
• CAFC No. 2018-1869 is listed on the patent's Google Patents page as a Federal Circuit case associated with this family (2018 filing). I could not retrieve a substantive opinion for 2018-1869 in this session.
• Sonus Networks, Inc. v. Metaswitch Networks Ltd et al., E.D. Tex. No. 2:18-cv-00155 — this case also lists patent 7,995,589, per the Stanford NPE Litigation Database entry for 7995589. This is the same case docket linked from the Google Patents litigation section.

On the "CAFC 2026 docket" request: I found no 2026 Federal Circuit docket, appeal, or new litigation naming patent 7,995,589. My searches for a 2026 appeal returned no hits, and the patent's recorded legal status is Expired – Fee Related with an adjusted expiration of June 13, 2023. I cannot rule out an unnoticed 2026 filing, but I have no authoritative evidence of one. Please treat any assertion of 2026 CAFC activity on this patent as unverified unless a docket number is provided.

---

Explicit uncertainties

1. Claim set / post-grant amendment. The record shows 24 claims, with claims 21–24 phrased as narrower dependents (21→1, 22→1, 23→11, 24→15) using different wording style than claims 1–20. This pattern is typical of claims added in a post-grant proceeding (e.g., an ex parte reexamination certificate), and the "adjusted expiration" entry is consistent with that. However, I did not locate a reexamination certificate for 7,995,589 confirming this, so I cannot state as fact that claims 21–24 were added post-issuance. Treat the claim numbering as taken from the Google Patents full-text rendering.
2. "Audio and video" limitation. Claims 1, 11, 15, and 19 as rendered recite "audio and video data," while the abstract and specification speak primarily of voice/audio with multimedia as a broader category. If claims 21–24 were added by certificate, the earlier claims may have been amended to add the video language. I have not verified the original issued claim text for this point.
3. Assignee chain. The "as issued" assignee is Genband US LLC; the current assignee of record is Ribbon Communications Operating Company, Inc., following the Genband merger. The Google Patents page also shows an original assignee field of "Genband US LLC" and lists a Nortel Networks assignment chain (Aug. 2010), consistent with the Federal Circuit's statement that the patents were acquired from Nortel's bankruptcy.

I'll research litigation involving US patent 7995589 across litigation databases.

Let me dig into the specific case records identified.

Let me get the appellate and docket details.

Litigation Involving U.S. Patent No. 7,995,589

Patent identified: U.S. 7,995,589 B2, "Controlling voice communications over a data network" (Sollee et al.; filed 2005‑08‑23 as Ser. No. 11/210,084; granted 2011‑08‑09; continuation of U.S. Ser. No. 09/524,342, now U.S. 6,934,279). Original assignee Nortel Networks; later Genband US LLC; current record assignee Ribbon Communications Operating Company, Inc. In the litigation record this patent is referred to as the "'589 Patent," and the asserted claim was claim 15.

Based on the litigation-database entries I was able to retrieve (Stanford NPE Litigation Database, Unified Patents litigation portal, Justia/CourtListener dockets, and Federal Circuit opinions), the '589 patent was asserted in the following proceedings. I have flagged where my confidence is lower.

---

1. Genband US LLC v. Metaswitch Networks Corp. (and Metaswitch Networks Ltd.)

• Court / jurisdiction: U.S. District Court for the Eastern District of Texas, Marshall Division
• Case No.: 2:14‑cv‑00033
• Filed: January 21, 2014
• Plaintiff(s): Genband US LLC (and Genband Inc.), asserting patents acquired from Nortel
• Defendant(s): Metaswitch Networks Corp. / Metaswitch Networks Ltd.
• '589 patent involvement: Yes. The '589 Patent was one of seven patents asserted. The court's findings of fact confirm that claim 15 of the '589 Patent was tried to the jury.
• Outcome / status: Jury trial January 11–15, 2016; on January 15, 2016 the jury found Metaswitch infringed all asserted claims (including '589 claim 15) and that they were valid, awarding $8,168,400 in damages. After a bench trial on equitable defenses and injunction, the court (Sept. 29, 2016 opinion) rejected laches/implied waiver/estoppel but denied a permanent injunction. Final judgment entered March 22, 2018 (≈$8.9M in royalties plus interest/costs). Case listed as closed 04/10/2018.
• Sources: Ex Parte case page (2:14‑cv‑00033, "Filed 01/21/14… Closed (04/10/18)"); court's findings of fact/opinion (Justia PDF, E.D. Tex. No. 2:14‑cv‑00033); Ribbon/Sonus SEC filings.

2. Genband US LLC v. Metaswitch Networks Corp. — Federal Circuit No. 2017‑1148

• Court: U.S. Court of Appeals for the Federal Circuit
• Case No.: 2017‑1148
• Decided: July 10, 2017 (861 F.3d 1378)
• Parties: Genband US LLC (appellant) v. Metaswitch Networks Corp. (appellee)
• '589 patent involvement: Yes — the opinion expressly lists U.S. Patent No. 7,995,589 among the patents for which the jury found infringement.
• Outcome: Vacated and remanded. The Federal Circuit held it could not determine whether the district court applied too stringent a "causal nexus / drive demand" standard for irreparable harm, and remanded for reconsideration of the denial of a permanent injunction (including the effect of Genband's litigation-timing choices).
• Status: Decided; remanded to the district court.
• Sources: Fed. Cir. opinion (17‑1148, July 6/10, 2017 opinion PDF); Wiley Federal Circuit Patent Bulletin; CourtListener (861 F.3d 1378).

3. Federal Circuit appeal No. 2018‑1869 (Metaswitch's appeal of the 2:14‑cv‑00033 judgment)

• Court: U.S. Court of Appeals for the Federal Circuit
• Case No.: 2018‑1869
• '589 patent involvement: This appeal arises from the same 2:14‑cv‑00033 judgment that included the '589 patent (Metaswitch noticed an appeal of the April 2018 final judgment on April 19, 2018).
• Outcome / status: Uncertain on the specific disposition. The record shows a "JOINT NOTICE OF SETTLEMENT AND NOTICE OF STAY OF FEDERAL CIRCUIT APPEAL" filed April 25, 2019 in the related E.D. Tex. case, and the district court entered a settlement/dismissal order July 1, 2019, consistent with the appeal being resolved by settlement rather than decision. I could not retrieve a Federal Circuit merits opinion for 2018‑1869, so I will not state an outcome I cannot verify.

4. Sonus Networks, Inc. v. Metaswitch Networks Ltd. et al.

• Court / jurisdiction: U.S. District Court for the Eastern District of Texas (Marshall Division)
• Case No.: 2:18‑cv‑00155
• Filed: April 17–18, 2018 (docket shows complaint entered 04/18/2018)
• Plaintiff: Sonus Networks, Inc. (post‑merger, Ribbon Communications Inc.)
• Defendant(s): Metaswitch Networks Ltd. and Metaswitch Networks Corp.
• Presiding judge: Rodney Gilstrap (docket initially assigned to Judge Robert W. Schroeder, III)
• '589 patent involvement: Likely, but verify. The Stanford NPE Litigation Database entry for patent 7995589 lists this case ("Sonus Networks, Inc. v. Metaswitch Networks Ltd et al, 2:18‑cv‑00155, E.D. Tex.") as a case involving the '589 patent. This suit alleged continuing infringement of patents from the earlier 2:14‑cv‑00033 action (the "redesign" case) and also asserted false advertising.
• Outcome / status: Settled and dismissed with prejudice. Mediation resulted in a post‑mediation settlement (reported April 22, 2019); the parties filed a joint notice of settlement and stay of the Federal Circuit appeal (April 25, 2019); the court granted an agreed motion to dismiss with prejudice on July 1, 2019. Case status: Closed (termination date listed 06/30/2019).
• Sources: Unified Patents litigation portal (2:18‑cv‑00155); UniCourt and Justia dockets; Stanford NPE database; Ribbon/Sonus SEC 10‑Q disclosures.

---

Related but not '589-patent litigation (context only)

• Genband/Sonus v. Metaswitch trade-secret action, District Court of Dallas County, Texas (state court), filed March 28, 2017 — trade‑secret claims, not a '589‑patent suit.
• Two separate Sonus v. Metaswitch patent suits filed March 8, 2018 in the E.D. Tex., Marshall Division, asserting ten patents (with Metaswitch counterclaims asserting ten patents). These are distinct from 2:18‑cv‑00155. I did not retrieve case numbers or confirm '589 involvement in those two suits; treat as unverified.

---

Summary table

Confidence and caveats

• High confidence: Cases 1 and 2 — the '589 patent is expressly named in the Federal Circuit opinion, and claim 15 was identified as tried to the jury.
• Medium confidence: Case 4 — one database (Stanford NPE) links patent 7995589 to 2:18‑cv‑00155, but I could not retrieve the 2018 complaint to confirm that the '589 patent itself (as opposed to sibling patents) was actually asserted there.
• Low confidence / unverified: The precise disposition of Fed. Cir. 2018‑1869; whether the two March 8, 2018 Sonus suits asserted the '589 patent; and any foreign counterpart proceedings (e.g., the EP 1 266 516 counterpart existed but I found no litigation assertion of it).
• I did not identify any litigation in which patent 7,995,589 was asserted by a non‑practicing entity or against parties other than Metaswitch Networks. All identified assertions appear to be by the Genband/Sonus/Ribbon operating‑company side (a "product company" per the NPE database), not an NPE.
• I did not auto‑correct any identifiers; the patent number, case numbers, and docket numbers above are reproduced as found. Note that Sonus's filings reference slightly different filing dates for 2:18‑cv‑00155 (April 17 vs. April 18, 2018) — I have reported both as they appear in the sources.

If you need, I can attempt to pull the actual 2018 complaint exhibits and the Federal Circuit docket for 2018‑1869 to firm up the two open items above.

I'll research PTAB proceedings for US 7,995,589, since the structured ODP data shows no AIA trials but the patent text shows heavy litigation (TXED cases and two CAFC appeals), which often correlates with IPR activity.

I found significant litigation. Now let me pin down whether the IPRs filed by Metaswitch (IPR2015-01456/01457) targeted the '589 patent, and search for any other proceedings.

Proceedings overview

Zero AIA trial proceedings (IPR / PGR / CBM) have ever been filed, instituted, or decided on US 7,995,589. The USPTO Open Data Portal returns none, and targeted searching turned up none. The breakdown is therefore: 0 active, 0 claims invalidated, 0 claims sustained, 0 settled, 0 institution denials — because nothing was ever instituted against this patent. The bottom line for a defendant is not "the patent is hardened by PTAB wins," and it is not "the claims are dead." It is the third, less common posture: all claims 1–24 stand exactly as issued and have never been tested at the Board. The validity that was litigated for this patent in 2015–2016 was decided by an E.D. Tex. jury, not by the PTAB.

⚠️ False-positive flag. Web searching surfaces two IPRs in the same Genband/Metaswitch family — IPR2015-01456 and IPR2015-01457 — which a skimmer could mistake for proceedings on the '589 patent. They are not. Both were filed 2015-06-22 by Genband US LLC / Genband Management Services Corp. (as petitioner) against Metaswitch (as patent owner) and challenged US 8,687,640 B2 ("Controlling communication sessions"), a Metaswitch-owned patent at issue in the mirror case Metaswitch Networks, Ltd. v. Genband US LLC, No. 2:14-cv-744 (E.D. Tex.). The FWD in IPR2015-01456 (dated 2016-12-15, panel: Lee, Cocks, Kinder) held claims 1, 6, 7, 11–13, 19–21, 25–31 of the '640 patent unpatentable. Those proceedings do not touch US 7,995,589 and are listed here only to prevent misattribution. (FWD; Patexia summary)

---

No proceedings to enumerate (US 7,995,589)

There is no {PROCEEDING_NUMBER} to report — no petition was ever filed against this patent. For completeness, the litigation record (which is what exists) is summarized below, because that is where the patent's validity has been tested.

Related district-court litigation — Genband US LLC v. Metaswitch Networks Ltd. et al., No. 2:14-cv-33-JRG-RSP (E.D. Tex.)

• Filed: 2014 (docket no. 2:14-cv-00033, Marshall Division).
• Patents asserted: the '589 patent was one of eight patents-in-suit (U.S. Pat. Nos. 6,772,210; 6,791,971; 6,885,658; 6,934,279 (the '589 parent); 7,047,561; 7,184,427; 7,990,984; and 7,995,589). The court construed terms across these patents in two rounds (Claim Construction Order 2015-04-02; Supplemental Claim Construction Order 2015-08-06). (Supplemental Markman, Dkt. 310)
• Jury verdict: 2016-01-15 — the jury found Metaswitch infringed seven Genband patents, including the '589 patent, and confirmed the validity of the asserted patents; damages of $8.1M for January 2014–August 2015. Accused products included Metaswitch Session Border Controllers, Integrated Softswitches, Call Feature Servers, Universal Media Gateways, and the MTAS platform. (Genband press release via TelecomTV)
• Defensive note: a jury validity finding is not a PTAB FWD and does not create § 315(e) estoppel, but it does mean a district-court invalidity defense on this patent has already been run once and rejected by a jury.

Related appellate activity (per the patent record)

• CAFC No. 2017-1148 — appeal arising from the 2:14-cv-33 litigation (docket listed on the patent page).
• CAFC No. 2018-1869 — a later Federal Circuit appeal tied to the same family (docket listed on the patent page).
• CAFC No. 17-1148 / Texas E.D. 2:18-cv-00155 — a later E.D. Tex. action (2018) and a Federal Circuit appeal.

I was unable to confirm with high confidence, in this session, the specific dispositions/holdings of CAFC Nos. 17-1148 and 18-1869. The patent page lists them as litigation entries but not outcomes. Do not treat any characterization of those outcomes (affirmance, vacatur, remand) as verified here — pull the opinions from the Federal Circuit docket/CourtListener before relying on them.

---

Strategic summary

Claim status — every claim is UNTESTED, none canceled or narrowed. All 24 claims of US 7,995,589 (independent claims 1, 11, 15, 19 and their dependents) remain exactly as they issued on 2011-08-09. No claim has been canceled, disclaimed, or amended through any AIA trial or certificate-of-correction process that I can find. Contrast this with the "invalidated" posture the prompt anticipates: here the entire claim set is live record-wise, so a demand letter citing claims 1–5 is not citing dead claims. What is true is that the claims have never been stress-tested for § 102/§ 103 by the Board — a genuine IPR avenue remains open in principle (subject to the timing constraints below).

Estoppel landscape — there is essentially none against this patent. Because no IPR on the '589 reached an FWD, no petitioner is subject to § 315(e)(2) estoppel as to the '589 claims. Prior-art grounds that were used (or could have been used) against the sibling patents in the Genband/Metaswitch wars — e.g., the Ejzak, Intel, and Cisco references central to the '640 IPRs, or the Baum reference that drove the '561 claim-construction fight — are not precluded against the '589 claims. A current defendant therefore has the full universe of pre-2000-03-13 art available in district court, and anyone who has not previously filed an IPR on this patent can still file one (again, subject to § 315(b) and the patent's expiry).

Pattern signals. (1) The same corporate family (Genband/Nortel → Genband → Ribbon Communications) was on both sides of the Genband/Metaswitch patent war; Metaswitch challenged some Genband patents and Genband challenged Metaswitch's '640 patent — but neither side ever filed an IPR on the '589 patent. Its survival at the PTAB appears to be a matter of the parties' strategic choices, not a merits signal. (2) No defensive aggregator (e.g., Unified Patents) appears in the chain for this patent. (3) The patent record shows the family has been through multiple district-court and appellate rounds and is flagged for "family has litigation" — expect the owner (now Ribbon Communications Operating Company, Inc., formerly Genband US LLC) to have a well-developed validity narrative from the 2016 jury win. (4) The patent is expired (status "Expired – Fee Related"; adjusted expiration 2023-06-13), which materially caps exposure to past damages inside the § 286 six-year window and eliminates injunction risk.

---

Recommended next steps

• If you are a defendant: the "no PTAB activity" result cuts both ways. You are not automatically barred by anyone's estoppel, and you can still petition for IPR on the '589 claims. But because no claim has been invalidated, do not plan a defense around canceled claims — none exist. Build your invalidity case on art predating the 2000-03-13 priority date, and pull the CAFC opinions (Nos. 17-1148 and 18-1869) to confirm whether any claim construction from the E.D. Tex. case was affirmed/limited on appeal, since that construction would bind your infringement analysis.
• Timing / § 315(b): if you (or a privy/RPI) have already been served with a complaint alleging infringement of the '589 patent, the one-year IPR clock is running and, if it has lapsed, IPR is unavailable. Confirm service dates before budgeting a petition.
• Expiry point: given the 2023-06-13 adjusted expiration, an IPR that cancels claims may be of limited practical value (the patent is already expired and only past damages are at stake). Weigh the cost of an IPR against a district-court invalidity defense, especially since there is no estoppel to gain by not filing.
• Verify before relying: (i) confirm there truly is no AIA trial by checking PTAB E2E / PTACTS directly under the patent number and application 11/210,084; (ii) confirm the CAFC dispositions for Nos. 17-1148 and 18-1869 on CourtListener; (iii) check for any ex parte reexamination, which would not appear in the ODP AIA-trial feed.

Caveat on this analysis: I did not have a verified FWD, institution decision, or settlement document for US 7,995,589 to quote, because — on the available structured data and search results — none exists. Everything above about the '589 patent is drawn from the patent's own prosecution/litigation record and the Genband v. Metaswitch docket summaries; the PTAB findings quoted (claims held unpatentable in IPR2015-01456) belong to US 8,687,640, not to the '589 patent. If you need a definitive "no AIA trials" certification for a filing, pull the PTAB E2E record directly rather than relying on search.

I'll start by researching the assignment and litigation record for this patent to supplement the authoritative text I've been given.

Good — I found specific reel/frame references in the Genband v. Metaswitch litigation record. Let me dig further into the specific assignment for the '589 patent and the litigation parties.

Let me nail down the specific reel/frame for the '589 patent and identify the 2018 EDTX case and Federal Circuit appeals.

Ownership & Assignment Reconstruction — US 7,995,589 B2

Patent: "Controlling voice communications over a data network"
App. No. 11/210,084 (continuation of 09/524,342) · Filed 2005-08-23 · Issued 2011-08-09 · Priority 2000-03-13
Status: Expired – Fee Related (adjusted expiration 2023-06-13)

Research caveat, stated up front: I could retrieve the reel/frame only for the core Nortel→Genband links (they are recited verbatim in the Genband v. Metaswitch record and in a filed 37 CFR 3.73(b) statement). The numerous bank security filings appear on Google Patents legal events without reel/frame, and I could not retrieve the correspondent of record (recording attorney) for any link from the sources available. I flag every such gap below rather than invent a value. The USPTO Assignment Center could not be queried live within this session; verify each entry there.

---

Inventors

Pattern notes:

• Employer is an inference from the chain of title, not a face-of-patent residence listing I could verify. The parent application and its PCT counterpart were Nortel filings, so all four inventors are presumed Nortel employees.
• No evidence retrieved of inventors departing within 12 months of filing, and no inventor-assignment reel (inventor → Nortel) was located for this specific patent. The 2000 filing predates the Nortel collapse by ~9 years, so a "fire-sale preceded by inventor exodus" pattern does not apply here.

---

Original assignee

Nortel Networks Limited / Nortel Networks Corporation (Canada) — the operating entity that filed the March 2000 parent application.

• Business: Tier-1 telecom equipment vendor (optical, carrier VoIP, switching). Nortel's CVAS (Carrier VoIP and Application Solutions) unit shipped the softswitch/gateway/SIP products that the '589 claims map onto.
• Product embodying the claims: Yes — the CVAS "Succession" carrier VoIP line (softswitches, gateways, SIP application servers) is the commercial embodiment family litigated in Genband v. Metaswitch.
• Current status: Dissolved via bankruptcy. Chapter 11 filed January 2009 (Bankr. D. Del. 09-10138); assets sold piecemeal §§363. The CVAS unit — including the '589 patent — was sold to Genband via a "stalking-horse" agreement dated December 2009, deal closed 2010-05-28 for ~$182–282M.

Note on Google Patents: the "Original Assignee" field shows Genband US LLC because the patent issued (2011) after the Nortel→Genband assignment was recorded; the assignee at filing was Nortel. This is a grant-date snapshot, not the filing-time owner.

---

Assignment timeline

Chronological. "Recorded" dates are USPTO recording dates; Google Patents legal-event dates are recording dates unless noted. Entries marked [RF verified] have a reel/frame recited in a primary document; [RF not retrieved] means the source listed the event without reel/frame.

1. 2010-05-28 (executed) / recorded 2010-08-25 — Reel 024879/0519 [RF verified]

• Conveyance: Assignment of Assignors' Interest
• Assignor: NORTEL NETWORKS CORPORATION
• Assignee: GENBAND US LLC
• Correspondent: not retrievable from sources consulted.
• Context: Bankruptcy §363 asset sale — the CVAS portfolio (including the '589) transfers to the strategic buyer Genband.

2. recorded 2010-06-02 — Reel 024468/0507 (portfolio-level; applicability to '589 uncertain)

• Conveyance: Change of Name
• Assignor: GENBAND INC.
• Assignee: GENBAND US LLC
• Correspondent: not retrievable.
• Context: Change of name only. ⚠️ This reel is confirmed for the Genband portfolio (e.g., US 6,529,524), but the '589 was Nortel-owned until mid-2010, so Genband Inc. never held it; treat the '589 linkage as a family-level artifact.

3. recorded 2010-06-18 — Reel/frame not retrieved

• Conveyance: Patent Security Agreement
• Assignor: GENBAND US LLC
• Assignee: ONE EQUITY PARTNERS III, L.P., as Collateral Agent
• Correspondent: not retrievable.
• Context: Securitization — financing lien tied to the CVAS acquisition (One Equity Partners was Genband's co-investor).

4. recorded 2010-11-09 — Reel/frame not retrieved

• Conveyance: Security Agreement
• Assignor: GENBAND US LLC
• Assignee: COMERICA BANK
• Correspondent: not retrievable.
• Context: Securitization.

5. recorded 2012-03-30 — Reel 027992/0443 [RF verified]

• Conveyance: Corrective Assignment (corrects conveying-party data previously recorded at Reel 024879/0519)
• Assignor: NORTEL NETWORKS CORPORATION and NORTEL NETWORKS LIMITED
• Assignee: GENBAND US LLC
• Correspondent: not retrievable.
• Context: Clean-up of the bankruptcy transfer (adds the second Nortel entity as assignor).

6. recorded 2014-01-10 — Reel/frame not retrieved

• Conveyance: Release by Secured Party
• Assignor: ONE EQUITY PARTNERS III, L.P., as Collateral Agent
• Assignee: GENBAND US LLC
• Context: Lien release.

7. recorded 2016-07-06 — Reel/frame not retrieved

• Conveyance: Patent Security Agreement
• Assignor: GENBAND US LLC
• Assignee: SILICON VALLEY BANK, as Administrative Agent
• Context: Securitization (refinancing).

8. recorded 2016-07-07 — Reel/frame not retrieved

• Conveyance: Release and Reassignment of Patents
• Assignor: COMERICA BANK, as Agent
• Assignee: GENBAND US LLC
• Context: Lien release.

9. recorded 2017-01-03 — Reel/frame not retrieved

• Conveyance: Corrective Assignment (corrects patent no. previously recorded)
• Assignor: GENBAND US LLC
• Assignee: SILICON VALLEY BANK
• Context: Corrective to the SVB security agreement.

10. recorded 2017-12-29 — Reel/frame not retrieved

• Conveyance: Termination and Release of Patent Security Agreement
• Assignor: SILICON VALLEY BANK
• Assignee: GENBAND US LLC
• Context: Lien release (precedes the Sonus combination).

11. recorded 2018-01-02 — Reel/frame not retrieved

• Conveyance: Security Interest
• Assignor: GENBAND US LLC and SONUS NETWORKS, INC.
• Assignee: SILICON VALLEY BANK, as Administrative Agent
• Context: Securitization — note the joint grantors, reflecting the Sonus/Genband combination that became Ribbon.

12. recorded 2020-03-03 — Reel/frame not retrieved

• Conveyance: Security Interest
• Assignor: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
• Assignee: CITIZENS BANK, N.A., as Administrative Agent
• Context: Securitization.

13. recorded 2020-07-15 — Reel/frame not retrieved

• Conveyance: Merger
• Assignor: GENBAND US LLC
• Assignee: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
• Context: Internal reorg / corporate merger — Genband US LLC merged into the Ribbon operating entity. (This is the ownership link to the current assignee.)

14. recorded 2021-12-06 — Reel/frame not retrieved

• Conveyance: Termination and Release of Patent Security Agreement
• Assignor: SILICON VALLEY BANK
• Assignee: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (f/k/a Genband US LLC and Sonus Networks, Inc.)
• Context: Lien release.

15. recorded 2024-06-24 — Reel/frame not retrieved

• Conveyance: Release by Secured Party
• Assignor: CITIZENS BANK, N.A.
• Assignee: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
• Context: Lien release.

Bottom line on ownership: There is no recorded transfer of the '589 patent to any licensing-only entity. Every lien in entries 3–15 is a financing security interest, not an ownership conveyance; the only true ownership transfers are Nortel → Genband (Reel 024879/0519) and Genband → Ribbon (2020 merger). The current owner of record is Ribbon Communications Operating Company, Inc., an operating telecom-software vendor.

---

Timeline diagram

timeline
    title Ownership of US 7995589
    2000 : Parent application filed by Nortel
    2005 : Continuation application filed
    2009 : Nortel files for Chapter 11
    2010 : Nortel CVAS sold to Genband
         : Assignment recorded at reel 024879 frame 0519
         : Security interest to One Equity Partners
         : Security agreement to Comerica Bank
    2011 : Patent issues to Genband US LLC
    2012 : Corrective assignment reel 027992 frame 0443
    2014 : Genband sues Metaswitch in East Texas
    2016 : Jury finds Metaswitch infringes
    2017 : Genband and Sonus combine as Ribbon
    2018 : Joint security interest to Silicon Valley Bank
         : Additional East Texas case filed
    2020 : Genband merges into Ribbon Communications
         : Security interest to Citizens Bank
    2023 : Patent term ends

---

NPE / troll-pattern signals

1. Shell-entity transfer — NOT PRESENT. No assignee carries an "IP / Patents / Licensing / Holdings / Ventures" suffix. The chain runs Nortel → Genband → Ribbon, all operating telecom vendors (Reel 024879/0519; 2020-07-15 merger). No single-member Delaware/Texas LLC, no registered-agent address.

2. Known asserter in the chain — NOT PRESENT. None of the assignees — Nortel Networks Corporation/Limited, Genband US LLC, Ribbon Communications Operating Company — appears on any Acacia / Marathon / IV / Wi-LAN / Conversant / Vringo / Pendrell / Round Rock / Spangenberg list, or in the RPX/Unified high-frequency-plaintiff registries. Genband was a serial filer, but as a practicing competitor (see Verdict).

3. Repeat correspondent across the chain — UNCLEAR / not analysable. The correspondent of record was not retrievable from the sources I could reach; the Google Patents legal-event entries for the security filings omit it. I will not name an attorney I cannot source. This is the one signal that would require direct Assignment Center access to close out.

4. Cascading transfers through chained LLCs in <24 months — NOT PRESENT. The only inter-entity ownership moves are the 2010 Nortel→Genband sale and the 2020 Genband→Ribbon merger — 10 years apart, both to named operating companies. The intervening recordings (2010→2024) are liens and lien releases, not transfers.

5. Pre-litigation transfer (<6 months before first suit) — NOT PRESENT. The ownership link (Reel 024879/0519) was executed 2010-05-28 and recorded 2010-08-25; the first suit asserting the '589 (Genband v. Metaswitch, E.D. Tex. 2:14-cv-00033) was filed January 2014 — roughly 3.5 years later. The transfer was not arranged to enable the suit.

6. Bankruptcy fire-sale — PRESENT (factually), but strategically purchased. Nortel filed Chapter 11 in Jan 2009; the CVAS unit and the '589 were sold through a stalking-horse §363 sale (Dec 2009 agreement; closed 2010-05-28) for ~$182–282M. The buyer was a competing operating company (Genband), not an NPE, so the signal fires as a mechanism but does not indicate troll acquisition.

7. Privateering — NOT PRESENT. Genband asserted the portfolio directly (in its own name) against a competitor; there is no transfer to an NPE to assert on its behalf. No NPE intermediary exists anywhere in the chain.

8. Defensive aggregator (anti-NPE) — NOT PRESENT. The chain terminates at Ribbon Communications Operating Company, Inc., not at RPX, AST, LOT, Unified, or OIN. The patent was not neutralized defensively.

---

Verdict

Operating-company assertion.

The chain is Nortel → Genband US LLC (Reel 024879/0519, executed 2010-05-28) → Ribbon Communications Operating Company, Inc. (2020-07-15 merger) — three operating telecom-equipment vendors, with every other recorded event a financing lien or lien release, and no shell entity, no known NPE, and no defensive aggregator anywhere in the record. Genband used the patent offensively, but as a market competitor: the Jan 2014 E.D. Tex. suit (2:14-cv-00033) asserted claim 15 of the '589 against Metaswitch, a rival in the session-border-controller/softswitch market, producing a Jan 15, 2016 jury verdict of infringement ($8.17M) later narrowed on appeal (Fed. Cir. 17-1148, 861 F.3d 1378). The presence of a bankruptcy-sale link is explained by the buyer being a strategic operating company, not an NPE — so the pattern points to a practicing-entity assertion, not a troll chain.

Verify at: USPTO Patent Assignment Center — https://assignmentcenter.uspto.gov/ · Assignment Search — https://assignment.uspto.gov/patent/index.html#/search?q=[7995589](/patent/7995589) · Google Patents — https://patents.google.com/patent/US7995589/en

Open items to close at Assignment Center (not resolvable from the sources available): (a) the correspondent of record for each of entries 1–15; (b) reel/frame for the security filings (entries 3, 4, 6–15); (c) confirmation of whether the Genband Inc. change-of-name reel (024468/0507) actually attaches to the '589 or is a family-level artifact.

I'll start by locating the patent itself and then verifying the key prior-art references before doing the anticipation analysis.

The patent and several key references are confirmed. Let me verify a few more of the cited references so the descriptions and dates are grounded rather than inferred from titles.

Prior-Art Analysis — U.S. Patent No. 7,995,589 B2

Note on the record and method. I could not open USPTO PatentCenter/PatFT directly in this session; the bibliographic and citation data below come from the full text you supplied and from the Google Patents record for US7995589B2 (https://patents.google.com/patent/US7995589/en and https://patentimages.storage.googleapis.com/42/82/f8/a0a35f641797be/US7995589.pdf), which mirrors the USPTO/EPO bibliographic data. I searched for the exact number 7995589 and did not substitute any similar-number record. Where I verified an individual cited reference through a second source I say so; where a description is derived only from the reference's own title I flag it.

---

1. The reference at issue (building on prior sections, not repeated)

Independent claims: 1, 11, 15, 19. All four recite, in substance, (i) a control system with a user interface, (ii) the control system sending control messages over the data network to a remote device to establish a call session, and (iii) commands sent to a separate telephony device / user terminal to establish the call session (RTP link) between that telephony device and the remote device. The granted claims add that audio and video data are exchanged in the session.

2. Critical date — this governs everything

The effective filing date is 2000-03-13 (the parent). Consequently:

• A reference is only §102 prior art if it was patented/published before 2000-03-13 ("§102(a)/(b)"), or is a U.S. patent granted on an application filed before 2000-03-13 ("§102(e)").
• References whose earliest priority date post-dates 2000-03-13 are not §102 prior art on this record — they are cited parenthetically/for background only. In this list that means: US 7,243,162 (2000-03-24), US 6,421,424 (2000-06-05), US 6,765,912 (2000-08-08), US 7,058,068 (2000-11-30), US 7,532,628 (2002-12-30), US 7,315,742 (2003-12-15), US 7,313,133 (2005-05-12).
• Alternative date to check: if the "audio and video data" limitation added in the continuation were held to lack written-description support in the 2000 parent, the effective date for claims 1/11/15/19 would be 2005-08-23, which would (a) remove the entire pre-2000 body of art's §102(b)/§102(a) effect for those claims and (b) potentially revive US 7,532,628, US 7,315,742 and US 7,313,133. The specification does discuss "video conferencing" and "multimedia (e.g., audio and video)" sessions, so support is likely, but this is the single most important validity fork.

3. Every patent citation on US 7,995,589, with §102 assessment

"Potentially anticipates" = a single-reference §102 theory is colorable for at least the named claim; "§103-relevant" = discloses elements but not the full claim. Descriptions marked (title-based) are inferred from the reference's own title because I could not open the full text.

4. Deep dive on the most relevant prior art

A. US 7,068,641 B1 — the closest reference (claim 1, 11, 15, 19).
Verified architecture: a PC ("network interface" on a processing entity) presents the user interface for the telephone, exchanges elemental control messages with the internet telephone over the IP network, and establishes a call between the telephone and a called station. This maps onto:

• claim 1(a) control system + user interface — disclosed (NI drives UI/visual/audio feedback);
• claim 1(b) control system sends control messages over the data network to a remote device — at least closely approached (NI establishes the call; the telephone and data services are addressed on the IP network);
• claim 1(c) commands to a separate telephony device to establish the session — disclosed (elemental control messages to the IT).
  Caveat: the "video" requirement and the precise split of signaling between the NI and the remote endpoint need element-by-element verification, and because this patent is expressly incorporated by reference, a §102(e) attack must treat it strictly as a separate prior-art document (its date, 1999-05-05 filing, precedes the critical date, so it qualifies).

B. US 6,549,621 B1 (Nortel) — best "computer controls a telephone" reference, but wrong transport. Verified that the computer generates call-control messages (ISDN) to a loop interface device toward the switch. It fails the "over the data network (packet) between the telephony device and the remote device" element and has no video — so it is §103 fodder (e.g., combined with a SIP reference such as US 6,678,735 or RFC 2543), not a clean §102 reference.

C. US 6,337,858 and US 6,430,282 (Nortel) — the "originate two legs and bridge" family. Both verified: a data terminal/voice button triggers a network server to originate calls, but the calls are bridged at the server/switch, not established as an end-to-end session between a telephony device and a remote device. This is a structurally different topology from claim 1(c), and neither shows video. §103-relevant, not anticipating.

D. US 6,678,735 (Nortel, SIP client manager) and US 7,120,141 (Genesys, SIP control messaging). These supply the SIP element (claims 5, 13, 16, 20) and (for US 6,678,735) explicit audio/video/whiteboard media descriptors, i.e., the multimedia element of claims 1/11/15/19. Individually they do not disclose the control-system → remote-device → separate-telephone command flow.

E. Multimedia references (US 5,712,906; US 6,430,176). These are the best single references for the "audio and video / multimedia" limitation, but each fails the "control system sends commands to a separate network telephony device" architecture. Useful in combination.

F. EP 0 829 995 (LAN telephone system) and EP 0 836 295 (controlling a switch over a digital information network). Both are earlier (1996 priorities) and are the best pre-1997 art for the general notion of controlling telephony endpoints over a data network; both would need to be read with a SIP/multimedia reference for a §103 case, and neither anticipates.

5. Non-patent literature (printed publications, §102(b) where >1 year pre-critical-date)

The 31 NPL citations include the IETF RFCs that define the invention's vocabulary — RFC 793 (TCP, Sep 1981), RFC 768 (UDP, Aug 1980), RFC 791 (IP, Sep 1981), RFC 2460 (IPv6, Dec 1998), RFC 2205 (RSVP, Sep 1997), RFC 1889 (RTP, Jan 1996), RFC 2326 (RTSP, Apr 1998), RFC 2327 (SDP, Apr 1998) and RFC 2543 (SIP, Mar 1999). The pre-March-1999 items are printed publications more than one year before the 2000-03-13 filing (§102(b)); RFC 2543 (Mar 1999) is right at the one-year boundary and is better treated as §102(a) or as evidence of the state of the art. None of these alone anticipates claims 1/11/15/19 because they describe protocols, not the claimed control-system/telephony-device architecture.

6. Bottom line and caveats

1. Most relevant single reference: US 7,068,641 B1 (Nortel), which is also incorporated by reference into the specification. It is the only cited reference that discloses a computer/control system presenting the telephone's user interface and driving a separate network telephone with control messages over an IP data network, and it predates the critical date (filed 1999-05-05) so it is §102(e)-eligible.
2. Best §103 combinations: US 6,549,621 or US 6,337,858/US 6,430,282 (computer-originated/controlled call) + US 6,678,735 or RFC 2543 (SIP) + US 5,712,906 or US 6,430,176 (multimedia/audio+video).
3. No cited reference is a clean, full anticipator of claims 1/11/15/19 on the face of the record, principally because the claims require the combination of (a) a control system's user interface, (b) control messages to a remote device over the data network, and (c) commands to a separate telephony device that exchanges both audio and video with the remote device — and each reference tends to have (a)+(c) on a PSTN/ISDN transport (US 6,549,621) or (a)+(b) with server-side bridging (US 6,337,858 / US 6,430,282).
4. Seven of the 37 citations (US 7,243,162; US 6,421,424; US 6,765,912; US 7,058,068; US 7,532,628; US 7,315,742; US 7,313,133) are post-critical-date and are not §102 prior art against the 2000-03-13 priority; they would matter only if the effective date for the video-bearing claims slips to 2005-08-23.

Explicit limitations of this analysis. I verified the full text/abstract of US 6,549,621, US 6,337,858, US 6,430,282 (via EP 0 852 872), US 7,068,641, US 6,678,735 and US 6,430,176. Descriptions of the remaining references are taken from the citation table in the ‘589 patent itself and from the references' titles, and are flagged (title-based); I did not open each of those documents, and no element-by-element §102 chart has been prepared for them. "Potentially anticipates" is used only where the title/abstract/verified text supports every limitation; otherwise the entry is labeled §103-relevant. Determining true anticipation requires reading each reference against each of claims 1–24 in full — this document is an analyst's screening, not a legal opinion.

I'll ground this analysis by verifying what several key cited references actually disclose before mapping them to the claims.

Obviousness Analysis — U.S. Patent No. 7,995,589 B2 ("Controlling voice communications over a data network")

Analyst note on method. This analysis maps the issued claims against the references that appear on the face of the patent (the "Citations (37)" and "Non-Patent Citations (31)" sections of the Google Patents record). I verified the disclosures of US 6,337,858, US 6,549,621, US 6,614,899, US 6,678,735, and US 6,091,808 by retrieval; for the remaining references I characterize them from their titles, abstracts, and known content and flag where full-text verification is required. Anything below that contradicts the authoritative full patent text in the record should be resolved in favor of that text.

---

1. Legal framework and claim construction

• Governing standard: Because the application was filed August 23, 2005 as a continuation of Ser. No. 09/524,342 (filed March 13, 2000, now US 6,934,279), the effective filing date is March 13, 2000. Pre-AIA 35 U.S.C. § 103 applies.
• Graham factors: scope/content of prior art; differences between prior art and claims; PHOSITA level; secondary considerations. KSR Int'l v. Teleflex (2007) supplies the rationales (predictable combination of known elements; design incentive; finite number of identified, predictable solutions; "obvious to try").
• Claim 1 is the representative claim. Its limitations are:
  1. (a) a user interface in a control system for establishing a call session in which audio and video data are communicated;
  2. (b) the control system communicates control messages over the data network to establish the call session with a remote device, in response to a request through the user interface; and
  3. (c) the control system transmits commands to a telephony device "connected to the data network and associated with the control system" to establish the call session between the telephony device and the remote device ... to exchange the audio data and video data.
• The patent's own Background supplies the stated problem/motivation: network telephones have superior voice quality (dedicated DSPs) but "do not provide desired multimedia presentation capabilities such as those offered by displays of computer systems," while computers "suffer from relatively poor speech processing performance." That admission is itself evidence of a known design need (KSR; In re Berg line of cases).

Key construction points. (i) "control system" and "telephony device" are separate, networked elements; (ii) the media path bypasses the control system (the RTP link runs "directly between the network telephone ... and the remote system"); (iii) "audio and video data" is a genuine narrowing element, not mere environment; (iv) a "call session" expressly covers voice or multimedia sessions.

---

2. The prior art landscape (as listed on the patent)

2.1 Primary references (control/GUI on a computer, telephony device as media endpoint)

2.2 Multimedia / audio-plus-video references

• US 5,712,906 (Bell Atlantic) — Communications systems supporting shared multimedia session (link) — multimedia (audio + video) session sharing.
• US 6,526,129 B1 (Nortel) — System and method for communication media management (link) — selecting/managing media types for a call.
• US 6,430,176 B1 (Nortel) — Multimedia channel management through PSTN signaling (link).

2.3 Call-control/bearer separation and SIP-in-call-center art

• EP 1 109 368 A2 (Nortel) — Support of bearer path services in a distributed control network (link) — decomposition of bearer (media) path from the control layer, the very architecture claim 1 embodies.
• US 7,120,141 B2 (Genesys) — Integrating SIP control messaging into existing communication center routing infrastructure (link) — SIP messaging driving call establishment/transfer in an existing telephony infrastructure.
• US 6,363,065 B1 (Quintum); WO 1999/005590 A2 (Starvox) — VoIP gateway apparatus (links, WO1999005590A2).

2.4 Non-patent literature (all 102(b) except where noted)

• Catchpole, "Introduction to Computer Telephony Integration," British Telecommunications Engineering, Vol. 14, No. 2, pp. 98–105 (July 1995) — the canonical CTI teaching: a computer provides the user interface/status display and call control while a separate telephone/switch handles the voice path.
• Boullet, "Voice Over IP in Alcatel OmniPCX 4400 and OmniOffice," Alcatel Telecommunications Review, pp. 7–11 (Jan. 1, 2000) — VoIP + CTI in a PBX/IP-telephone product family (102(a) as of Jan. 2000, since it is within one year of the filing date; verifiable and not commonly owned).
• Thom, "H.323: The Multimedia Communications Standard for Local Area Networks," IEEE Communications Magazine, Vol. 34, No. 12, pp. 52–56 (Dec. 1996) — audio and video multimedia terminals over a LAN with separate call-signaling and media channels.
• M. Handley et al., "SIP: Session Initiation Protocol," RFC 2543 (Mar. 1999) — INVITE/ACK/BYE/200 OK, SDP session descriptions, proxies, user agents (rfc2543).
• H. Schulzrinne et al., "RTP: A Transport Protocol for Real-Time Applications," RFC 1889 (Jan. 1996) (rfc1889).
• Handley et al., SDP, RFC 2327 (Apr. 1998) (rfc2327); RSVP RFC 2205; RTSP RFC 2326; TCP RFC 793; UDP RFC 768; IP RFC 791; IPv6 RFC 2460.
• Sparks et al., "SIP Telephony Service Examples With Call Flows," Internet Draft (Oct. 1999) — worked SIP Internet-telephony call flows.
• Foo et al., "A Telephone Adapter for Internet Telephony Systems," Microprocessors and Microsystems, Vol. 21, No. 4, pp. 213–221 (Dec. 30, 1997) — a hardware telephone adapter coupling a conventional telephone to an Internet-telephony system via a computer.
• Donovan, "The SIP Info Method" (June 1999 / Feb. 2000); Petrack, "The PINT Service Protocol" (Oct. 14, 1999); Kuthan, "Sample Uses of SIP Info" (Oct. 17, 1999); "Comparison of H.323 and SIP" (≤ Feb. 3, 2000); Crowcroft, "Comments About H.323 and SIP" (Jan. 22, 1998).
• "Unified Networks IP Stimulus Protocol," Draft v2.1, Dec. 7, 1999, and Ser. No. 09/307,356 (US 7,068,641), incorporated by reference — the phone↔controller stimulus protocol. (These are the applicant's own materials/incorporations and are not usable as § 103 art against the same inventive entity, but they prove the protocol's pre-existing availability.)

---

3. The core combination

Combination C1 — the "representative" rejection

US 6,614,899 + RFC 2543 (SIP) + RFC 1889 (RTP) + Thom (H.323); optionally + US 6,678,735 and US 6,549,621.

Combination C2 — "printed-publication" rejection (no common-ownership exposure)

Catchpole (CTI) + Boullet (VoIP/CTI, Jan. 2000) + RFC 2543 + RFC 1889 + Thom (H.323) + EP 0 836 295 (IBM) / EP 0 829 995 (Sphere) + US 5,712,906 (Bell Atlantic).

This is the combination a challenger should prefer, because every reference is a printed publication (102(a)/(b)) and thus immune to the § 103(c) common-ownership carve-out discussed in § 6 below. Boullet in particular teaches the marriage of VoIP and CTI in a product line with IP telephones and PC-based call control — i.e., the exact "IP phone for voice, PC for control/display" architecture claim 1 recites.

Combination C3 — SIP-specific claims (5, 13, 16, 20)

Any of C1/C2 + RFC 2543 (SIP), or US 6,678,735 (SIP client manager; expressly "creating, modifying, and terminating sessions ... Internet telephone calls ... audio, video"), or US 7,120,141 (SIP control messaging in an existing telephony infrastructure). Motivation: SIP is the IETF standard expressly designed to "establish, maintain, and terminate multimedia sessions over a data network" — a finite, identified solution set (SIP vs. H.323) that the art itself compares ("Comparison of H.323 and SIP").

Combination C4 — RTP claims (3, 22, 24)

Any of C1–C3 + RFC 1889. The patent's own specification states the voice path "may be an RTP link," and RFC 1889 is the standard real-time transport for such sessions.

Combination C5 — control/bearer separation

Any of C1–C4 + EP 1 109 368 A2 (Nortel, Dec. 1999) (bearer path services in a distributed control network) and/or US 6,337,858 — to supply the express teaching that the call-control signaling and the media (bearer) path are established and managed separately, which is the heart of claim 1(c).

---

4. Dependent-claim mapping

---

5. Motivation to combine (why a PHOSITA would have done this)

1. The problem was known and its solution was conventional. The patent's own Background admits that network telephones give superior voice but poor multimedia presentation, and computers give superior presentation but poor voice processing. KSR treats a known design need plus a finite set of known solutions as compelling evidence of obviousness.
2. CTI is precisely the claimed split. Catchpole (1995) teaches offloading control and display to a computer while the telephone/switch handles the voice path. US 6,549,621 implements exactly that: the computer generates the call-control message; the telephone is the endpoint.
3. The industry was already moving control to the network/PC. US 6,337,858 (CTI hardware separate from the PSTN; VoIP gateway; control from the data network), US 6,091,808 (browser-based call control), and EP 1 109 368 (bearer/control decomposition) all push call control into software on a data network — the same direction as claim 1.
4. Boullet shows the two technologies had already been merged in a shipping product family (OmniPCX 4400 / OmniOffice, Jan. 2000), removing any "separate worlds" argument between CTI and VoIP.
5. SIP was the predictable choice. RFC 2543 is an IETF standard expressly for establishing Internet telephony and multimedia sessions; the art itself compares H.323 with SIP. Where the prior art discloses a finite number of identified solutions, selecting one is obvious under KSR.
6. RTP was the standard media transport. RFC 1889 supplies the real-time transport, and the patent concedes the RTP link.
7. Video was an established multimedia capability. Thom (H.323) standardizes audio and video terminals on a LAN; US 5,712,906 and US 6,526,129 teach multimedia/media-type negotiation. Adding video to the terminal is a predictable use of existing multimedia capability, particularly where the user interface is on a computer display (the very rationale the patent gives for its own invention).

Expected success / reasonable expectation: combining a known CTI control architecture, a known IP telephone endpoint, a standardized signaling protocol (SIP), and a standardized transport (RTP) to yield "good voice/video at the endpoint + good GUI at the computer" is a predictable aggregation of known elements (KSR; Perfect Web Techs. v. InfoUSA).

---

6. Caveats, dates, and defensive considerations a challenger must address

1. § 103(c) common ownership — the biggest risk to C1. Pre-AIA § 103(c)(1) excludes § 102(e)/(f)/(g) art that was commonly owned at the time the invention was made. The most on-point references are all Nortel: US 6,614,899 (filed 2000‑01‑31), US 6,678,735 (filed 2000‑01‑26), US 6,549,621 (filed 1999‑07‑26), plus US 7,110,391 (2000‑03‑03) and US 6,944,150 (2000‑02‑28). The '589 patent itself was assigned to Genband from Nortel Networks Corporation / Nortel Networks Limited (see the assignment history in the record). If those references and the '589 patent were commonly owned at the time of invention, they are disqualified as § 103 art. This is why Combination C2 (printed publications only: Catchpole, Boullet, Thom, RFC 2543, RFC 1889, EP 0 836 295, EP 0 829 995, US 5,712,906) is the tactically superior attack.
2. 102(e) timing. US 6,614,899 and US 6,678,735 were filed barely six weeks before the March 13, 2000 priority date. Even setting aside § 103(c), the applicant could attempt to swear behind under pre-AIA Rule 131 if it can document an earlier invention date.
3. References that are not prior art and must be discarded: US 7,243,162 (filed 2000‑03‑24), US 6,421,424 (2000‑06‑05), US 6,765,912 (2000‑08‑08), US 7,058,068 (2000‑11‑30), US 7,532,628 (2002‑12‑30), US 7,315,742 (2003‑12‑15), US 7,313,133 (2005‑05‑12), and the 2007 EPO search report / 2009 EPO examination report (not prior art at all). Note also that the patent lists these among its citations; a careful analyst must strip them out.
4. The "audio and video" limitation is the strongest non-obviousness argument available to the patentee. Most CTI/VoIP references of the era are voice-only. The video element must be met by H.323/Thom, US 5,712,906, US 6,526,129 or US 6,430,176 — and specifically for the telephony device exchanging video with the remote device. Full-text verification is needed to confirm that at least one reference teaches a dedicated IP telephone/videophone endpoint (rather than a PC) exchanging video.
5. Claim 10/18 ("image of the caller or callee") is the least well-mapped element against the listed references; a challenger should confirm against the CTI screen-pop and video-telephony literature before asserting it.
6. Admissions in the specification. The applicant's description of SIP, H.323, RTP, SDP, RSVP, the "Unified Networks IP Stimulus Protocol," and the separate-format phone↔controller channel can all be used as admissions of what a PHOSITA knew — useful for claim 2 and 4 in particular.
7. Secondary considerations. No compelling nexus evidence appears in the record. Note that the listed litigation (T.E.D. 2:14‑cv‑00033 and 2:18‑cv‑00155; Fed. Cir. 17‑1148 and 18‑1869) is not a § 103 objective indicium; however, a challenger should check whether these claims were previously construed or held valid, to avoid collateral estoppel or estoppel arguments.
8. Status. The patent is recorded as Expired – Fee Related (adjusted expiration June 13, 2023). A § 103 analysis at this point is retrospective (e.g., for a validity opinion, portfolio diligence, or a collateral challenge), not for procurement.

---

7. Bottom line

Claim 1 — a computer-side user interface that drives SIP control signaling over a data network to a remote device while sending commands to a separate IP telephony endpoint that carries the RTP audio/video session — is, on the listed prior art, a predictable combination of known elements for which the art supplied a clear motivation (the acknowledged voice-quality vs. display-quality tradeoff, plus the CTI, VoIP, H.323 and SIP teachings). The strongest, cleanest rejection is Combination C2 (Catchpole + Boullet + RFC 2543 + RFC 1889 + Thom, with EP 0 836 295 / EP 0 829 995 / US 5,712,906 for the LAN-endpoint and multimedia elements). The most likely allowance-saving distinction for the patentee is the recitation that audio and video are exchanged by the telephony device (rather than by the PC), plus any showing that the specific IP-endpoint-plus-PC-control integration was not suggested; the challenger should therefore focus discovery on the H.323 videophone and multimedia-session references and on the Alcatel/BT publications (Boullet, Catchpole), which are printed art unaffected by the § 103(c) common-ownership issue that clouds the Nortel 102(e) references.