----- Oorspronkelijk bericht ----- Van: Rene Kluwen <[email protected]> Verzonden: donderdag 20 oktober 2011 0:18 Aan: Aarno Syvänen <[email protected]> Onderwerp: RE: Using smppbox id
I case of multiple smppboxes with possibly shared clients the same logic applies. The return message is routed to the client that the original message came from. No matter at which smppbox it is currently connected. ----- Oorspronkelijk bericht ----- Van: Aarno Syvänen <[email protected]> Verzonden: woensdag 19 oktober 2011 15:26 Aan: [email protected] Devel <[email protected]> Onderwerp: Re: Using smppbox id This relies on assumption that no two smppbox share a client. I cannot accept this. Besides, I can have two smppboxes connected to my application Aarno On 19.10.2011, at 15:19, Rene Kluwen wrote: > Like I said before: In clients.txt, you can put system-type to the > opensmppbox-id and you are all set. > > == Rene > > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Aarno Syvänen > Sent: Wednesday, 19 October, 2011 09:35 > To: [email protected] Devel > Subject: Re: Using smppbox id > > > In my case, there is an application between bearerbox and smppbox. > Thus application must route to smppbox and not to its clients. > > Aarno > > > On 18.10.2011, at 23:25, Rene Kluwen wrote: > >> In this case the boxcid represents the particular ESME in subject to route >> the DLR/MO back to. >> Every ESME represents a different box as far as bearerbox is concerned. >> Multiple clients mean multiple bearerbox connections. >> What is (in your opinion) the bug in this logic? >> >> == Rene >> >> -----Original Message----- >> From: Andreas Fink [mailto:[email protected]] >> Sent: Tuesday, 18 October, 2011 17:47 >> To: Rene Kluwen >> Cc: devel Devel >> Subject: Re: Using smppbox id >> >> On 18.10.2011, at 17:44, Rene Kluwen wrote: >> >>> Once you look further in the opensmppbox documentation, you will see that >>> system-type (or system-id if use-systemid-as-smsboxid is set to true) is >>> used as boxcid whilst communicating to bearerbox. > [Het originele bericht is niet volledig opgenomen]
