hi alt,
we have temporarily removed all code related to OpenTelemetry from the Inetlab source code for now.
I would suggest adding a smppclient option for enabling/disabling activity diagnostics. I think this would be more flexible in case users use their own approach to tracing.

Update: Possible root cause for our memory leak case - "Activity Theft" in SmppConnection

After deeper look into dotMemory, seems we found the cause.

Profiler Data:
- Activity objects: 49
- DiagNode: 5,158,820 (thousands events per Activity!)
- SmppConnection: 765
- SmppSession: 765

Retention ...

Hi alt,

We discovered a memory leak in our production environment. Memory grows from ~2GB to 3.6GB over one week and never releases.

Environment:
- Inetlab.SMPP version: 2.9.35
- .NET 8
- Linux

Memory profiler shows DiagNode<ActivityEvent> objects accumulating: see image1.jpeg

Memory growth ...

kind reminder

can esm_class have multiple flags in deliver_sm? we have an example for one SMSC provider we're connected to sending a deliver_sm with 0x24 (36) for esm_class as if both flags SMSCDeliveryReceipt + IntermediateDeliveryNotification assembled

for this reason Receipt is not created in SmppReader.cs ...

"Occurs when Unbind packet received from SMSC" - means that if your partner unbind the session gracefully then evUnBind event raised, and your client got unsubscribed to evDeliverSm

can you elaborate on problem? you have multiple options: increase window size, increase number of smpp clients, push messages in bulk (multi), play around with stream tunning

all above options depend on what specific issue with this specific SMSC, e.g. if submit_sm_resp latency is high then window ...