Developing a USSD application in Push Mode(only Notificatiion) usin...

Developing a USSD application in Push Mode(only Notificatiion) usin... SearchSearch
Author Message
Akash Saxena
New member
Username: Akash_saxena

Post Number: 1
Registered: 05-2011
Posted on Thursday, May 05, 2011 - 11:50 am:   

Hi,
I have been working on an application where i need to send USSD to USSD Gateway using SMPP on Unix.
I am using SMPPCXX library to send request to SMPP but i don't have any SMPP simulator which
can help me in validating the request sent.

My application acts like an independent network identity, so this USSD request will be network initiated and not mobile initiated. Where i need to send notification only from my application using USSD and the application does not maintain
any sessions corresponding to USSD sent. So it is
Network Initiated single push–no response(USSN).

Also i am using ussd_service_op TLV (tag length value ) parameter to send USSD notification which is supported in SMPP v3.4 and v5.0.
In ussd_service_op TLV tag= 0x0501, length = 1, and value= 3 (USSN request)

I want to use smsnow to act as a SMPP server and replies back the same tlv with tag = 0x0501, length =1 and value=19(USSN confirm).

My application requires only to send USSD and it should reach to subscriber via USSD gateway.


I have downloaded the smsnow application , could you let me know whether smsnow would be useful in my aforesaid activity.

If yes how would I configure it and use it accordingly.

Thanks & Regards
Akash Saxena
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3153
Registered: 08-2008
Posted on Friday, May 06, 2011 - 10:04 pm:   

Hi Akash,

I'm sorry, but I can't think of any easy way to facilitate this.

You could easily do a loopback to yourself without having the ussd_service_op tag modified, but there's no good way of changing that value.

If you want to try that, here's what I'd suggest.

NowSMS is going to complain if you don't have an upstream SMSC route. Just define a bogus HTTP SMSC connection. Point it to a web server, tell it that the web server is using the NowSMS format.

Go ahead and check "Support any outbound message traffic".

If any messages accidentally end up getting routed in this direction, NowSMS will just be sending HTTP requests to this web server. No big deal.

Define an account under "SMS Users". This is the credentials that your client will use to connect.

Check the option to route received SMS messages to your account, and put * in the "Recipient Addresses to route to this user" field. This means that if NowSMS has any messages to route, it is going to try to deliver them to this account. When you submit messages, it will essentially create a loopback.

I believe the ussd_service_op parameter is supported by default.

If for some reason you are not receiving it in replies, edit SMSGW.INI and add the following section:

[SMPPOptions]
ussd_service_op=501,Integer,1

Not exactly what you want, but perhaps useful.

--
Des
NowSMS Support