Predictika · Session border controller license quotes

An AI sales agent's SBC SWe Lite license quote, checked before it goes out

An AI sales agent prepares a license quote for a software session border controller: the deployment type, the media-service tier, the session packs, any transcoding top-up, recording, codec and registration licenses. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published licensing rules and returns a verdict, every reason and the figures it computed.

Scope: Ribbon SBC SWe Lite license quotes: on-premises or public cloud licenses, the -SG, -SGX and -SP media-service tiers, session packs, -ME top-ups, SIPREC recording, AMR-WB, registrations and license format. See everything this validator covers

This validator models license quotes for Ribbon SBC SWe Lite as described in the Ribbon public SBC Edge documentation (Working with Licenses, read October 5, 2026), not just the scenarios shown below.

  • Deployment and base — cloud licenses cannot be assigned to an on-premises instance and on-premises licenses cannot be assigned to a public cloud instance; the base license is required; the trial license is for non-production use only; version 2 license files cannot be used on release 8.0.4 or later (or 8.1.5 or later).
  • Sessions and media services — SIP session licenses come in packs of 5, 10, 25 and 100 in three tiers: -SG (no encryption or manipulation), -SGX (encryption and partial manipulation, no transcoding) and -SP (full media services with transcoding). -ME top-up licenses add transcoding and encryption to existing -SG or -SGX sessions and add nothing to -SP sessions.
  • Other licenses — SIPREC recording packs add recording to existing SIP sessions; AMR-WB is a separate per-instance license; registrations are sold in packs of 100, with listed limits of 1,000 (under 1.5 GiB of memory) or 5,000 (1.5 GiB or more); -SG-Cloud licenses are not for Microsoft Teams Direct Routing.

Any SBC SWe Lite license quote that touches these rules is in scope — not only the scenarios pictured here. Not covered: prices (Ribbon publishes no list prices, so this validator produces no price build-up or line-item quote), SBC SWe Edge, SBC 1000 and 2000 and other Ribbon products, high-availability pairs, the licenses that Release 9.0 enables by default, and support contracts. Assumptions: that ME top-ups cannot exceed the base sessions and that recording packs cannot exceed the SIP sessions are read from the documentation's wording that they add to existing sessions.

The AI sales agentBuilds the SBC license quote from the conversation and says it is ready.
Predictika validatorChecks every rule at once and returns the verdict, each finding, and the computed figures.

7 scenarios in 3 groups · each group runs from the agent’s first attempt to the outcome · click one to switch

What the agent proposes

The AI sales agent says

Illustrative agent statement. The validator receives the structured request below.

Proposing agent: AI sales agent (scripted)

Before sending, the agent must call Recorded run

Predictika validator


      

        
        
        
      

      
Waiting for the call.

      
    

  

  
  

    
Where rules-based CPQ gets it wrong
Click to expand
    
Our assessment of what a typical rules-based CPQ (product rules, price rules and validation rules, as in Salesforce CPQ) does with the same cases. It is a judgment about effort and reliability, not a claim that nothing can be built.

    
What the validator caughtTypical rules-based CPQPredictika
Licenses that are different for cloud and on-premisesOnly with care
Each deployment type has its own set of license items, so a rep can easily pick the wrong family; a rule has to compare the two on every quote.		A cloud license on an on-premises quote, or the reverse, is a blocking finding in the same pass as the other rules.
A tier that decides which media services are licensedOnly with workarounds
Whether a session can be transcoded or encrypted depends on its tier and on any top-up, so the number of capable sessions has to be worked out before it can be compared with the need.		The sessions with transcoding and with encryption are computed from the tier and the top-ups and compared with what the customer needs.
Items that only add to existing sessionsOnly with care
Top-up and recording licenses make sense only next to enough base sessions, which is a quantity comparison across lines rather than a rule on one item.		Top-up or recording sessions above the SIP sessions on the quote are a blocking finding.
A limit that depends on memoryOnly with workarounds
The registration limit changes with the memory size on the quote, so the quote needs that field and a rule that picks the right limit.		Registrations above the limit for the stated memory go to a person for approval.
Every problem returned in one answerOnly with workarounds
Rules tend to fire as the quote is saved or a step is completed, so a rep often fixes one error and meets the next.		All findings come back together, whatever order the choices arrived in.

  

  

    
What this validator catches: findings from its test cases
Click to expand
    
Every rule is checked on every call, in any order the choices arrive; one problem never hides another. Blocking findings stop the quote; approval findings need a person to sign off; everything else is computed.

    
1The customer needs 20 sessions with transcoding, but the licenses cover 0; -SG and -SGX sessions have no transcoding unless covered by -ME top-up licenses.
2The customer needs 20 sessions with media encryption, but the licenses cover 0; -SG sessions have no encryption unless covered by -ME top-up licenses.
3The licenses are for a different deployment type than the one quoted; Ribbon states that cloud licenses cannot be assigned to an on-premises instance and on-premises licenses cannot be assigned to a public cloud instance.
4The quote has no SBC SWe Lite base license; Ribbon lists the base license as required to activate the software.
5The quote has no SIP session licenses; the trial license of 5 sessions is for non-production use only.
6The quote relies on the trial license for a production deployment; Ribbon lists the trial licenses for non-production use only.
7The quote uses version 2 license files, but the planned release (8.0.4 or later, or 8.1.5 or later) needs version 3 licenses.
8The quote uses cloud -SG session licenses for Microsoft Teams Direct Routing; Ribbon warns not to apply -SG-Cloud licenses for Teams Direct Routing because functionality is limited.
9The customer needs 51 sessions with transcoding, but the licenses cover 50; -SG and -SGX sessions have no transcoding unless covered by -ME top-up licenses.
10The customer needs 10 recorded sessions, but the quote licenses recording for 0.
11The quote has 100 recording sessions but only 50 SIP sessions; Ribbon describes SIPREC licenses as adding call recording to existing SIP sessions.
12The customer needs the AMR-WB codec, but the quote has no AMR-WB license; Ribbon sells it as a separate per-instance license.
13The customer needs 250 SIP registrations, but the quote licenses 100; registration licenses are sold in packs of 100.
14The customer needs 1,100 SIP registrations; Ribbon lists up to 1,000 registrations for the memory size on the quote, so a person should confirm the sizing.
15The quote adds ME top-up licenses to -SP sessions; Ribbon states the ME licenses add no features to -SP sessions, so a person should confirm they are wanted.
16The quote has 100 ME top-up sessions but only 50 SIP sessions; Ribbon describes the ME licenses as adding transcoding and encryption to existing -SG or -SGX sessions.
17The customer needs 60 sessions with transcoding, but the licenses cover 50; -SG and -SGX sessions have no transcoding unless covered by -ME top-up licenses.
18The customer needs 5 recorded sessions, but the quote licenses recording for 0.

  

  

    
Scenarios and results
Click to expand
    
The recorded result of the validator for each scenario on this page: the request the AI agent sent, the verdict, and every finding, in the order they appear above.

    
1. Cloud deployment and transcoding: A cloud deployment quoted with on-premises -SGX licenses and a transcoding need

    
The agent's request. Please quote SBC SWe Lite for a public cloud deployment with on-premises licenses, -SGX media-service tier session packs (2 x 25), with the base license, 1 registration pack. The customer needs 30 sessions with transcoding, 40 with media encryption, 0 recorded sessions and 100 registrations on an instance with 2,048 MiB of memory. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Cloud and on-premises licenses mixed. The licenses are for a different deployment type than the one quoted; Ribbon states that cloud licenses cannot be assigned to an on-premises instance and on-premises licenses cannot be assigned to a public cloud instance.
    • 
      
  • Transcoding needed beyond the licensed sessions. The customer needs 30 sessions with transcoding, but the licenses cover 0; -SG and -SGX sessions have no transcoding unless covered by -ME top-up licenses.
    • 
    

    
2. Cloud deployment and transcoding: The agent resubmits after fixing the errors

    
The agent's request. Please quote SBC SWe Lite for a public cloud deployment with public cloud licenses, -SGX media-service tier session packs (2 x 25), with the base license, ME top-up packs (2 x 25), 1 registration pack. The customer needs 30 sessions with transcoding, 40 with media encryption, 0 recorded sessions and 100 registrations on an instance with 2,048 MiB of memory. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • License summary. 50 SIP sessions licensed, 50 with transcoding, 50 with media encryption, 0 recorded sessions, 100 registrations licensed.
    • 
    

    
3. Recording and AMR-WB: -SP sessions with a recording need and an AMR-WB need, and neither license on the quote

    
The agent's request. Please quote SBC SWe Lite for a on-premises deployment with on-premises licenses, -SP media-service tier session packs (1 x 25), with the base license, 1 registration pack. The customer needs 20 sessions with transcoding, 20 with media encryption, 20 recorded sessions and 100 registrations on an instance with 2,048 MiB of memory. The customer needs the AMR-WB codec. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Recording needed beyond the licensed sessions. The customer needs 20 recorded sessions, but the quote licenses recording for 0.
    • 
      
  • AMR-WB needed without its license. The customer needs the AMR-WB codec, but the quote has no AMR-WB license; Ribbon sells it as a separate per-instance license.
    • 
    

    
4. Recording and AMR-WB: The agent resubmits after fixing the errors

    
The agent's request. Please quote SBC SWe Lite for a on-premises deployment with on-premises licenses, -SP media-service tier session packs (1 x 25), with the base license, 1 registration pack. The customer needs 20 sessions with transcoding, 20 with media encryption, 20 recorded sessions and 100 registrations on an instance with 2,048 MiB of memory. The customer needs the AMR-WB codec and the quote includes its license. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Recording needed beyond the licensed sessions. The customer needs 20 recorded sessions, but the quote licenses recording for 0.
    • 
    

    
5. Recording and AMR-WB: The agent resubmits after fixing the errors

    
The agent's request. Please quote SBC SWe Lite for a on-premises deployment with on-premises licenses, -SP media-service tier session packs (1 x 25), with the base license, recording packs (1 x 25), 1 registration pack. The customer needs 20 sessions with transcoding, 20 with media encryption, 20 recorded sessions and 100 registrations on an instance with 2,048 MiB of memory. The customer needs the AMR-WB codec and the quote includes its license. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • License summary. 25 SIP sessions licensed, 25 with transcoding, 25 with media encryption, 25 recorded sessions, 100 registrations licensed.
    • 
    

    
6. Teams Direct Routing: Cloud -SG licenses for Microsoft Teams Direct Routing with 1,500 registrations on 1,024 MiB of memory

    
The agent's request. Please quote SBC SWe Lite for a public cloud deployment with public cloud licenses, -SG media-service tier session packs (2 x 25), with the base license, 15 registration packs. The customer needs 0 sessions with transcoding, 0 with media encryption, 0 recorded sessions and 1,500 registrations on an instance with 1,024 MiB of memory, for Microsoft Teams Direct Routing. It is ready to send.

    
Verdict: Blocked.

    
    
      
  • Teams Direct Routing on a cloud -SG license. The quote uses cloud -SG session licenses for Microsoft Teams Direct Routing; Ribbon warns not to apply -SG-Cloud licenses for Teams Direct Routing because functionality is limited.
    • 
      
  • Registrations above the RAM-based limit. The customer needs 1,500 SIP registrations; Ribbon lists up to 1,000 registrations for the memory size on the quote, so a person should confirm the sizing.
    • 
    

    
7. Teams Direct Routing: The agent resubmits after fixing the errors

    
The agent's request. Please quote SBC SWe Lite for a public cloud deployment with public cloud licenses, -SGX media-service tier session packs (2 x 25), with the base license, 15 registration packs. The customer needs 0 sessions with transcoding, 0 with media encryption, 0 recorded sessions and 1,500 registrations on an instance with 2,048 MiB of memory, for Microsoft Teams Direct Routing. It is ready to send.

    
Verdict: Allowed.

    
    
      
  • License summary. 50 SIP sessions licensed, 0 with transcoding, 50 with media encryption, 0 recorded sessions, 1,500 registrations licensed.
    • 
    

  

  

    
Narration transcript
Click to expand
    
The text of the narrated walkthrough, step by step.

    
    
      
  1. Welcome to a demo of Predictika's Validator. An AI sales agent prepares a license quote for a software session border controller: the deployment type, the media-service tier, the session packs, and more. Before it goes out, the agent sends it to Predictika, which checks it against a declarative model of the published licensing rules and returns a verdict, every reason and the figures it computed.
    2. 
      
  2. I will start with the first request by the agent.
    3. 
      
  3. The agent says. Please quote SBC SWe Lite for a on-premises deployment with on-premises licenses, -SP media-service tier session packs (1 x 25), with the base license, 1 registration pack. The customer needs 20 sessions with transcoding, 20 with media encryption, 20 recorded sessions and 100 registrations on an instance with 2,048 MiB of memory. The rest of the request is on screen.
    4. 
      
  4. Before it goes out, the agent calls the validator.
    5. 
      
  5. Blocked, with two findings, all in one answer. The customer needs 20 recorded sessions, but the quote licenses recording for 0. The customer needs the AMR-WB codec, but the quote has no AMR-WB license; Ribbon sells it as a separate per-instance license.
    6. 
      
  6. The validator returned two blocking findings in one answer. A check that reads one field at a time would pass most of this; it shows only when the choices in the quote are checked against each other.
    7. 
      
  7. What this shows: for licenses that are different for cloud and on-premises, a rules-based CPQ is error-prone for this.
    8. 
      
  8. Now the agent resubmits.
    9. 
      
  9. The corrected request. It changes the AMR-WB license on the quote to yes.
    10. 
      
  10. It calls the validator again.
    11. 
      
  11. Still blocked, with one finding, all in one answer. The customer needs 20 recorded sessions, but the quote licenses recording for 0.
    12. 
      
  12. One finding cleared. Still blocking: recording needed beyond the licensed sessions.
    13. 
      
  13. The agent resubmits once more.
    14. 
      
  14. The revised request. It changes the recording packs to 0 / 0 / 1 / 0.
    15. 
      
  15. It calls the validator once more.
    16. 
      
  16. This time the validator clears it.
    17. 
      
  17. The earlier finding is cleared.
    18. 
      
  18. Two problems caught in one call, fixed in two passes, and a clean quote. That is the value of Predictika's validator: catching mistakes before they reach the customer. Now you can try the other scenarios yourself.
    19.