Turpin, you cannot do that.

On TCP/IP CLIENT connections, you usually only specify one port for
the binding (the server port) , the other part is decided at Kernel
level.

Look at my case, I have a couple of connections with an SMSC over SMPP
on port 5109 (one for send and one for receive but NOT
transceiver-mode):

netstat -n | 

tcp        0      0 my.ip.add.ress:52055      his.ip.add.ress:5101    
   ESTABLISHED
tcp        0      0 my.ip.add.ress:52054      his.ip.add.ress:5101    
   ESTABLISHED

I've never specified the 52054/55 ports, the Kernel chose whatever
found appropiate (depending on availability and access, of course).
Even the receiver connection is a CLIENT connection for Kannel.

Remember: Kannel acts as an SMPP CLIENT, so it does not capture any ports. 

That's what a SERVER usually does: It capture a port (or many) for
himself, usually (but now always) a <1024 one (requiring root access
during capture of course).

Why do you require a specific port to bind Kannel to? If you're behind
a firewall, as long as you can reach the destination port, the
returning packets should traverse ok (if the firewall is well
configured), or you can set (or ask to) the FW to allow packets coming
form the SMSC IP to be routed to Kannel.

Hope it helps,



On Wed, 29 Dec 2004 10:50:36 -0300, Rodrigo A. Cremaschi
<[EMAIL PROTECTED]> wrote:
> 
> Turpin,
> 
>    I think you cannot stablish "our-port" under SMPP. Check the
> protocol/user guide first!
> 
>    Double check the protocol, ports, connection mode, SMPP version, user
> and password your SMSC is using. After that, configure your conection
> accordingly. If you still have problems, post your configuration file, and
> detailed log.
> 
>    Best Regards,
> 
> Rodrigo Cremaschi.
> 
> 
> ----- Original Message -----
> From: "TURPIN Patrick" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Cc: <[email protected]>
> Sent: Thursday, December 30, 2004 9:25 AM
> Subject: Re: KANNEL PORT NUMBER
> 
> > Hello,
> >
> > I identify the problem: We can't define the "SOURCE PORT" in SMPP mode!
> > The SMSC connexion port is ok but not the source port !
> > For more explication : the source port is the "local port" of my serveur
> > that the smsc use to connect to my server
> > MY SERVER (local port=600)<------>(connect port=700) SMSC SERVER
> > I also define the parameter : "our port" in the conf file but it dind't
> > do any thning, but if Y try to use de "EMI" protocol it work (but the
> > smsc use smpp) .
> >
> > The main error in the log file : "bind error"
> >
> > Also the SMSC can accept the transceiver mode.
> >
> > We don't know where to define It ?
> >
> >
> > I contact the smsc admin ans he say the the port source need to be
> > define, if is not the server cant accept the connexion .
> >
> > Thank to your help
> >
> >
> >
> 
> 
> Este mensaje se dirige exclusivamente a su destinatario y puede contener
> informaci�n CONFIDENCIAL sometida a secreto profesional o cuya divulgaci�n
> est� prohibida en virtud de la legislaci�n vigente. Si ha recibido este
> mensaje por error, le rogamos que nos lo comunique inmediatamente por esta
> misma v�a o por tel�fono (54.11 5776-5000) y proceda a su destrucci�n.
> N�tese que el correo electr�nico v�a Internet no permite asegurar ni la
> confidencialidad de los mensajes que se transmiten ni la correcta recepci�n
> de los mismos. En caso de que el destinatario de este mensaje no
> consintiera la utilizaci�n de correo electr�nico v�a Internet rogamos lo
> ponga en nuestro conocimiento de manera inmediata.
> 
> 


-- 
Alejandro Guerrieri
Magicom
http://www.magicom-bcn.net/

Reply via email to