23 Nov
2009
23 Nov
'09
8:23 p.m.
Hi zecke,
thanks for the update.
On Fri, Nov 20, 2009 at 06:13:33PM +0100, Holger Freyther wrote:
on-waves/mgcp:
- This includes the MGCP media gateway implementation. The MSC in use
has a mapping from the Circuit Identity Code (Multiplex + Timeslot)
to an MGCP Endpoint. To ease development I have one bsc process
and one mgcp one. To properly "connect" audio bsc and mgcp share
a secret which is the RTP port to be used... E.g. I can bind all
RTP ports ahead of time (also nice for tunneling data).
There is some overlap with the current rtp proxy code but I'm not
yet sure how these two fit together... So the future might be I
include the MGCP code in the BSC and use the existing proxy code..
but I really don't know right now.
Ok, I think what should rather happen is that the RTP proxy should be moved
into your MGCP process, as the RTP code should be a separate process anyway.
- In terms of OpenBSC I want this to be done
after the congress to not
create a mess right now.
yes, thanks for your consideration :)
as there is little danger of breaking things I have
merged the MGCP and SCCP
branches into master as well. I hope there is agreement (otherwise there is
always git revert)
this is fine. On a side note, the 'src' directory is getting quite a bit
full and chaotic now. I think we should probably converge around something
where we have src/common for common code, and then something like one directory
for each program that we build. i.e. something like
src/common
src/libbsc
src/bsc_hack
src/ipaccess-config
src/bs11-config
src/bsc_mgcp
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)