Mobees protocol integration modules

The protocol team you cannot hire Engineering Services

Twenty-five telco-grade systems delivered. Most of them were not products — they were somebody’s blocked programme, a legacy migration nobody wanted, or an integration that three other parties had declared impossible. This is the capability underneath everything else we sell.

  • Protocol integration: SS7/SIGTRAN, MAP, INAP, CAMEL, Diameter, SIP, SMPP, MM1–MM9, 5G HTTP/2
  • Legacy migration and IN modernisation without a big-bang cutover
  • Deal rescue: the escalation team for a transformation that has hit the network layer
  • Custom network functions built on our existing, proven protocol modules
  • Delivered as a subcontract behind your brand, or direct to the operator

SS7 / SIGTRAN

MAP · INAP · CAMEL

Diameter

SIP / IMS

SMPP

MM1–MM9

5G SBI / HTTP-2

GTP

Kubernetes

Legacy migration

Subcontract delivery

Source-code escrow

What people actually call us about

The programme hit the protocol layer. A transformation is on schedule until it reaches CAMEL, an IN platform nobody documented, or a roaming interface that behaves differently from the specification. There are very few people left who can read that quickly.

The vendor said no. A required behaviour is not on the roadmap, or is quoted at a price and a date that make the business case collapse. We build the missing piece beside the platform rather than inside it.

The exit is blocked. You want out of a vendor relationship and discover the lock-in is not commercial, it is protocol-level. Untangling that is most of what we have done for eight years.

It has to work in six weeks. Regulatory deadline, launch date, a partner who will not wait. Fifteen people with no internal approval chain is a genuine structural advantage here.

Engagement types

Protocol integration

  • Connect systems that were never designed to talk to each other
  • Reuse of twenty-plus already-proven protocol modules
  • Conformance and interoperability testing included, not extra
  • Typical duration: four to twelve weeks

Legacy migration

  • IN, messaging and VAS platforms moved off end-of-life hardware
  • Shadow, canary and ramp — never a big-bang weekend
  • Behaviour compared on the wire, not against documentation
  • Rollback available until you decide you no longer want it

Custom network functions

  • Built on the same modules as our products, so not from zero
  • Cloud-native and containerised by default
  • You get the documentation, the tests and an escrow option
  • Typical duration: one to two quarters to production

Deal rescue and L3

  • Dropped into a programme that is already late, with no ramp-up theatre
  • Trace analysis and root cause across multi-vendor boundaries
  • Works behind your brand if that is what the account needs
  • Available as an ongoing retainer

How we work

  • Paid discovery, always. A short, fixed-price scoping engagement that produces a written architecture and a firm price. Free discovery produces optimistic estimates and we have stopped pretending otherwise.
  • Fixed price where the scope is knowable. Time and materials only for genuinely exploratory work, and we will tell you which one you are buying.
  • Your architects in the room. We do not disappear for a quarter and return with a deliverable. Weekly demo, working software.
  • Documented and escrowed. Every engagement ends with architecture documentation, runbooks and test suites. Source-code escrow is offered as standard.
  • Behind your brand if needed. A large share of this work is delivered as a subcontract to integrators and platform vendors. We are comfortable being invisible.
Engineering delivery model

What our customers say

References are anonymised at the customer’s request. Named references and written reference letters are available under NDA.

Core network operations, Tier-1 MNO (DT group)

„We were finding signalling degradations from the complaint queue. ProBee moved that left by roughly forty minutes — we now see the retransmission pattern build before the first customer calls. It is the same Grafana our NOC already lives in, so nobody had to learn a new console.”

Head of Platforms, MVNE serving 300k+ subscribers

„Our BSS was complete and our network layer was not. Mobees dropped in the messaging core and the TS.43 entitlement server behind our existing provisioning, per tenant. We stopped referring those deals out.”

Delivery director, systems integrator, CEE

„They are the people we call when a transformation programme hits SS7 or CAMEL and the schedule is already tight. Small team, no layers, an answer the same week.”

Describe the problem in one paragraph.

You will get an engineer’s opinion back, not a capability deck. If it is outside what we do well, we will say that too.