Hello Holger,
On Mon, 04 Oct 2010 16:33:15 +0800, "Holger Hans Peter Freyther" <holger(a)freyther.de> wrote:
>
> To implement Emergency Calls in bsc_hack you might need to change the gsm0408
> code of OpenBSC to handle the CM Service Request for emergency calls properly
> (e.g. check for a valid IMSI as of German regulations), and provide a 'dial
> plan' of where 110 should be forwarded to. E.g. it could make sense to have a
> small setting to forward 110 to a different mobile subscriber...
An additional hint to Andreas: The appended patch is a simple hack which
sets the subscriber number to be called for an Emgergency Call. I only
quickly tested this a while ago, so I don't know if it will always work.
And of course the fixed number used in the patch should be replaced by a
number tacken from the Config or DB.
Best regards,
Dieter
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hello all,
I would like to establish an emergency call with OpenBSC for testing
reasons.
I already set "rach emergency call allowed 1" but I get only a busy
line. Is there something else I have to do? I guess the emergency call
procedure is fully implemented in OpenBSC? I found some hints in the
code but I am still not sure.
Thanks,
Andreas
Hi Guys,
We are implementing the separate MSC module and we will be using the
openBSC, and we are mainly concerned for SMS services. So, I will be highly
obliged if you can provide us the documentation on openBSC code so that we
can understand the messages expected on separate MSC side from open BSC and
the messages to be sent from MSC to openBSC side.
--
Thanks & Regards
Tejas Oza
Dear sir,
I am planning to buy a ip.access nano BTS to run at GSM900.
What features should I quote as specification while placing the order ??
whether it (OpenBSC) will work properly with GSM900 or should I go for
DCS1800 ????
Thanks.
Hi,
I have been looking around and I am wondering, when you are interested in a
consumer 3G / Femto or Pico cell it might be very cheap through AT&T at
around $150. Might somebody be working rverse engineering on those cheaper
cells?
The nanoBTS from ipaccess is costing euro 3450 Mind you this is without any
software or server, just a single nanoBTS unit.
Does anybody have any experience and info about pricing? I find this price
crazy but it is the only way in the Netherland to buy it officially.
Also I have a license for GSM frequencies ad for that price they only send
it to an address.
Thanks
Albert
Hello,
Searching the web I found the following BTS:
http://www.haysystems.com/mobile-networks/hsl-picocell/
The System seams to be very similar to the ip.access nanoBTS.
POE and Abis over IP.
Can someone roughly estimate the time needed to integrate this BTS into
openBSC? The developer I have in mind already has some experience in
OpenBSC.
What exactly is needed to complete this task?
The company also has a different BTS called Femtocell. The interesting
thing is that they offer a "Femtocell Trial Package" for USD 7200. The
trail Package include BSC Software and two BTS. I also has a Network
Interface but I found nothing about the protocol used between BSC and BTS.
Regards
Konrad
Hello all,
I am trying to get a Positioning Capability Response from a MS by
sending an Positioning Capability Request. I checked ETSI TS 144 031
(v9.2.0) to figure out how to build the package. Only the
"extended-reference" field is mandatory and so I tried to send a package
just with the content of that field. The "extend-reference" consists of
the smlc-code and the transactionID.
By testing I found out that I have to send at least 6 octets. The first
octet is as usual the referenceNumber and to specify the rrlp component.
The last 2 bits of the 3rd octet and the first 4 bits of the 4th octet
are for the smlc-code. The rest of the 4th octet, the full 5th octet and
the first 6 bits of the 6th octet are for the transactionID.
Furthermore the first 3 bits of the second octet are for the choice
extension. Anyway I have no clue what the meaning is of the last 6 bits
of the 2nd octet and the first 6 bits of the 3rd octet although it seems
like that the 4th bit of the second octet is an extension bit.
However if I send a package I always get "Meassage too short" error.
Adding octets does not help.
Anyone has ever got a Positioning Capability Response for a Request? If
yes I would really appreciate if that someone would share this Request
with me.
Wireshark always shows me that I have sent a Positioning Capability
Request but the Response never comes but the error message. RRLP is
implemented in the phone since I get responses for a Measure Position
Request.
I think by now I have sent around 500 packages :) One example I am using
is: 0x30 0x0E 0x00 0xFF 0xA2 0x04
Best,
Andreas
