Hi
in order to decode Cipher Mode Command from Alcatel S-12, please accept a patch to gsm0808.c Without it OpenBSC rejects ciphering, and procedures are broken from MSC side
@@ -305,6 +305,7 @@ [GSM0808_IE_CELL_IDENTIFIER] = { TLV_TYPE_TLV }, [GSM0808_IE_CHOSEN_CHANNEL] = { TLV_TYPE_TV }, [GSM0808_IE_LAYER_3_INFORMATION] = { TLV_TYPE_TLV }, + [GSM0808_IE_LAYER_3_HEADER_INFORMATION] = { TLV_TYPE_TLV }, [GSM0808_IE_SPEECH_VERSION] = { TLV_TYPE_TV }, [GSM0808_IE_CHOSEN_ENCR_ALG] = { TLV_TYPE_TV }, },
Right now there is a pilot with MNO, and Telscale SS7 Card runs code for A-interface gateway, converting BSSAP/SS7 to SCCPoverIP + rtp.
It seems that such a gateway also has to adapt OpenBSC to each particular MSC. As an example, DTAP portion of Cipher Mode Complete must be removed for proper operation with S12.
Code will published as soon as pilot succeeds.
Best Regards,
Dmitri
On Thu, Jul 11, 2013 at 10:49 AM, Dmitri Soloviev dmi3sol@gmail.com wrote:
It seems that such a gateway also has to adapt OpenBSC to each particular MSC. As an example, DTAP portion of Cipher Mode Complete must be removed for proper operation with S12.
Could we specify MSC model in the config the same way we specify BTS model? Then we could have tweaks for each particular MSC with a simple "if()".
-- Regards, Alexander Chemeris. CEO, Fairwaves LLC / ООО УмРадио http://fairwaves.ru
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:
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!
Dear Harald,
On Thu, Jul 11, 2013 at 11:23 AM, Harald Welte hwelte@sysmocom.de wrote:
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:
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?
not yet
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.
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
Code will published as soon as pilot succeeds.
Great!
--
- Harald Welte hwelte@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
-
Alexander Chemeris -
Dmitri Soloviev -
Harald Welte