search

larvit / larvitsmpp

SMPP made simple
MIT License
7 stars 7 forks source link

Support for bind_transceiver, bind_transmitter and bind_receiver #16

Open Dexus opened 8 years ago

Dexus commented 8 years ago

see topic

lillem4n commented 8 years ago

Just to clarify; right now there is support for bind_transceiver and only bind_transceiver. We need support for bind_transmitter and bind_receiver as well.

Also I do not remember what happends if another client connects with anything else than bind_transceiver, it is very possible those connections are allowed and treated like transceiver connections.

Dexus commented 8 years ago

The Server should for all incoming connections listen to all events, and send back a error on wrong bindings.

And the server should only send dlrs and sms to transceiver or receiver. In the real world, i have one or more multiple services that i use parallel, and i receive only on one Server, but send from a bigger cluster. So i can't handle all incoming dlrs/sms on the same cluster because they only work more or less as a just in time proxy. based on service provider you can use transmitter and receiver or transceiver. Also with multiple connections, but at last you should know if you only have a transceiver, it is possible if you dont listen to incoming dlrs/sms you lost them, so you should for sending only use transmitter.

lillem4n commented 8 years ago

Aye, I recognize the need. Good clarification!

All help in this matter is appreciated. For example, if you could toss together a few tests to demonstrate a few different needs that would be amazing.

I am building this for a customer and will not be able to handle this extra implementation for at least a few weeks yet.