-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stipe Tolj wrote:
|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
On 13.02.2004, at 19:27, Misc wrote:
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.
if you ask me, ask your UCP providers to read a book about how TCP/IP
works.
Forcing you to use a specific tcp port on
Configuring NAT is not the only option.
I have the same issue with outgoing local port with my local telco,
and in my sms application written in perl I have easily passed it with LocalPort
option
of IO::Socket::INET object. I think it is done with bind(2) and can be easily
implemented
in
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
