10 Nov
2012
10 Nov
'12
11:33 a.m.
<000f> bsc_api.c:315 Sending ChanModify for speech 1 1
<000c> rtp_proxy.c:258 Correcting frame difference of 38886 frames
I used to get these messages when I make a call using osmo-nitb.
But recently I updated to newest git version and I get something like
<000b> bsc_api.c:374 Sending ChanModify for speech 0 1
<000b> bsc_api.c:118 Using non speech mode: 0
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
And I get no sound for my phones.
There is a year gap between the previous version and the new version, so I
couldn't locate exactly what change is causing this.
Can somebody help me fixing it?
10 Nov
10 Nov
7:28 p.m.
On Sat, Nov 10, 2012 at 07:33:39PM +0900, Pierre Kim wrote:
Dear Kim,
<000b> bsc_api.c:374 Sending ChanModify for
speech 0 1
<000b> bsc_api.c:118 Using non speech mode: 0
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
this message is 'wrong' and should be removed.
And I get no sound for my phones.
Can somebody help me fixing it?
well please provide the following items:
1.) the command line you use to start osmo-nitb
2.) a pcap file for tracing port 3002, port 3003 and UDP (for
rtp).
cheers
holger
8:35 p.m.
Here is the pcap file
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 3:29 AM
To: openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
On Sat, Nov 10, 2012 at 07:33:39PM +0900, Pierre Kim wrote:
Dear Kim,
<000b> bsc_api.c:374 Sending ChanModify for
speech 0 1
<000b> bsc_api.c:118 Using non speech mode: 0
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
this message is 'wrong' and should be removed.
And I get no sound for my phones.
Can somebody help me fixing it?
well please provide the following items:
1.) the command line you use to start osmo-nitb
2.) a pcap file for tracing port 3002, port 3003 and UDP (for rtp).
cheers
holger
11 Nov
11 Nov
9:17 a.m.
On Sun, Nov 11, 2012 at 04:35:37AM +0900, Pierre Kim wrote:
Here is the pcap file
Hi,
I asked for pcap and invocation. The invocation is missing.
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
well please provide the following items:
1.) the command line you use to start osmo-nitb
2.) a pcap file for tracing port 3002, port 3003 and UDP (for rtp).
11:14 a.m.
I start it with
sudo ./osmo-nitb -m -P
and I did not change anything other than the operating band(PCS1900) from
the default nanobts configuration file.
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 5:18 PM
To: Pierre Kim
Cc: openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
On Sun, Nov 11, 2012 at 04:35:37AM +0900, Pierre Kim wrote:
Here is the pcap file
Hi,
I asked for pcap and invocation. The invocation is missing.
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Holger Hans
Peter Freyther
well please provide the following items:
1.) the command line you use to start osmo-nitb
2.) a pcap file for tracing port 3002, port 3003 and UDP (for rtp).
11:33 a.m.
On Sun, Nov 11, 2012 at 07:14:32PM +0900, Pierre Kim wrote:
Hi,
I start it with
sudo ./osmo-nitb -m -P
please try with the built-in mncc and without the proxy.
and I did not change anything other than the operating band(PCS1900) from
the default nanobts configuration file.
You were using libosmo-abis one year ago? Please include your OpenBSC
configuration file. I think you are not using the right BTS type (or I am
too blind to see it.. or the channel modify ack was actually a nack and
the channel type was not switched to speech).
12:50 p.m.
Here's the pcap file captured from built in mncc.
It works just fine.
And the console says
<000b> bsc_api.c:374 Sending ChanModify for speech 33 1
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
And I already sent you the configuration file(directly to your email)
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 7:33 PM
To: Pierre Kim
Cc: openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
On Sun, Nov 11, 2012 at 07:14:32PM +0900, Pierre Kim wrote:
Hi,
I start it with
sudo ./osmo-nitb -m -P
please try with the built-in mncc and without the proxy.
and I did not change anything other than the operating band(PCS1900)
from the default nanobts configuration file.
You were using libosmo-abis one year ago? Please include your OpenBSC
configuration file. I think you are not using the right BTS type (or I am
too blind to see it.. or the channel modify ack was actually a nack and the
channel type was not switched to speech).
1:36 p.m.
On Sun, Nov 11, 2012 at 08:50:54PM +0900, Pierre Kim wrote:
Here's the pcap file captured from built in mncc.
It works just fine.
And the console says
<000b> bsc_api.c:374 Sending ChanModify for speech 33 1
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
Hi,
the PBX is 'LCR'? The MNCC interface was not versioned and there
were some changes. I added versioning and I think Andreas had not
merged my code:
http://git.misdn.eu/?p=projects/lcr.git;a=shortlog;h=refs/heads/holger/clea…
holger
3:17 p.m.
Hmm, I am trying to build lcr from your git repo.
But it seems to be broken
chan_lcr.c:701:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING PROBLEM
chan_lcr.c: In function 'lcr_in_setup':
chan_lcr.c:950: error: 'struct ast_channel' has no member named
'redirecting'
chan_lcr.c:951: error: 'struct ast_channel' has no member named 'caller'
chan_lcr.c: In function 'lcr_request':
chan_lcr.c:2145: error: 'requestor' undeclared (first use in this function)
chan_lcr.c:2145: error: (Each undeclared identifier is reported only once
chan_lcr.c:2145: error: for each function it appears in.)
make[1]: *** [chan_lcr.po] Error 1
make[1]: Leaving directory `/home/manatails/gsmc/lcr'
make: *** [all] Error 2
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Sunday, November 11, 2012 9:37 PM
To: Pierre Kim
Cc: openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
On Sun, Nov 11, 2012 at 08:50:54PM +0900, Pierre Kim wrote:
Here's the pcap file captured from built in mncc.
It works just fine.
And the console says
<000b> bsc_api.c:374 Sending ChanModify for speech 33 1 <000b>
osmo_msc.c:73 Assignment complete should not have been reached.
Hi,
the PBX is 'LCR'? The MNCC interface was not versioned and there were some
changes. I added versioning and I think Andreas had not merged my code:
http://git.misdn.eu/?p=projects/lcr.git;a=shortlog;h=refs/heads/holger/clean
ing
holger
5:30 p.m.
On Sun, Nov 11, 2012 at 11:17:58PM +0900, Pierre Kim wrote:
Hi,
Hmm, I am trying to build lcr from your git repo.
But it seems to be broken
I think you need to take it up with Andreas but please include the version
of LCR and Asterisk you are compiling against.
holger
chan_lcr.c:701:2: warning: #warning DISABLED DUE TO
DOUBLE LOCKING PROBLEM
chan_lcr.c: In function 'lcr_in_setup':
chan_lcr.c:950: error: 'struct ast_channel' has no member named
'redirecting'
chan_lcr.c:951: error: 'struct ast_channel' has no member named 'caller'
chan_lcr.c: In function 'lcr_request':
chan_lcr.c:2145: error: 'requestor' undeclared (first use in this function)
chan_lcr.c:2145: error: (Each undeclared identifier is reported only once
chan_lcr.c:2145: error: for each function it appears in.)
make[1]: *** [chan_lcr.po] Error 1
make[1]: Leaving directory `/home/manatails/gsmc/lcr'
make: *** [all] Error 2
6 p.m.
I am using the latest git for LCR
And Asterisk 1.6.2.9 for Debian
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Holger Hans Peter
Freyther
Sent: Monday, November 12, 2012 1:30 AM
To: Pierre Kim
Cc: openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
On Sun, Nov 11, 2012 at 11:17:58PM +0900, Pierre Kim wrote:
Hi,
Hmm, I am trying to build lcr from your git repo.
But it seems to be broken
I think you need to take it up with Andreas but please include the version
of LCR and Asterisk you are compiling against.
holger
chan_lcr.c:701:2: warning: #warning DISABLED DUE TO
DOUBLE LOCKING
PROBLEM
chan_lcr.c: In function 'lcr_in_setup':
chan_lcr.c:950: error: 'struct ast_channel' has no member named
'redirecting'
chan_lcr.c:951: error: 'struct ast_channel' has no member named 'caller'
chan_lcr.c: In function 'lcr_request':
chan_lcr.c:2145: error: 'requestor' undeclared (first use in this
function)
chan_lcr.c:2145: error: (Each undeclared identifier is reported only
once
chan_lcr.c:2145: error: for each function it appears in.)
make[1]: *** [chan_lcr.po] Error 1
make[1]: Leaving directory `/home/manatails/gsmc/lcr'
make: *** [all] Error 2
6:11 p.m.
Pierre Kim wrote:
I am using the latest git for LCR
And Asterisk 1.6.2.9 for Debian
hi pierre,
could you try jolly/new branch of lcr? it will be more convenient and
should have this bug fixed. (iirc) also it does not rely on mISDN
anymore, if you just want to interface gsm with asterisk or gsm with sip.
regards,
andreas
6:18 p.m.
This is what I get when I try to compile on jolly/new
chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING PROBLEM
chan_lcr.c: In function 'lcr_read':
chan_lcr.c:2901: error: request for member 'integer' in something not a
structure or union
make[1]: *** [chan_lcr.po] Error 1
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Monday, November 12, 2012 2:11 AM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
Pierre Kim wrote:
I am using the latest git for LCR
And Asterisk 1.6.2.9 for Debian
hi pierre,
could you try jolly/new branch of lcr? it will be more convenient and should
have this bug fixed. (iirc) also it does not rely on mISDN anymore, if you
just want to interface gsm with asterisk or gsm with sip.
regards,
andreas
13 Nov
13 Nov
12:52 p.m.
Pierre Kim wrote:
This is what I get when I try to compile on jolly/new
chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING PROBLEM
chan_lcr.c: In function 'lcr_read':
chan_lcr.c:2901: error: request for member 'integer' in something not a
structure or union
make[1]: *** [chan_lcr.po] Error 1
hi pierre,
can you try this patch? if it works, let me know.
regards,
andreas
1:08 p.m.
Um... I think you forgot to attach the patch file?
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Tuesday, November 13, 2012 8:52 PM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
Pierre Kim wrote:
This is what I get when I try to compile on jolly/new
chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING
PROBLEM
chan_lcr.c: In function 'lcr_read':
chan_lcr.c:2901: error: request for member 'integer' in something not
a structure or union
make[1]: *** [chan_lcr.po] Error 1
hi pierre,
can you try this patch? if it works, let me know.
regards,
andreas
3:12 p.m.
Pierre Kim wrote:
Um... I think you forgot to attach the patch file?
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Tuesday, November 13, 2012 8:52 PM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
Pierre Kim wrote:
sorry
This is what I get when I try to compile on
jolly/new
chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING
PROBLEM
chan_lcr.c: In function 'lcr_read':
chan_lcr.c:2901: error: request for member 'integer' in something not
a structure or union
make[1]: *** [chan_lcr.po] Error 1
hi pierre,
can you try this patch? if it works, let me know.
regards,
andreas
5:29 p.m.
Hello,
Your patched worked, now I can compile LCR without getting any errors.
However, this error still persists:
<000b> bsc_api.c:374 Sending ChanModify for speech 0 1
<000b> bsc_api.c:118 Using non speech mode: 0
<000b> osmo_msc.c:73 Assignment complete should not have been reached.
I still think OpenBSC itself causes this problem as it is the only thing
I've changed.
Any ideas?
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Tuesday, November 13, 2012 11:12 PM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
Pierre Kim wrote:
Um... I think you forgot to attach the patch file?
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Andreas
Eversberg
Sent: Tuesday, November 13, 2012 8:52 PM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
Pierre Kim wrote:
sorry
This is what I get when I try to compile on
jolly/new
chan_lcr.c:693:2: warning: #warning DISABLED DUE TO DOUBLE LOCKING
PROBLEM
chan_lcr.c: In function 'lcr_read':
chan_lcr.c:2901: error: request for member 'integer' in something not
a structure or union
make[1]: *** [chan_lcr.po] Error 1
hi pierre,
can you try this patch? if it works, let me know.
regards,
andreas
8:31 p.m.
On Wed, Nov 14, 2012 at 01:29:56AM +0900, Pierre Kim wrote:
Dear Pierre, Andreas,
please cherry-pick my four patches from the holger/cleaning-rebased
branch. This will make sure that both LCR and OpenBSC agree on the
size of structures for MNCC and offsets inside these structs. If this
code does not detect a mismatch we can continue from there.
10:10 p.m.
Holger Hans Peter Freyther wrote:
On Wed, Nov 14, 2012 at 01:29:56AM +0900, Pierre Kim
wrote:
Dear Pierre, Andreas,
please cherry-pick my four patches from the holger/cleaning-rebased
branch. This will make sure that both LCR and OpenBSC agree on the
size of structures for MNCC and offsets inside these structs. If this
code does not detect a mismatch we can continue from there.
hi holger,
i will try to set up my bs11 with all the latest git sources tomorrow.
then i will look at the chan modify issue.
regards,
andreas
14 Nov
14 Nov
11:05 a.m.
hi holger,
i will try to set up my bs11 with all the latest git sources tomorrow.
then i will look at the chan modify issue.
regards,
andreas
hi,
just tested and fixed lcr/new branch. it works now with master branch of
openbsc. indeed it is quite a good idea to check version/sizeo of MNCC
interface.
regards,
andreas
4:29 p.m.
On Wed, Nov 14, 2012 at 11:05:53AM +0100, Andreas Eversberg wrote:
just tested and fixed lcr/new branch. it works now
with master
branch of openbsc. indeed it is quite a good idea to check
version/sizeo of MNCC interface.
Shall I rebase the LCR/MNCC patches for lcr/new? Do you advise to
use lcr/new to connect with the EventPhone at the 29C3?
holger
7:13 p.m.
Holger Hans Peter Freyther wrote:
Shall I rebase the LCR/MNCC patches for lcr/new? Do
you advise to
use lcr/new to connect with the EventPhone at the 29C3?
hi holger,
yes i do, because jolly/new has improved audio handling.
bridging/conferencing is not done via mISDN only, but also inside lcr.
this way it is not required to use isdn loop interfaces to connect
chan_lcr, sip, isdn and gsm together. it is now routed inside lcr. for
all interfaces except isdn, you don't need mISDN at all. (if you diff
between master and jolly/new, you might get scared.)
we can use a sip trunk to eventphone and an isdn trunk. we could use
(for a test) isdn for two days and sip the other two days.
regards,
andreas
7:17 p.m.
On Wed, Nov 14, 2012 at 07:13:01PM +0100, Andreas Eversberg wrote:
Holger Hans Peter Freyther wrote:
we can use a sip trunk to eventphone and an isdn trunk. we could use
(for a test) isdn for two days and sip the other two days.
ah great. At the 28C3 we used the E1/ISDN over IP option in mISDN and
I would assume we do something like this again.
holger
12 Nov
12 Nov
5:55 p.m.
Could you tell me what version of asterisk do I have to have in order to
compile LCR successfully?
-----Original Message-----
From: openbsc-bounces(a)lists.osmocom.org
[mailto:openbsc-bounces@lists.osmocom.org] On Behalf Of Andreas Eversberg
Sent: Monday, November 12, 2012 2:11 AM
To: Pierre Kim
Cc: 'Holger Hans Peter Freyther'; openbsc(a)lists.osmocom.org
Subject: Re: ChanModify
Pierre Kim wrote:
I am using the latest git for LCR
And Asterisk 1.6.2.9 for Debian
hi pierre,
could you try jolly/new branch of lcr? it will be more convenient and should
have this bug fixed. (iirc) also it does not rely on mISDN anymore, if you
just want to interface gsm with asterisk or gsm with sip.
regards,
andreas
4185
days inactive
4186
days old
24 comments
3 participants
participants (3)
-
Andreas Eversberg -
Holger Hans Peter Freyther -
Pierre Kim