USSD commands with Vodafone Mobile Connect Lite

[the1ne]

Hi Guys

I'm trying to write a little C# application that send USSD commands to Vodacom via Vodafone Mobile Connect Lite usb modem.

Whilst "AT+COPS?" works fine, "AT+CUSD=1,*111#, 15" command sometimes works and sometimes it doesn't. When it does work, it tried to send "AT+CUSD=1,1, 15" (to choose an option) which has not worked yet.

The kind of errors I get are:
No response from modem
Phone is Busy

Does anyone know Why I'm getting there and where I'm going wrong?

Your help will be highly appreated.
Thank you

[ginggs]

Whilst "AT+COPS?" works fine, "AT+CUSD=1,*111#, 15" command sometimes works and sometimes it doesn't. When it does work, it tried to send "AT+CUSD=1,1, 15" (to choose an option) which has not worked yet.
Try putting the string in double quotes as follows:

AT+CUSD=1,"1",15
And no space before the 15.

[the1ne]

Try putting the string in double quotes as follows:

And no space before the 15.

Did that, gave me the same problem.

Is there any thing I should put between the first command and the second command? Because it keep on giving that "Phone is busy" error

[ginggs]

Did that, gave me the same problem.
Modem make and model?

Is there any thing I should put between the first command and the second command? Because it keep on giving that "Phone is busy" error
I haven't needed to, I just send the USSD command, wait until the menu is received and then send the menu option.

[the1ne]

Okay thanks, I suspect it could be a modem that I'm using because I do it exactly the same way you did it. I need to do a lot of digging around as I'm tasked to find out how to setup a USSD server and write the server side of it so that it can handle client requests.

Thanks for you help so far. If you have any valuable links and info for me and USSD, please swing it along

[ginggs]

Modem make and model?
?

[the1ne]

Oh, sorry

I am using Vodafone Mobile Connect Lite USB Modem, Model: K3765-Z

[ginggs]

I am using Vodafone Mobile Connect Lite USB Modem, Model: K3765-Z
That's the one made by ZTE, any chance you could find one made by Huawei?

[the1ne]

No, I dont think we have it here at work. The one I was using belongs to one of the managers. Is there a difference between the two model?

[cbrunsdonza]

Okay thanks, I suspect it could be a modem that I'm using because I do it exactly the same way you did it. I need to do a lot of digging around as I'm tasked to find out how to setup a USSD server and write the server side of it so that it can handle client requests.

Thanks for you help so far. If you have any valuable links and info for me and USSD, please swing it along

Have fun! Reason why I'm not involved in the USSD side of our company :D . Unless you work for a WASP I'm going to be brutally honest and tell you to consider working though a WASP instead.

You still have to resolve the issues of timeouts, keeping transaction states, the dreaded 20 second session limits, etc ... oh an not to forget the activation issues with each network, as mentioned have fun :D

[cbrunsdonza]

That's the one made by ZTE, any chance you could find one made by Huawei?

VC seems to only have the ZTE ones in stock. When I did an upgrade last month, my SP could not get any Huawei. Another thing is that ZTE seems to be the next preferred vendor (personally I prefer Huawei).

[the1ne]

Have fun! Reason why I'm not involved in the USSD side of our company :D . Unless you work for a WASP I'm going to be brutally honest and tell you to consider working though a WASP instead.

You still have to resolve the issues of timeouts, keeping transaction states, the dreaded 20 second session limits, etc ... oh an not to forget the activation issues with each network, as mentioned have fun :D

You scaring me now LOL. I think the reason we going with USSD is that we want to cater for all mobile phones, not only WAP enabled.

[the1ne]

Have fun! Reason why I'm not involved in the USSD side of our company :D . Unless you work for a WASP I'm going to be brutally honest and tell you to consider working though a WASP instead.

You still have to resolve the issues of timeouts, keeping transaction states, the dreaded 20 second session limits, etc ... oh an not to forget the activation issues with each network, as mentioned have fun :D

And this is a new project in our company and there could be many more to come. So it makes sense that we should it ourselves

[cbrunsdonza]

If your company does not have a WASP licence then your not going to get a USSD bind from the networks. You will have to operate through a WASP then. The WASP will act as a gateway and you connect to their USSD platform.

Asking for assistance here is great, but the connecting WASP will be the one you need to communicate with.

But if you guys do have a WASP licence and are developing your own infrastructure, then you should consider a more reliable language. Developing a client app in C# is one thing, but to do a server app that needs scalability, reliability is another thing.


Also you need to be registered with WASPA as at least an affiliate to get a USSD service from a WASP anyway. You need to familarise yourself with WASPA guidelines concerning USSD, failure to do so can lead to hefty fines and termination of your binds.


(Note: My presence on the hub is purely personal and in no way am I here to canvas business for my employer. My comments are from personal experience and are unbiased)

[the1ne]

If your company does not have a WASP licence then your not going to get a USSD bind from the networks. You will have to operate through a WASP then. The WASP will act as a gateway and you connect to their USSD platform.

Asking for assistance here is great, but the connecting WASP will be the one you need to communicate with.

But if you guys do have a WASP licence and are developing your own infrastructure, then you should consider a more reliable language. Developing a client app in C# is one thing, but to do a server app that needs scalability, reliability is another thing.


Also you need to be registered with WASPA as at least an affiliate to get a USSD service from a WASP anyway. You need to familarise yourself with WASPA guidelines concerning USSD, failure to do so can lead to hefty fines and termination of your binds.


(Note: My presence on the hub is purely personal and in no way am I here to canvas business for my employer. My comments are from personal experience and are unbiased)

Okay, it seems like you have an idea of what I want to achieve. I will ask you a couple of questions:
Is your company a WASP?
When you say a WASP will be the gateway, do you mean they will host our USSD service?
What language do you consider reliable when developing the server side of it?

Thank you for your input

[cbrunsdonza]

I work for a WASP and we handle USSD (you can get a list of WASPs from WASPA).

It really is up to the client to decide what content is hosted by the WASP. If its static content, then usually the WASP does everything, if its dynamic content then usually there is interaction with the clients servers.

On languages, the mobile industry has chosen erlang - for prototyping and small services C# will still scale, its when you need a full production server that has failover and can handle the required hits.