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. This is to facilitate the proper return path for DLR's (and also: MO's) to the different ESME clients that are connected to opensmppbox.
Secondly: You are right that opensmppbox-id is useless for routing purposes. That's why it is never used. == Rene -----Original Message----- From: Andreas Fink [mailto:[email protected]] Sent: Tuesday, 18 October, 2011 17:39 To: Rene Kluwen Cc: 'Aarno Syvänen'; [email protected] Subject: Re: Using smppbox id The system type has nothing to do with the box-id. The boxid is used to connect to bearerbox and is also used to route delivery reports back. Oone box can only have one ID which is transmitted initially at connection time so having multiple smpp users sending this way different box-id's back would not make any sense at all as it would not get back due to the routing in bearerbox. Secondly at the time OpenSMPPBox connects to bearerbox, the box-id is not yet set. In other words only the default routing is used which makes the use of box-id useless. In our case we might have multiple boxes connected to one bearerbox. Such as a SMSBox and a OpenSMPPBox (or our own box which is in the workings). in this case bearerbox needs to know on which link the connection was coming from to send back the delivery report through the right path. On 18.10.2011, at 17:26, Rene Kluwen wrote: > What you can do instead of changing the code is specify your smppboxid as a > system-type in clients.txt. > > Wouldn't that be the same? > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On Behalf > Of Aarno Syvänen > Sent: Tuesday, 18 October, 2011 15:02 > To: [email protected] Devel > Subject: Using smppbox id > > Hi List, > > simply changing box id in outgoing message to refer smppbox, and not to its > client > > >
