USSD implementation.

M

muhammad_salman

New Member
Joined
Apr 28, 2009
Messages
3
Reaction score
0
I want to implement USSD in .net. I am a beginner and want to know the complete step by step process.

Application which originates a TCP/IP network connection between a service application and the USSDC.
Log in to the USSDC through the UssdBind message.
The flow that a service application initiates a USSD session
The flow that a mobile phone initiates a USSD session
The flow of forwarding services
The flow of charging

Is there anybody who can help me in achieving these tasks?
 
muhammad_salman said:
I want to implement USSD in .net. I am a beginner and want to know the complete step by step process.

Application which originates a TCP/IP network connection between a service application and the USSDC.
Log in to the USSDC through the UssdBind message.
The flow that a service application initiates a USSD session
The flow that a mobile phone initiates a USSD session
The flow of forwarding services
The flow of charging

Is there anybody who can help me in achieving these tasks?
Click to expand...

My dear friend,

I have learned a lot about USSD from ginggs.
Please contact him.
Another source of information is Google search for USSD.

My technology is based on One-Step-Ahead approach.
So first I draw charts, discuss, than write a code.

Linux + shell scripting is an excellent development platform for USSD, MS Vista <> Linux integration, remote Linux servers diagnostics and more.

What you really need is USSD server on your desk.
As sending USSD commands is like sending AT commands, you may try to simulate sending USSD express codes and have USSD Gateway on and running.

Try to set up your own SMS Gateway, than Web server and have all of them interfaced interactively.

As USSD Gateway is telecom operator's side service, try to convince your telecom operator to let you experiment with USSD service.

In my view USSD service can be described as another data pipeline + interfacing. Service is as old as the first GSM phone, never developed into some more sophisticated solution or service.

I have spent a lot of time with USSD trying to learn how to write
basic USSD express code for balance check send/receive application,
and succeeded.

USSD system has still a great future, but is restricted by my Telecom
so I can do nothing.

In some regions USSD service is not for free.

I was approached by developers of USSD Gateways.
Unfortunately, got no response at a later time.
 
Thank you for the reply...
Actually implementing the USSD is a requirement of the service provider company in which I am working. We have no restriction from our telecom operators and we need to develop a solution for one of the telecom in our region. Our company is basically provide sms based solutions. We are already connected to the SMSC of the local telecom operators.
But we dont have as such experience in developing USSD based applications. And we need to perform this task in .Net environment.
So for this reason if you or anyone here can help me out, it would be highly appreciated.
 
muhammad_salman said:
Thank you for the reply...
Actually implementing the USSD is a requirement of the service provider company in which I am working. We have no restriction from our telecom operators and we need to develop a solution for one of the telecom in our region. Our company is basically provide sms based solutions. We are already connected to the SMSC of the local telecom operators.
But we dont have as such experience in developing USSD based applications. And we need to perform this task in .Net environment.
So for this reason if you or anyone here can help me out, it would be highly appreciated.
Click to expand...

u got PM
 
muhammad_salman said:
Thank you for the reply...
Actually implementing the USSD is a requirement of the service provider company in which I am working. We have no restriction from our telecom operators and we need to develop a solution for one of the telecom in our region. Our company is basically provide sms based solutions. We are already connected to the SMSC of the local telecom operators.
But we dont have as such experience in developing USSD based applications. And we need to perform this task in .Net environment.
So for this reason if you or anyone here can help me out, it would be highly appreciated.
Click to expand...

Ok.
I am really interested to work for your company, developing highly-sophisticated USSD services and solutions.

One step is isntallation of USSD Gateway,
second step is development of hot USSD applications, to attract telecom customers.

As you can have full development control of USSD Gateway at your telecom I am really interested to offer you some hot USSD stuff, to make your USSD service the hottest global product in telecommunication world.

I would be very interested to come with new USSD products for some world telecommunication trades and fairs as pretested, implemented and working product.

Please send me contact info, email, as a private message.


Darius
 
Can you guys please mention your regions and Telecoms. Cause if your bragging about Vodacom, Mtn or CellC then this thread is a joke. You can have all the hottest SS7 hardware and lines (ja sure) and it means nothing if your destination network sucks.

USSD has a great future and is a good field to get into. Mobile skills are in dire shortage and any experience you can bring to a WASP is of great value. Personally I hope to get involved with some USSD development with my employer.
 
cbrunsdonza said:
Can you guys please mention your regions and Telecoms. Cause if your bragging about Vodacom, Mtn or CellC then this thread is a joke. You can have all the hottest SS7 hardware and lines (ja sure) and it means nothing if your destination network sucks.

USSD has a great future and is a good field to get into. Mobile skills are in dire shortage and any experience you can bring to a WASP is of great value. Personally I hope to get involved with some USSD development with my employer.
Click to expand...

Congratulations.
My personal view, based on my experience with my broadband telecom operator, is, USSD service is highly unreliable, service temporary unavailable is a common message I get trying to check my prepaid balance.
Any message I get is:
Please try again soon.

I am really surprised, how some telecom operators dare to charge end-users for such unreliable, low-quality, low-speed, limited-use USSD service (express codes).

I see no future for such unreliable service like USSD.

We must develop much more sophisticated service.

Darius
 
The reason why USSD has a (short) future is that the networks have run out of shortcodes. With WASPA requirements relating to unsubscribes, companies are using USSD as their are no more standard rate numbers left.
 
cbrunsdonza said:
The reason why USSD has a (short) future is that the networks have run out of shortcodes. With WASPA requirements relating to unsubscribes, companies are using USSD as their are no more standard rate numbers left.
Click to expand...

Hi,

could you kindly explain the above in details and why do you claim that the networks have been run out of shortcodes (express codes) ?

http://waspa.org.za/
http://www.waspa.org.za/code/download/0014.pdf


My last USSD test:

Service not running!
Please try again later.

We are sorry. Service temporary unavailable.
Please try later.

(I was told service was provided by Huawei - USSD Gateway).

BTW.

No word about USSD in the programme of the Mobile Money Transfer Africa Conference & Expo Conference, May 2009.
 
Last edited:
USSD is a real time application, at least from the handset to the WASP application. Thus maybe for IDOLs they can consider using USSD in future.

Each network operator should have interface specifications to their USSD gateways as this is not standardised in the industry unlike SMS which interacts over SMPP. The logic is still very similar, for instance balance requests only require one request and one reply. For USSD menu's, the menu context is with the WASP and the gateway merely provides the mediation from IP to SS7. Thus USSD sessions running concurrently as well as keeping track of each session is held by GW and also need to be held by the WASP.

Some USSD gateways uses SMPP for USSD transactions but this is more fit if its one request one reply based. For USSD menu's this is not the best solution as there is quite a lot of overhead in a SMPP packet.

USSD can be bi-directional as well, meaning that the WASP can initiate the USSD to the handset and the subscriber will see some text on the handset. This is not commonly used in SA but more used in foreign networks.
 
parmalat said:
USSD is a real time application, at least from the handset to the WASP application. Thus maybe for IDOLs they can consider using USSD in future.

Each network operator should have interface specifications to their USSD gateways as this is not standardised in the industry unlike SMS which interacts over SMPP. The logic is still very similar, for instance balance requests only require one request and one reply. For USSD menu's, the menu context is with the WASP and the gateway merely provides the mediation from IP to SS7. Thus USSD sessions running concurrently as well as keeping track of each session is held by GW and also need to be held by the WASP.

Some USSD gateways uses SMPP for USSD transactions but this is more fit if its one request one reply based. For USSD menu's this is not the best solution as there is quite a lot of overhead in a SMPP packet.

USSD can be bi-directional as well, meaning that the WASP can initiate the USSD to the handset and the subscriber will see some text on the handset. This is not commonly used in SA but more used in foreign networks.
Click to expand...

Thanks for your excellent manual on USSD.
I am looking for direct contact with telecom operators, implementing high-techs in USSD service, or interested to implement in near future.

What I mean are micro payments and money transfer.

One solution is offered by Nokia with NFC phones and other is known as one-time codes sent by SMS.
USSD communication protocol is interesting.
Unfortunately it fails as a reliable communication means with my operator from time to time (network busy, please try later, service temporary unavailable and the like messages).

Developing system for mobile micro-payments I would like to run some tests and USSD Gateway simulator running on my desk.

NFC requires another simulator.

But for system charting I don't need any hardware, just free discussion,
how to make such system safe and reliable.

Master Card is going to sponsor such system solutions.
 
where can i find open saurce USSD api server, google doesnt show.
 
Hi,

basically i have

(1) Interface spesification frm telecoms

I lost to start.anyonw can help?
 
USSD Developer

Hi All

Are there any private contractors that would be interested in a USSD project?

A Client of mine need a USSD menue system created, they have direct connections but need a developers to setup the code

Please feel free to contact me directly
 
darius2 said:
Ok.
I am really interested to work for your company, developing highly-sophisticated USSD services and solutions.

One step is isntallation of USSD Gateway,
second step is development of hot USSD applications, to attract telecom customers.

As you can have full development control of USSD Gateway at your telecom I am really interested to offer you some hot USSD stuff, to make your USSD service the hottest global product in telecommunication world.

I would be very interested to come with new USSD products for some world telecommunication trades and fairs as pretested, implemented and working product.

Please send me contact info, email, as a private message.


Darius
Click to expand...

Please Would you guide me through in developing an uss mobile payment application for a bank?
 
Please Would you guide me through in developing an uss mobile payment application for a bank?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X