try to hold the phone to a loudspeaker in order to have an
electro-magnetic indication that the SMS is in fact arriving the device.
Stipe
Hi Stipe,
I did also that :-D I'm pleased such "uncommons" techniques are used by
you too :-D
However I got it solved: my application was waiting for
Loïc Minier wrote:
On Thu, Jun 08, 2006, Julien Buratto wrote:
Are you adding some other parameters to the http call ?
Usual parameters, sender, recipient, nothing special apart from text
and udh.
Any particular conf in the kannel.conf file ?
No.
It's strange, I can send any typ
Setting the UDH will change some bits on the ESM_CLASS to non-zero and
that's probably changing the message to binary.
Hope it helps,
On 6/9/06, Julien Buratto <[EMAIL PROTECTED]> wrote:
Loïc Minier ha scritto:
> On Thu, Jun 08, 2006, Julien Buratto wrote:
>>> You need a source port, and I don
Loïc Minier ha scritto:
> On Thu, Jun 08, 2006, Julien Buratto wrote:
>>> You need a source port, and I don't think you need to add %00 at the
>>> end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the
>>> destination port (2948) and 23F0 the source port (9200).
>> I've tested that
Loïc Minier ha scritto:
> On Thu, Jun 08, 2006, Julien Buratto wrote:
>> Are you adding some other parameters to the http call ?
>
> Usual parameters, sender, recipient, nothing special apart from text
> and udh.
>
>> Any particular conf in the kannel.conf file ?
>
> No.
>
>> It's strange, I
Uhmm I don't think so, I can ear my phone making "sound" in my computer
speakers (I know it's a strange test method) and also I do receive a
positive delivery report message back.
I think something is getting "touched" in the transmission and the port
is changed...
Will debug more :-D
J
Loïc Mi
On Thu, Jun 08, 2006, Julien Buratto wrote:
> Are you adding some other parameters to the http call ?
Usual parameters, sender, recipient, nothing special apart from text
and udh.
> Any particular conf in the kannel.conf file ?
No.
> It's strange, I can send any type of message (sync, wap) b
Loïc Minier ha scritto:
> On Thu, Jun 08, 2006, Julien Buratto wrote:
>>> You need a source port, and I don't think you need to add %00 at the
>>> end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the
>>> destination port (2948) and 23F0 the source port (9200).
>> I've tested that
Funny, my UDH without the last %00 works, if I use the %00 it give
malformed.
With your UDH give no errors.
However my application does not intercept the message even if listening
to port 16664...
Should I add something else as a parameter like coding or wmi or similar ?
Thanks
J
Oscar Elfving
On Thu, Jun 08, 2006, Julien Buratto wrote:
> > You need a source port, and I don't think you need to add %00 at the
> > end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the
> > destination port (2948) and 23F0 the source port (9200).
> I've tested that with a source port too, see
Loïc Minier ha scritto:
> On Thu, Jun 08, 2006, Linkas wrote:
>> So I did my UDH as %06%05%04 %40%74 %00
>> Where the %40%74 is 16500 in HEX.
>
> You need a source port, and I don't think you need to add %00 at the
> end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the
> destinat
Oscar Elfving ha scritto:
> udh=%06%05%04%41%18%00%00
>
> This is how my UDH-string looks for sending to my java app at 16664 :)
> Hope this helps!
> You seem to be missing the terminating %00.
>
> Regards,
> Oscar Elfving
> On Jun 8, 2006, at 9:43 AM, Linkas wrote:
I will try that, thanks, mayb
On Thu, Jun 08, 2006, Linkas wrote:
> So I did my UDH as %06%05%04 %40%74 %00
> Where the %40%74 is 16500 in HEX.
You need a source port, and I don't think you need to add %00 at the
end. The typical WAP PUSH UDH is 0605040B8423F0, where 0B84 is the
destination port (2948) and 23F0 the source
udh=%06%05%04%41%18%00%00This is how my UDH-string looks for sending to my java app at 16664 :)Hope this helps!You seem to be missing the terminating %00.Regards,Oscar ElfvingOn Jun 8, 2006, at 9:43 AM, Linkas wrote:I think you misunderstood my question or my question was not clear:the problem is n
I think you misunderstood my question or my question was not clear:
the problem is not an HTTP port to call for kannel url, but special
ports used in sms to get different services.
Example: RTTTL (ringtones) normally go to phone in a special port - in
this way the phone can understand it's no
Hi Linkas,
When you specify in the kannel config file:
.
.
.
group = smsbox
bearerbox-host = localhost
sendsms-port = 14013
global-sender = 123
log-file = "/export/home/sites/sms/kannel/smsbox.log"
log-level = 1
access-log = "/export/home/sites/sms/kannel/smsaccess.log"
The server will listen f
Hello,
as I'm working with a J2ME application runnning on my phone in wich I
can specify on which port I can listen for sms messages, I was wondering
if anyone knows how to specify a specific destination port number with
kannel when sending messages.
I think this can be done setting the "dest
17 matches
Mail list logo
