Delivery Receipt Concept

[gaurav]

Hello, I am new to SMPP and developing a gateway which interworks with
SIP and SMPP messages.
One side of gateway is connected to SMSC (with SMPP interface) and
other side with SIP interface. The gateway needs to bind in
transceiver mode with SMSC. I am using jSMPP stack to communicate with
SMSC.
When my gateway submits a registered message (using submit_sm), SMSC
generates and send a delivery receipt (using deliver_sm). Now consider
the other case:
When SMSC wish to send an SMS to my gateway, it will use
deliver_sm operation. Assuming it is also a registered message (hence
gateway has to send delivery receipt to SMSC).

Am i right with above statements, or the SMSC will itself generate and
send delivery receipt (to the SMS originator)?

Also if I want to control deliver_sm_resp to SMSC, how can i do this?

In class org.jsmpp.session.state.SMPPSessionBoundRX, the method
processDeliverSm0() is called when deliver_sm comes from SMSC. And
here , the stack itself sends deliver_sm_resp using ResponseHandler.

Please support.

Regards
Gaurav

[gaurav]

Hello folks, please discuss my issue by taking some time in your busy
schedule.
It's really critical from my development perspective .

Regards
Gaurav

[alok vaidya]

Hi Gaurav,
The SMPP flow is in this fashion:
1. ESME (in this case your gateway is an ESME to the SMSC) sends a 
message using submit_sm
2. SMSC sends a submit_sm_resp as an acknowledgement of the receipt of 
the message, in it detailing error if any, through error code, if there 
is no error within the submit_sm_resp there is also a id that the SMSC 
sends back which identifies the sms message uniquely at the SMSC
3. The SMSC sends a deliver_sm (if you have a receiver session bound) 
that details the timestamps for actions taken on the sms by the SMSC, 
delivery status, id (sent back in submit_sm_resp) for you to know to 
associate the delivery report with a specific message among other details.
4. The ESME sends back a deliver_sm_resp to the SMSC acknowledging the 
successful receipt of the delivery report.

These steps, the PDUs in detail and all other things are mentioned in 
the smpp specification document, you can get it from logica's site. Just 
google.

Thanks & Regards,
Alok Vaidya

Gaurav

--
You received this message because you are subscribed to the Google Groups "jsmpp" group.
To post to this group, send email to js...@googlegroups.com.
To unsubscribe from this group, send email to jsmpp+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jsmpp?hl=en.

[Stefán Þorvarðarson]

Hi

When the SMSC sends a message to your application and the sender of that message has requested a delivery receipt, then the SMSC is normally responsible for generating that delivery receipt when your application acknowledges the deliver_sm operation. You do not need to think about generating your own delivery receipt unless your application has specfically been configured that way in the SMSC. Such configuration is only used when the SMPP large account is an inter-SMSC connection where the receipt of the deliver_sm operation does not indicate that the message has reached the final destination.

To control the deliver_sm_resp message you need to use the setMessageReceiverListener() method on the SMPPSession object. Then your implemented method onAcceptDeliverSm() will be called and you can either accept the message or return an error back via the ProcessRequestException.

Best regards,
Stefan

________________________________________
From: js...@googlegroups.com [js...@googlegroups.com] On Behalf Of alok vaidya [get...@gmail.com]
Sent: Friday, January 13, 2012 6:23 AM
To: js...@googlegroups.com
Subject: Re: Delivery Receipt Concept

Hi Gaurav,
The SMPP flow is in this fashion:
1. ESME (in this case your gateway is an ESME to the SMSC) sends a
message using submit_sm
2. SMSC sends a submit_sm_resp as an acknowledgement of the receipt of
the message, in it detailing error if any, through error code, if there
is no error within the submit_sm_resp there is also a id that the SMSC
sends back which identifies the sms message uniquely at the SMSC
3. The SMSC sends a deliver_sm (if you have a receiver session bound)
that details the timestamps for actions taken on the sms by the SMSC,
delivery status, id (sent back in submit_sm_resp) for you to know to
associate the delivery report with a specific message among other details.
4. The ESME sends back a deliver_sm_resp to the SMSC acknowledging the
successful receipt of the delivery report.

These steps, the PDUs in detail and all other things are mentioned in
the smpp specification document, you can get it from logica's site. Just
google.

Thanks & Regards,
Alok Vaidya

On Tue, Jan 3, 2012 at 12:39 PM, gaurav <gaura...@gmail.com<mailto:gaura...@gmail.com>> wrote:
Hello, I am new to SMPP and developing a gateway which interworks with
SIP and SMPP messages.
One side of gateway is connected to SMSC (with SMPP interface) and
other side with SIP interface. The gateway needs to bind in
transceiver mode with SMSC. I am using jSMPP stack to communicate with
SMSC.
When my gateway submits a registered message (using submit_sm), SMSC
generates and send a delivery receipt (using deliver_sm). Now consider
the other case:
When SMSC wish to send an SMS to my gateway, it will use
deliver_sm operation. Assuming it is also a registered message (hence
gateway has to send delivery receipt to SMSC).

Am i right with above statements, or the SMSC will itself generate and
send delivery receipt (to the SMS originator)?

Also if I want to control deliver_sm_resp to SMSC, how can i do this?

In class org.jsmpp.session.state.SMPPSessionBoundRX, the method
processDeliverSm0() is called when deliver_sm comes from SMSC. And
here , the stack itself sends deliver_sm_resp using ResponseHandler.

Please support.

Regards
Gaurav

--
You received this message because you are subscribed to the Google Groups "jsmpp" group.

To post to this group, send email to js...@googlegroups.com<mailto:js...@googlegroups.com>.
To unsubscribe from this group, send email to jsmpp+un...@googlegroups.com<mailto:jsmpp%2Bunsu...@googlegroups.com>.

[gaurav]

Many many thanx to Alok and Stefán. I will try these scenario and get
back to you.


Regards
Gaurav

On Jan 13, 2:54 pm, Stefán Þorvarðarson <stefa...@siminn.is> wrote:
> Hi
>
> When the SMSC sends a message to your application and the sender of that message has requested a delivery receipt, then the SMSC is normally responsible for generating that delivery receipt when your application acknowledges the deliver_sm operation. You do not need to think about generating your own delivery receipt unless your application has specfically been configured that way in the SMSC. Such configuration is only used when the SMPP large account is an inter-SMSC connection where the receipt of the deliver_sm operation does not indicate that the message has reached the final destination.
>
> To control the deliver_sm_resp message you need to use the setMessageReceiverListener() method on the SMPPSession object. Then your implemented method onAcceptDeliverSm() will be called and you can either accept the message or return an error back via the ProcessRequestException.
>
> Best regards,
> Stefan
>
> ________________________________________

> From: js...@googlegroups.com [js...@googlegroups.com] On Behalf Of alok vaidya [geta...@gmail.com]

> Sent: Friday, January 13, 2012 6:23 AM
> To: js...@googlegroups.com
> Subject: Re: Delivery Receipt Concept
>
> Hi Gaurav,
> The SMPP flow is in this fashion:
> 1. ESME (in this case your gateway is an ESME to the SMSC) sends a
> message using submit_sm
> 2. SMSC sends a submit_sm_resp as an acknowledgement of the receipt of
> the message, in it detailing error if any, through error code, if there
> is no error within the submit_sm_resp there is also a id that the SMSC
> sends back which identifies the sms message uniquely at the SMSC
> 3. The SMSC sends a deliver_sm (if you have a receiver session bound)
> that details the timestamps for actions taken on the sms by the SMSC,
> delivery status, id (sent back in submit_sm_resp) for you to know to
> associate the delivery report with a specific message among other details.
> 4. The ESME sends back a deliver_sm_resp to the SMSC acknowledging the
> successful receipt of the delivery report.
>
> These steps, the PDUs in detail and all other things are mentioned in
> the smpp specification document, you can get it from logica's site. Just
> google.
>
> Thanks & Regards,
> Alok Vaidya
>

> To unsubscribe from this group, send email to jsmpp+un...@googlegroups.com<mailto:jsmpp%2Bunsubscribe@googlegroups. com>.
> For more options, visit this group athttp://groups.google.com/group/jsmpp?hl=en.

[Gaurav Singh]

Yes I have done most of the task
probably it is going to deploy soon. Any help is welcome.

On 6 Jun 2013 17:16, "Hamid R. Hashmi" <hamid.h...@gmail.com> wrote:

Gaurav have you implemented this way ??? is it working fine ??/

--

You received this message because you are subscribed to the Google Groups "jsmpp" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jsmpp+un...@googlegroups.com.

To post to this group, send email to js...@googlegroups.com.

Visit this group at http://groups.google.com/group/jsmpp?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Hamid R. Hashmi]

Thanks for your quick reply.  OK, I will try it and ask for help again if I need it. 

Regards

Hamid R. Hashmi

On Tuesday, January 3, 2012 12:09:52 PM UTC+5, gaurav wrote: