Hi Holger,
If we will make any changes to OpenBSC code then we will release it as a
GPL. And regarding our MSC code, we got the permission from company that we
can release it as a GPL or GPL Compatible under the Licence for inhouse and
testing use.
We gone through SCCP and now we are going to start implementing SCCP in
Erlang and we gone through the SCCP files in Open BSC code. We are confused
that if we have to implement all SCCP function same as in OpenBSC in MSC to
communicate.
Please advice.
On Fri, Oct 1, 2010 at 1:38 PM, Holger Hans Peter Freyther <
holger(a)freyther.de> wrote:
On 10/01/2010 07:26 PM, tejas oza wrote:
Hi Holger,
We are going to build MSC using 'Erlang' which will
communicate
with OpenBSC 'C' code. Since we will be
dealing with SMS services only,
so
during MO operation our MSC should get messages
from OpenBSC and for MT
operation we should pass the messages to OpenBSC. As we will follow SS7
protocol for communication of MSC to HLR and MSC to SMSC and we will be
dealing with SCCP.
Will you be able to release the resulting code a GPL or GPL compatible?
We are concerned about Open BSC and MSC communication for SMS service and
we
need to know from OpenBSC code that what
particular messages are used for
SMS
transfer.
There is nothing SMS specific (besides using SAPI=3). Consult GSM08.08 for
the
messages between the MSC and the BSC.