My concern is to avoid a proliferation of interfaces in the core
engine. We might end up with one bit of code for Cisco, another for
Huawei, etc. Not ideal in the core. Best to keep these as separate
modules.
P.
On Sep 29, 2005, at 13:49, Alexander Simakov wrote:
Message: 1
Date: Tue, 27 Sep 2005 19:33:47 +0300
From: Paul Bagyenda <[EMAIL PROTECTED]>
Subject: Re: [Users] Mbuni: getting MSISDN from Cisco AS5300 access
server
To: Mbuni MMS Gateway Users List <[email protected]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Alexander,
This is very welcome indeed and am sure a lot of people will
find it handy.
I would suggest the following: This more properly fits within
the detokenizer module framework. That is, one needs to add a
library that one can call. It's arguments (passed in config file)
would include the the path to the script, etc.
Surely this will much more handy than a separate patch :)
The only gap so far is the detokenizer module is not being sent
the client IP. This is easy to add (I shall do so in CVS). Your
patch would then be an additional module (much like
mms_detokenize_shell) that would do what you describe.
Ok.
P.
_______________________________________________
Users mailing list
[email protected]
http://mbuni.org/mailman/listinfo/users_mbuni.org
_______________________________________________
Users mailing list
[email protected]
http://mbuni.org/mailman/listinfo/users_mbuni.org
