11 Jul
2013
11 Jul
'13
9:38 a.m.
Dear Harald,
On Thu, Jul 11, 2013 at 11:23 AM, Harald Welte <hwelte(a)sysmocom.de> wrote:
it's up to philosophy: if you are planning to keep a pure BSC code for
SCCPoverIP, or SS7 A-Interface as well.
In the second case, such a gateway is not needed at all, and my activities
make no sence
Dear Dmitri,
thanks for your patch, it will of course be merged.
On Thu, Jul 11, 2013 at 10:49:32AM +0400, Dmitri Soloviev wrote:
not yet
Right now there is a pilot with MNO, and Telscale
SS7 Card runs code
for A-interface gateway, converting BSSAP/SS7 to SCCPoverIP + rtp.
this is great news. Please let us know if you need any assistance. Did
I ever send you the protocol traces that you asked for?
It seems that such a gateway also has to adapt
OpenBSC to each
particular MSC.
I'm not sure if this really belongs into the gateway, or if we shouldn't
rather have this code in OsmoBSC itself.
So far, OsmoBSC has been used (to my knowledge) with Altobridge, Zynetix
(Globe Wireless) and Quortus.
We can introduce a 'msc model' in osmo-bsc, similar to having a 'bts
model', and then code e.g. generating 08.08 messages can selectively
check on the msc->model to have vendor-specific kludges.
Code will published as soon as pilot succeeds.
Great!
--
- Harald Welte <hwelte(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Schivelbeiner Str. 5
* 10439 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte