fredag 13. februar 2004, 03:20, skrev Phuah Yee Keat:
Err... I have got something to say over here...
Should this be a telco problem? or a protocol module problem?
For the CPA that I was talking about, it have some sense of
transaction for long messages. The difference with this transaction
Hmmm... after thinking over what you have said, you are probably right.
The protocol is CPA, Content Provider Architecture.
The protocol itself does have some stupid stuffs. Fully agreed that
everything is in the UDH, but yet the CPA protocol need separate fields
to do the transaction.
Christopher Kho wrote:
Hi,
I am trying to configure 2 kannel (smpp) for 2
different projects. My provider has set up an login
account for me to connect to their smsc. I am
able to connect to the smsc with no problem. I has
been assigned with 2 different numbers for those
projects, 1
or try to define address-range in your config...
On Friday 13 February 2004 14:47, Stipe Tolj wrote:
Christopher Kho wrote:
Hi,
I am trying to configure 2 kannel (smpp) for 2
different projects. My provider has set up an login
account for me to connect to their smsc. I am
able to
Attached are some diffs to implement OMA-style sending of OTA settings.
Refer to OMA-WAP-ProvCont-v1_1-20021112-C (at
http://www.openmobilealliance.org/tech/docs/) for details on how this
works.
The changes include all (most) the HMAC computation stuff required for
authentication. What I've
Hi there,
my Smsc gave me an UCP access but it requires me to connect FROM a defined
PORT and IP address TO a defined PORT and IP address.
Saying that the EMI/UCP server I need to connect TO is 191.9.65.89 port 5002
and that my kannel box should connect from 242.31.225.60 port 9000
I've set:
my Smsc gave me an UCP access but it requires me to connect FROM a defined
PORT and IP address TO a defined PORT and IP address.
Saying that the EMI/UCP server I need to connect TO is 191.9.65.89 port 5002
and that my kannel box should connect from 242.31.225.60 port 9000
I've set:
group
Replying to Stipe Tolj:
the 'our-port' defines the _server_ port of your side of the UCP
server itself is about to establish an TCP connection for MO
tranmissions ie. It is _not_ defining the client TCP port of the
connection towards the server. The OS is assigning this socket port
and you
After some trawling of the Nokia Developer site, it turns out not all
Series 40/60 support OMA CP. The first Series 60 to support this is the
6600. The first Series 40 to support is the 6800. This is why my phone
(an earlier Series 60) is not working. Would somebody on the list be
kind enough
