Hi Mat, Hi Thomas,
thanks to both of you I figured out that I had to use the shortcode as username. I hadn't done this before because I got no connection to the SMSC with an empty username, that's what gave me the headache. Right now everything's fully functional so I can start hardening our system to security needs.
Thx again, Christian.
Matthieu Parisot wrote:
Hello,
the UCP60 operation is basically the login of the UCP connection. I
haven't digged in the kannel sources, but i think that not specifying
the username can be the cause of your problem. With our provider, the
username corresponds to the shortcode/shortID/phonenumber (depending on
your terminology). You must also have some good debug in the logfile if you set loglevel to
0 in your config file. What i generally do for connection new shortcodes
is to launch directly bearerbox and smsbox from the command line (no
run_kannelbox wrapper), which will give you the logging directly on the
standard output.
Voila, i hope it will help you!
Mat
On Mon, 2004-12-06 at 17:12 +0100, Christian Vandrei wrote:
Hello list,
I started to use Kannel about two month and have since been able to set up SMSC connections to two different service providers using SMPP3.3/3.4 quite successfully. So I have to give my thanks to the developers of Kannel and its mailinglists. You've done a good job here.
Unfortunately I need to a third SMSC conncetion using EMI/UCP4.2 and that's what gives me some headache. I've already managed to establish the connection to the SMSC, but sending a text SMS isn't working yet. In cooperation with the service providers developer support I was able to find out that sending a text SMS (aka OT51 message) is correct but the issue is that no opening of a session (required to send successfuly) happens yet.
The developer support told me that I need to send an OT60 message to open a session before the OT51 message. My problem now is that I haven't been able to figure out how to represent this behaviour in a Kannel config.
The actual config for the SMSC connection is as follows (using Kannel 1.4.0 stable):
# SMSC CONNECTION group = smsc smsc-id = SMSCx smsc = emi host = 1.2.3.4 port = 1111 # receiving msg's will be cared for later #receive-port = # connection to smsc is accepted without username, so this one's left blank #smsc-username = "" smsc-password = "asdf"
The Userguide states that EMI/UCP 3.5 and 4.0 are supported. Is this information still accurate or is version 4.2 insofar downward compatible that it should work with the actual Kannel?
Many thx in advance and have good day, Christian.
-- Christian Vandrei [EMAIL PROTECTED] www.mobi-tech.com Mobi-tech GmbH Glogauer Str. 6 10999 Berlin Kreuzberg Germany phone 030 616 757 30 fax 030 616 757 34
