Re: [Oserl-questions] OSERL - SUBMIT_MULTI_RESP - unsuccess_sme(s)

[Sanjaya V. <sa...@wa...>]

Hi Quique,

It works, thanks a lot for the help.

Sanjaya Vitharana

----- Original Message -----
From: "Enrique Marcote Peña" <mpq...@gm...>
To: "Sanjaya Vitharana" <sa...@wa...>
Cc: <ose...@li...>
Sent: Wednesday, 01 August 2007 05:21 pm
Subject: Re: [Oserl-questions] OSERL - SUBMIT_MULTI_RESP - unsuccess_sme(s)


Hi Sanjaya,

unsuccess_sme is supported, find below a simple example.  If any
doubt, please
let me know.  In future posts, your sample code will be greatly helpful.

One important issue to be aware of regarding submit_multi_resp, is
that no_unsuccess
is automatically calculated and inserted from the list of
unsuccess_sme(s),
thus should not be added in params (find further comments on this in
the hrl
files)

sample() ->
     SME1 = #unsuccess_sme{dest_addr_ton = ?TON_INTERNATIONAL,
                           dest_addr_npi = ?NPI_ISDN,
                           destination_addr = "654321",
                           error_status_code = ?ESME_RINVEXPIRY},

     SME2 = #unsuccess_sme{dest_addr_ton = ?TON_INTERNATIONAL,
                           dest_addr_npi = ?NPI_ISDN,
                           destination_addr = "123456",
                           error_status_code = ?ESME_RINVEXPIRY},
     Params = [{message_id, "ABC"},
               {unsuccess_sme, [SME1, SME2]}],
     Pdu = operation:new(?COMMAND_ID_SUBMIT_MULTI_RESP, 1, Params),
     {ok, [Head,Body]} = operation:pack(Pdu),
     binary:to_hexlist(Head) ++ binary:to_hexlist(Body).

This function will return:

"0000002F800000210000000000000001414243000201013635343332310000000062010
13132333
435360000000062"

Meaning:

0000002F  command_length
80000021 command_id
00000000 command_status
00000001 sequence_number

41424300 message_id is "ABC"

02 no_unsuccess is 2

01 dest_addr_ton
01 dest_addr_npi
36353433323100 destination_addr "654321"
00000062 error_status_code

01 dest_addr_ton
01 dest_addr_npi
31323334353600 destination_addr is "123456"
00000062 error_status_code

Hope this helps,

Quique




--
Enrique Marcote Peña
Nomasystems, S.L.
C/ Juan Flórez 8, 5º
15004, A Coruña
Land line: (+34) 902 056 155
Mobile: (+34) 628 095 484
Web Phone: http://www.nomasystems.com (ext 202)
enr...@no...


El 26/07/2007, a las 5:39, Sanjaya Vitharana escribió:

> Hi,
>
> How to set the unsuccess_sme(s) in SUBMIT_MULTI_RESP.
>
> It works with [{message_id, "0"},{no_unsuccess,0},{unsuccess_sme,[]}]
>
> But my different tries to set the {unsuccess_sme,[]} with the data
> of dest_addr_ton, dest_addr_npi, destination_addr,error_status_code
> fails.
> With below grep over the oserl source, I have a intention that
> #unsuccess_sme not used in anywhare. In this case it's fair to fail
> my tries to set the {unsuccess_sme,[]}  in SUBMIT_MULTI_RESP. Am I
> mistaken, or correct? is this feature currently supported?
>
> Thanks in advance.
>
> Sanjaya Vitharana.
>
>
> NOTE: Search for UNSUCCESS_SME_VALUE returns only the definition.
> Seems it is not used in anywhere else.
>
> [root@vm_linux omni_smpp-4.1]# grep -ir "UNSUCCESS_SME_VALUE" /home/
> sanjaya/erlang/smpp_new/oserl-1.3/
> /home/sanjaya/erlang/smpp_new/oserl-1.3/include/smpp_base.hrl:-
> define(UNSUCCESS_SME_VALUE(DestAddrTon, DestAddrNpi, DestAddr,
> StatusCode),
> [root@vm_linux omni_smpp-4.1]#
> ----------------------------------------------------------------------
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a
> browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Oserl-questions mailing list
> Ose...@li...
> https://lists.sourceforge.net/lists/listinfo/oserl-questions