Routing of delivery receipts to correct instance of ESME

Routing of delivery receipts to correct instance of ESME SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through August 22, 2012 » Routing of delivery receipts to correct instance of ESME « Previous || Next »
Author Message
Brendan Moynihan
New member
Username: Brendan

Post Number: 1
Registered: 05-2012
Posted on Wednesday, May 02, 2012 - 09:04 am:   

Hello,
This is a general support query in relation to delivery of delivery receipt.

Consider hostA running 2 instances of an ESME that is bound to NowSMS with same system_id and password. Also consider an instance of the same ESME running on hostB.

Assuming all instances of the ESME submit message with receipt requested, after message submission and termination to SMSC and subsequent deliver_sm for receipt is received from SMSC, will NowSMS be able to route the delivery receipt over the corrent connection to the correct instance of the app on either hostA or hostB.
Will NowSMS have correlation data to identify the correct instance to route to on hostA?

What about if the instances unbind and subsequently bind in again, will NowSMS be able to route the receipts correctly?

Appreciate your input.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3942
Registered: 08-2008
Posted on Wednesday, May 02, 2012 - 06:11 pm:   

Hi Brendan,

No. If they are using the same system_id and password, the receipt could be delivered to either system.

I'd be very surprised if this behaviour was specific to NowSMS ... I'd expect this from other systems as well.

There may be some confusion in some discussions about the topic, because acknowledgments are sent back in the same session/bind. That is protocol, those actions are part of the same transaction. A delivery receipt is a new transaction (and it could happen hours or days later).

If receipts need to be sent back to the same instance, different system_id values should be used for each instance.

--
Des
NowSMS Support
Brendan
New member
Username: Brendan

Post Number: 2
Registered: 05-2012
Posted on Wednesday, May 02, 2012 - 08:04 pm:   

Hi Des,
thanks very much for reply.
Would it be useful to track IP of client, so at least the receipt could be delivered to the correct machine. If not, there may be a significantly unbalanced load. (ie, all receipts going to a single system).
Is receipt correlation expected at the application ESME?
For example: message from system A and receipt is sent to system B.
Thanks again.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3950
Registered: 08-2008
Posted on Thursday, May 03, 2012 - 07:37 pm:   

Hi Brendan,

I understand that there are some scenarios where this may be desirable.

However, as I stated, I'd be very surprised if other systems did this. (The exception being simulators.) I know that when running NowSMS with multiple front-ends in a load balanced configuration, we have to be ready to accept delivery receipts regardless of which system it originated with.

In the scenario that you describe, if the client requires that receipts be sent back to the same instance, different system_id values should be used for each instance. Is there a reason you cannot do this?

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics