Actually the current implementation should terminate the interactive
session by sending an escape character.
No easy way comes to my mind to actually handle an interactive
session, especially as there can be no generic implementation for this
problem due to these sessions being different from each other.
However I think it could be possible to implement the possiblity of
registering a USSD session handler. This handler you would need to
write by yourself tailored to the specific flow of the USSD session
you are about to create. Then your code would need to pass an instance
of this handler to SMSlib along with the the actual USSD command. Once
the command is executed and the session established, SMSlib would
transfer control to that handler to cope with the session.
I think this might be possible, but not all that easily and it calls
for some work on the library that is for sure.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"SMSLib for Java User Group" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/smslib?hl=en
-~----------~----~----~----~------~----~------~--~---
