Re: [Kannel-Users] [RFC] Re: Fwd: [Kannel-Users] Re: SMS message ids

On Fri, 28 Jan 2005, Stipe Tolj wrote:

> Matthew Hixson wrote:
>
>> Any chance we could get the dlr notification to include the message_ids 
>> that can be found in bearerbox.log?
>>   Thanks,
>>    -M@
>
> ok, picking this up here from the architecture design perspective.
>
> Mainly the request is to have a "way" in getting the protocol-specific 
> message-id that is send in a SMS MT ack reply (not a DLR itself) back to the 
> application layer, hence via urltrans mechanism.
>
> I think this is a legitimite request of feature, since many SMSC protocol 
> allow then the application layer to do nesty things like, cancel'ing or 
> modify'ing messages that are in the SMSC queue.
>
> Now, how do we get that transported? bearerbox gets subsmit_sm_resp (in case 
> of SMPP) which contains the SMPP specific msg-id. smsbox gets "only" acks 
> from bearerbox with Kannel msg-ids.
>
> A way may be do add a field to the ack msg structure to carry that field to 
> smsbox and get it to the application layer via Kalle's new sendsms concept on 
> waiting on acks from bearerbox.

  Stipe --

  What I don't understand is why the smsbox would be involved at all.  As I
  understand it (and I could be wrong) is that the smsbox is for accepting
  messages, and the bearerbox actually calls Delivery Reports (DLR-URLs)
  with the various information.  This is my understanding:

     1. Message is submitted via /cgi-bin/sendsms to smsbox
     2. smsbox checks for validity, accepts the message
     3. smsbox communicates this to bearerbox
     4. bearerbox submits the message to the appropriate smsc
     5. bearerbox saves the dlr report (internal, mysql, etc)
     6. bearerbox gets a response (submit_sm_resp) from the smsc
     7. bearerbox generates a DLR report with type=8 and all that other
        stuff, excluding dlr->ts which contains the remote SMSC message-id

  I know that all I'm looking for is an escape code in the DLR report that
  bearerbox generates i.e. %X which would have to be a string, since some
  are decimal, hex or strings, so when my DLR-URL is called, I can update my
  DB with the remote SMSC message id.

  I don't know how smsbox is involved in that -- could you explain?  And if
  I'm reading it right, I think it doesn't make sense for the message-id of
  the remote SMSC to be returned by the smsbox at all.  Nor do I think it
  makes sense to return the kannel sms.id via the smsbox at HTTP GET/POST
  either.  I could just be generally confused... :-)

Beckman
---------------------------------------------------------------------------
Peter Beckman                                                  Internet Guy
[email protected]                             http://www.purplecow.com/
---------------------------------------------------------------------------