Expertise · Network evidence
VoIP, SMS and Network Interconnection Expert
Interconnection disputes often turn on details that are invisible in commercial correspondence: signaling sequences, addressing, routing choices, handoff points, protocol behavior and the distinction between transport, termination and an application-layer service.
Questions the evidence can answer
- Where did a call or message enter and leave each network?
- Did a failure originate in routing, signaling, provisioning, capacity or policy?
- Was the disputed service termination, transit, access or a separate follow-on service?
- Do observed traffic records support the asserted volumes and charges?
Relevant technical records
- SIP ladders and session logs
- SMPP submits, delivery receipts and error codes
- SS7/SCCP and routing evidence
- Numbering plans, portability data and ENUM responses
- Switch, SBC, SMSC and billing configurations
Clear explanation for the record
The objective is not to overwhelm the matter with protocol terminology. It is to identify the decisive event, explain which party controlled it, test alternative explanations and present a reproducible technical narrative.
Public sources
ACM KPN/RGTN SMS matter↗PortaOne P2A case study↗COIN real-time ENUM implementation↗For counsel
Discuss the technical record.
Engagements are subject to conflicts and scope review. Initial enquiries are treated as confidential.
Contact Leo Herps ↗