After running the command git checkout -b origin/on-waves/bsc-master , we are getting fatal: You are on a branch yet to be born

Hi Stefan, I managed to fix the problem.Thanks for your support. And now onwards I will post related to OpenBSC stuffs on this mailing list. Sorry for any churns.

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.

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.

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.

Hi Holger, We will publish our code as soon as we produced it. As you said we made C node and wrapped libsccp.a. After running bsc_msc_ip we are getting following error. *ozmank@ozmank-desktop:~/libosmocore/openbsc/openbsc/src$ ./bsc_msc_ip 130.238.15.219 58620 Bootstraping the network. Sending GSM08.08 reset. mi_e1_line_update could not open socket Address family not supported by protocol full talloc report on 'sccp' (total 29 bytes in 2 blocks) struct sccp_data_callback contains 28 bytes in 1 blocks (ref 0) 0x9ca12a8* Can you please advice.

Hi Holger, Right now we do not have any BTS but we are going to have nano BTS it soon. So we are trying to communicate between BSC and MSC only without having BTS. We created openbsc.cfg file and tried to avoid the BTS configuration in it and run but with no success.

We are able to connect to MSC but after it gets connected, it throws below error:- [...] So We are wonder that if we are sending some wrong packet OR wrong packet format from MSC to BSC as it is throwing cannot read the packet. Can you Please advice.

On 10/12/2010 01:15 PM, Harald Welte wrote: file) make You can download the latest version of wireshark, it will detect the IPA protocol on port 5000. Two things to note on the stream.. a) use the right header.. e.g. the length (two byte) is in network order b) send header + payload together... our code makes that assumption

On 10/14/2010 10:08 AM, tejas oza wrote: track it should code Theory: After you sent the Paging Request the BSC will start to page the subscriber. If the Mobile Stations sees the Paging Request it will open a channel with the BSC, the BSC will forward the Paging Response to the MSC on a new SCCP connection. Ironically the code you are using has a bsc_msc_ip.c:test_msc that is called when you send the ID_GET request. This will send you the data of a paging response, so you could start dealing with connections while we figure out the current issue. Issue: You are right the package looks good. You will need to go to the code to figure out what is wrong. You should set a breakpoint in ipaccess_read_msg (src/input/ipaccess.c). It will try to receive the header and then it will receive the data. In the other mail I have indicated that you need to send header + data as one packet (instead of two writes for header and data). You can use gdb to step through these lines of code and you should see the place where it returns NULL.

On 10/15/2010 10:15 AM, tejas oza wrote: can libsccp.a Hi, did you resolve the other problem? I am not sure I understand your current question?

well check the header file called sccp.h? It contains functions to handle the connections, but also functions to just parse and generate packets.

Hi Holger, We found the below code in bsc_msc_ip.c static int msc_sccp_accept(struct sccp_connection *connection, void *data) { LOGP(DMSC, LOGL_DEBUG, "Rejecting incoming SCCP connection.\n"); return -1; } So, Does the Open BSC accepts the SCCP connection request from MSC ?

Hi Holger, Kindly find the Attachment for SCCP Patch.

Hi zecke,

GSM 08.06 Chapter 6.1 Connection establishment: ii) the MSC decides to perform an external handover and a new dedicated radio resource has t obe reserved in the new BSS. The SCCP connection establishment is then initiated by the MSC So there is at least one case in which this procedure is being used. I know, we only do intra-BSC handover at the moment and no external handover is supported. But I think you might be interested in this anyway :)