RE: [PATCH] SMPP

We faced that problem too. But we simply swiched to transceiver mode to
avoid it.

+1 from me.

Angel Fradejas
Mediafusión España, S.A.
[email protected]
www.mediafusion.es
Tel. +34 91 252 32 00
Fax +34 91 572 27 08


-----Mensaje original-----
De: [email protected] [mailto:[email protected]]En
nombre de Oded Arbel
Enviado el: viernes 21 de junio de 2002 00:06
Para: Nisan Bloch; [email protected]
Asunto: RE: [PATCH] SMPP


Good - we noticed that too.
+1 for commiting this to the stable branch.

--
Oded Arbel
m-Wise Mobile Solutions

[email protected]
Mobile: +972-67-340014
Tel: +972-9-9581711 (ext: 116)

::..
This book fills a much-needed gap.
	-- Moses Hadas in a review


> -----Original Message-----
> From: Nisan Bloch [mailto:[email protected]]
> Sent: Thursday, June 20, 2002 11:21 PM
> To: [email protected]
> Subject: [PATCH] SMPP
>
>
> Hi
>
> A small patch for the SMPP SMSC module.
> When the bind_receiver_resp comes in after the
> bind_transmitter_resp the
> SMPP module switches SMSCCONN_ACTIVE_RECV when it is allready in
> SMSCCONN_ACTIVE and preventing messages getting routed to this smsc.
>
> Nisan
>
> --- gw/smsc_smpp.c      Tue Jun  4 23:14:24 2002
> +++ /home/nisof/kannel/work/smsc_smpp.c     Thu Jun 20 23:27:44 2002
> @@ -779,6 +779,7 @@
>                         octstr_get_cstr(smpp->conn->id),
>                         pdu->u.bind_transmitter_resp.command_status);
>               } else {
> +                               if (smpp->conn->status !=
> SMSCCONN_ACTIVE)
>                   smpp->conn->status = SMSCCONN_ACTIVE_RECV;
>                   smpp->conn->connect_time = time(NULL);
>               }
>
>
>