Hi,
Don't do that. Instead use this:
client -> opensmppbox -> bearerbox (1.5) ->SMScs
Bearerbox 1.5 is stable enough to use in production.
BR,
Nikos
----- Original Message -----
From: "Wayne Gemmell" <[email protected]>
To: "Nikos Balkanas" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, April 20, 2011 10:37 AM
Subject: Re: Connecting a development kannel instance to a stable instance
Hi Nikos
That is the problem. I can't bolt opensmpp onto the stable box (afaik
anyway,
I'm no expert.) I need the following configuration.
client --> opensmpp --> dev server (1.5) --> production server (1.4.1) -->
network smscs.
Sorry if I wasn't clear
--
Regards
Wayne
On Wednesday 20 April 2011 06:08:08 Nikos Balkanas wrote:
Hi,
You cannot connect bearerbox to another bearerbox directly. You need
opensmppbox in between. You should have no problems connecting
development
with stable releases, as long as they are compatible versions. 1.4.3
should
be compatible with 1.5.0 for communication purposes. However, you still
have to build opensmppbox using the latest.
BR,
Nikos
----- Original Message -----
From: "Wayne Gemmell" <[email protected]>
To: <[email protected]>
Sent: Tuesday, April 19, 2011 4:31 PM
Subject: Connecting a development kannel instance to a stable instance
> Hi all
>
> Please disregard my previous email, it was sent in error.
>
> I've setup opensmpp on a development box. Now I would like to bring it
> into my
> production environment without changing my production box from stable
> to
> development. I understand that you cannot connect a development
> instance
> of
> bearerbox to a stable one as the protocol has changed. Any ideas how to
> do this? Is there a sort of proxy available?
--
Cheers
Wayne
