Hi Holger,
We have wrapped the libsccp.a to our C node so can you let us know how it can be useful to write C Node as we run the code without wrapping the libsccp.a and it works fine.
We mean how can we make the best use of it !
On Thu, Oct 14, 2010 at 10:24 AM, Holger Hans Peter Freyther < holger@freyther.de> wrote:
On 10/14/2010 10:08 AM, tejas oza wrote:
Hi Holger,
We managed to send the paging request from MSC to OpenBSC and we can
track it
on wireshark that the packet format is correct but we are wonder if we
should
expect any response from OpenBSC to MSC for paging request and OpenBSC
code
seems to be returning -1 as per our understanding.
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.