16 May
2012
16 May
'12
4:49 p.m.
Hello.
*Can someone help me out at this point of the Osmocom-bb project [making a
call]....
I am done with all the steps involved in the project.
1. i have added the /.osmocom/bb/mobile.cfg
2. i am in the branch sylvian/testing
I used git checkout --track -b remotes/origin/sylvian/testing
command to enter this branch. It worked right... Am i RIGHT here?
3. when i download the firmware layer 1 on the phone it worked pretty good.
it says..*
handle_write(): finished
got 1 bytes from modem, data looks like: 1b .
got 1 bytes from modem, data looks like: f6 .
got 1 bytes from modem, data looks like: 02 .
got 1 bytes from modem, data looks like: 00 .
got 1 bytes from modem, data looks like: 41 A
got 1 bytes from modem, data looks like: 03 .
got 1 bytes from modem, data looks like: 42 B
Received DOWNLOAD ACK from phone, your code is running now!
battery_compal_e88_init: starting up
OSMOCOM Layer 1 (revision osmocon_v0.0.0-1348-g083a2dc)
======================================================================
Device ID code: 0xb4fb
Device Version code: 0x0000
ARM ID code: 0xfff3
cDSP ID code: 0x0128
Die ID code: f2d81c119e039be2
======================================================================
REG_DPLL=0x2413
CNTL_ARM_CLK=0xf0a1
CNTL_CLK=0xff91
CNTL_RST=0xfff3
CNTL_ARM_DIV=0xfff9
======================================================================
Power up simcard:
Assert DSP into Reset
Releasing DSP from Reset
Setting some dsp_api.ndb values
Setting API NDB parameters
DSP Download Status: 0x0001
DSP API Version: 0x0000 0x0000
Finishing download phase
DSP Download Status: 0x0002
DSP API Version: 0x3606 0x0000
LOST 1161!
BAT-ADC: 549 6 0 0 1023 349 328 204
Charger at 51 mV.
Battery at 3753 mV.
Charging at 0 mA.
Battery capacity is 69%.
Battery range is 3199..3999 mV.
Battery full at 468 LSB .. full at 585 LSB
Charging at 239 LSB (204 mA).
BCICTL2=0x3ff
battery-info.flags=0x00000000
bat_compal_e88_chg_state=0
*
4. when i launch the MOBILE application it says like*
000f> sim.c:1223 init SIM client
<0006> gsm48_cc.c:63 init Call Control
<0007> gsm480_ss.c:231 init SS
<0017> gsm411_sms.c:63 init SMS
<0001> gsm48_rr.c:5479 init Radio Ressource process
<0005> gsm48_mm.c:1315 init Mobility Management process
<0005> gsm48_mm.c:1037 Selecting PLMN SEARCH state, because no SIM.
<0002> gsm322.c:5025 init PLMN process
<0003> gsm322.c:5026 init Cell Selection process
Mobile '1' initialized, please start phone now!
VTY available on port 4247.
<0005> subscriber.c:601 Requesting SIM file 0x2fe2
<000f> sim.c:209 got new job: SIM_JOB_READ_BINARY (handle=00000004)
<000f> sim.c:697 go MF
<000f> sim.c:241 SELECT (file=0x3f00)
000f> sim.c:949 command successfull
<000f> sim.c:151 sending result to callback function (type=0)
<0005> subscriber.c:360 received SMSP from SIM (sca=+49232********000)
<0005> subscriber.c:561 (ms 1) Done reading SIM card
(IMSI=26****************654 Germany, E-Plus)
<0005> subscriber.c:573 -> SIM card registered to 262 03 (Germany, E-Plus)
<0005> gsm48_mm.c:4379 (ms 1) Received 'MMR_REG_REQ' event
<0002> gsm322.c:3806 (ms 1) Event 'EVENT_SIM_INSERT' for automatic PLMN
selection in state 'A0 null'
<000e> gsm322.c:1372 Start search of last registered PLMN (mcc=262 mnc=03
Germany, E-Plus)
<0002> gsm322.c:1376 Use RPLMN (mcc=262 mnc=03 Germany, E-Plus)
<0002> gsm322.c:800 new state 'A0 null' -> 'A1 trying RPLMN'
<0003> gsm322.c:4037 (ms 1) Event 'EVENT_NEW_PLMN' for Cell selection in
state 'C0 null'
<000e> gsm322.c:3619 Selecting PLMN (mcc=262 mnc=03 Germany, E-Plus)
<0003> gsm322.c:3628 Start normal cell selection.
<0003> gsm322.c:823 new state 'C0 null' -> 'C1 normal cell
selection'
<0003> gsm322.c:2791 Scanning power for all frequencies.
*
Here its starts to search for frequencies and cells..... and see what
happens....
*
<0003> gsm322.c:2852 Scanning frequencies. (0..0)
<0003> gsm322.c:2913 Done with power scanning range.
<0003> gsm322.c:2791 Scanning power for all frequencies.
<0003> gsm322.c:2852 Scanning frequencies. (512(DCS)..512(DCS))
<0003> gsm322.c:2913 Done with power scanning range.
<0003> gsm322.c:2791 Scanning power for all frequencies.
<0003> gsm322.c:2852 Scanning frequencies. (975..975)
<0003> gsm322.c:2913 Done with power scanning range.
<0003> gsm322.c:2791 Scanning power for all frequencies.
<0003> gsm322.c:2813 Found no frequency.
This repeats all the TIME........
*I am able to login to the vty terminal and able to execute some
instructions.....
*
enable
show ms
show subscriber
etc*
when I try to make a call..... see what happens*
<0009> mnccms.c:570 Make call to 01747180018
<0009> mnccms.c:150 support TCH/H also
<0009> mnccms.c:174 support full rate v2
<0009> mnccms.c:178 support full rate v1
<0009> mnccms.c:187 support half rate v1
<0006> transaction.c:76 ms 1 allocates transaction (proto 3 trans_id 255
callref 1 mem 0x8cf7370)
<0006> gsm48_cc.c:243 new state NULL -> MM_CONNECTION_PEND
<0006> gsm48_cc.c:507 Sending MMCC_EST_REQ
<0005> gsm48_mm.c:3774 (ms 1) Received 'MMCC_EST_REQ' event in state MM
idle
<0005> gsm48_mm.c:3777 -> substate PLMN search
<0005> gsm48_mm.c:3779 -> callref 1, transaction_id 255
<0005> gsm48_mm.c:3042 Init MM Connection, not in normal state.
<0006> gsm48_cc.c:2161 (ms 1) Received 'MMCC_REL_IND' in CC state
MM_CONNECTION_PEND
<0006> gsm48_cc.c:196 (ms 1 ti ff) Sending 'MNCC_REL_IND' to MNCC.
<0006> gsm48_cc.c:243 new state MM_CONNECTION_PEND -> NULL
<0006> transaction.c:104 ms 1 frees transaction (mem 0x8cf7370)
<0009> mnccms.c:372 Call has been released (cause 21)
<0009> mnccms.c:71 (call 1) Call removed.
0003> gsm322.c:2889 Getting PM for ARFCN 858(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 859(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 860(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 861(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 862(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 863(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 864(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 865(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 866(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 867(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 868(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 869(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 870(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 871(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 872(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 873(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 874(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 875(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 876(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 877(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 878(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 879(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 880(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 881(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 882(DCS) twice. Overwriting the
first! Please fix prim_pm.c
<0003> gsm322.c:2889 Getting PM for ARFCN 883(DCS) twice
I even find this sometimes................
can someone fix this for me.... where could be the error......
Looking forward for a helping hand.....
Thank you..
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
20 May
20 May
4:33 a.m.
First we are in the same shoe of fixing prim.c and I can assure you that if
you
find anyone that respond you must be lucky.
Secondly, you jumped the gun by making call when you very well know that
MS has not camped on any cell. There is no point in going ahead, just relax
take your time and open the damn code as only solution proffer for a case
as yours and mine.
Just to give a nudge, find more information about gsm servcie in your
location,
get a registered sim that work with 900Mhz. If you are lucky that the band
function
in your area, then set sim parameter too 900 band only and make use of stick
option
AFRCN. I believe by that OBB should work for you.
However, if you are so unlucky as I am with PCS band only working in my
area, then you
will have to roll up your sleeve, google GSM 03.22 TS and read through it.
That will
give you an idea of IDLE MODE state work. After that, bury yourself in OBB
code and open
file gsm322.c where the IDLE MODE is implemented. Doing this I assumed that
you are
already familiar with basic GSM technology. Thus, you can troubleshoot what
might be the
issue and find solution to it.
That is my best recipes for you now cause I am as well still battling with
the actual issue
you are having. If thing works out for you please let me know.
Best of luck.
Sincerely,
Rasak
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
21 May
21 May
6:10 p.m.
Thank you so much for your help....
I had bought a new SIM and started testing. and its WORKING. I am able to
make call and also sms.
I have two Motorola c123 handsets. One work very good and the other is also
camping onto a cell, doing all other scanning for frequencies and other
stuff but provides only emergency calls... I cud nt make calls from the
second handset.
Where do u stay. How come you dont have a GSM band in your area.
I started with the layer23 application. I didnt understand where to use
this command. In which path??
./layer23 -a 871 -i 127.0.0.1
I dont understand where and how to launch this application. Can you kindly
explain me this.
Thanks in advance
Yours Sincerely
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
6:14 p.m.
Layer23 only exists in the burst_ind branch as far as I know.
(see my buildscript here:
https://aur.archlinux.org/packages/os/osmocombb-git/PKGBUILD )
On Mon, 21 May 2012, Altaf wrote:
Thank you so much for your help....
I had bought a new SIM and started testing. and its WORKING. I am able to
make call and also sms.
I have two Motorola c123 handsets. One work very good and the other is also
camping onto a cell, doing all other scanning for frequencies and other
stuff but provides only emergency calls... I cud nt make calls from the
second handset.
Where do u stay. How come you dont have a GSM band in your area.
I started with the layer23 application. I didnt understand where to use
this command. In which path??
./layer23 -a 871 -i 127.0.0.1
I dont understand where and how to launch this application. Can you kindly
explain me this.
Thanks in advance
Yours Sincerely
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
24 May
24 May
6:49 p.m.
When I run the Layer23(ccch_scan) application it gives me the following
output on the terminal....
Failed to connect to '/tmp/osmocom_sap'.
Failed during sap_open(), no SIM reader
<000c> l1ctl.c:114 FBSB RESP: result=255
What does it mean.. Can some one help me at this point..
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
7:33 p.m.
http://lists.osmocom.org/pipermail/baseband-devel/2012-April/002946.html
On Thu, May 24, 2012 at 9:49 AM, Altaf <altaf329(a)gmail.com> wrote:
When I run the Layer23(ccch_scan) application it gives
me the following
output on the terminal....
Failed to connect to '/tmp/osmocom_sap'.
Failed during sap_open(), no SIM reader
<000c> l1ctl.c:114 FBSB RESP: result=255
What does it mean.. Can some one help me at this point..
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
7:36 p.m.
http://lists.osmocom.org/pipermail/baseband-devel/2012-May/003004.html
On Thu, May 24, 2012 at 10:33 AM, Joshua Pereyda
<pere5027(a)vandals.uidaho.edu> wrote:
http://lists.osmocom.org/pipermail/baseband-devel/2012-April/002946.html
On Thu, May 24, 2012 at 9:49 AM, Altaf <altaf329(a)gmail.com> wrote:
> When I run the Layer23(ccch_scan) application it gives me the following
> output on the terminal....
>
> Failed to connect to '/tmp/osmocom_sap'.
> Failed during sap_open(), no SIM reader
> <000c> l1ctl.c:114 FBSB RESP: result=255
>
> What does it mean.. Can some one help me at this point..
>
> --
> View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
> Sent from the baseband-devel mailing list archive at Nabble.com.
>
>
21 May
21 May
7:16 p.m.
Hi,
Good to hear that at least you can make calls with one and the other camped
perfectly with limited service. That is milestone you just covered with
ease.
Where do u stay. How come you dont have a GSM band in
your area.
I stay in US where GSM band is a bit different from the rest of the World
and as well the phone rf radio in some cases differ. The bands around me are
850 and PCS1900. My SIM career uses PCS1900. Also Motorola c123 with the
radio band serving my area is hard to come by. So I guess, that is where my
predicament lies. Hopefully I might get help eventually.
I started with the layer23 application. I didnt
understand where to use
this command. In which path??
./layer23 -a 871 -i 127.0.0.1
layer23 app has been demoted for ccch app for a very long time ago. So
disregard any instruction related to running of layer23, it should be
ccch-app.
I will implore that you first search the mailing list archive for solution
before making a post; by that you can easily find solution to many problems
and learn from others mistakes.
Best of luck.
Sincerely,
Rasak
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
9:43 p.m.
For what it's worth, you can get the Motorola c155 (barely) on Amazon
right now. It seems to work with OsmocomBB, but my SIM is locked and
customer support either didn't want to or was unable to give me the
PIN.
Josh
On Mon, May 21, 2012 at 10:16 AM, rola <roladunjoye(a)gmail.com> wrote:
Hi,
Good to hear that at least you can make calls with one and the other camped
perfectly with limited service. That is milestone you just covered with
ease.
Where do u stay. How come you dont have a GSM band
in your area.
I stay in US where GSM band is a bit different from the rest of the World
and as well the phone rf radio in some cases differ. The bands around me are
850 and PCS1900. My SIM career uses PCS1900. Also Motorola c123 with the
radio band serving my area is hard to come by. So I guess, that is where my
predicament lies. Hopefully I might get help eventually.
I started with the layer23 application. I didnt
understand where to use
this command. In which path??
./layer23 -a 871 -i 127.0.0.1
layer23 app has been demoted for ccch app for a very long time ago. So
disregard any instruction related to running of layer23, it should be
ccch-app.
I will implore that you first search the mailing list archive for solution
before making a post; by that you can easily find solution to many problems
and learn from others mistakes.
Best of luck.
Sincerely,
Rasak
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
29 May
29 May
6:31 p.m.
Hi all:
thanks for the responds and I appreciate all your support.
@Josh:
I actually started with C155 that is SIM locked by tracphone.
I believe you had the same issueas you've mentioned. My main concern
is not really with the phone but with the PCS1900band because the 850 band
that works for many is not functioning in my area. If there is anyway round
to
make PCS1900 works please let me know.
Presently, to circumvent the SIM lock issue of C155 I opted for Pirelli.
By the way if you have a clue how to break the bond of tracphone on C155
please do not hesitate to let me know. I know someone in the mailing list
was able to overwrite the firmware to support any SIM.
Thanks.
@Harald Welte-3
Thanks for taking time out of your busy schedule to make a response. This
is what I should let you know, this project is something I see in the
category of Linux. I believe with time it will be the most essential tool
for all
telecommunications students in the world. So I strongly thanks every single
programmers that participated in this work for making this possible.
I hope I could do a bit but not all of us are as sound as you guys.
My technical competence is nothing compare to your
recommendation, but I truly appreciate the response.
Thanks so much.
@ Luca
I've been on Pirelli with the same issue for a while. I made some posts
related
to these a long time ago. I eventual switched to C139 which I thought would
work but ended up having similar problem. But recently, I realized that the
issue
might be peculiar to PCS1900 band. Right now, I am sticking with Pirelli to
see
if by chance thing will work out. I've made my observation known to Sylvain
as
a response to my unfix bug post. I hope something can be done.
Thanks to all and I sincerely appreciate all your response.
From,
Rasak
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
7 Jun
7 Jun
1:22 p.m.
Hai list.
I am actually working on a test network which does not have the encryption.
when we sniff the data using the dsp_sniff and receive bursts, if these
bursts contains SMS, they can read and decoded from Wireshark Gsmtap...
right..?
Incase if the bursts contain voice samples we need code from airprobe in
order to convert from bursts to audio.. right.?
thanx
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
1:29 p.m.
when we sniff the data using the dsp_sniff and
receive bursts, if these
bursts contains SMS, they can read and decoded from Wireshark Gsmtap...
right..?
Yes
Incase if the bursts contain voice samples we need
code from airprobe in
order to convert from bursts to audio.. right.?
Yes
Cheers,
Sylvain
8 Jun
8 Jun
2:20 p.m.
The Wireshark is unable to display the voice frames that are carried on TCH.
I am able to see the SI 5 and 6.....
I can see the SMS decoded clearly. but not the voice frames.
How can I also see the voice frames.
thanx
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
2:33 p.m.
Hai......
The Wireshark with GSMtap i use is unable to display the voice frames that
are carried on TCH.
I am able to see the SI 5 and 6..... and all other measurement reports...
between the initiation and termination of a call.....
I can see the SMS decoded clearly..... but not sign voice frames.
Could it be the problem with the Hardware/serial cable i use.....?
How can I also see the voice frames. ?
Thanx
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
2:42 p.m.
Hai all......
The Wireshark with GSMtap i use is unable to display the voice frames that
are carried on TCH.
I am able to see the SI 5 and 6..... and all other measurement reports...
between the initiation and termination of a call.....
I can see the SMS decoded clearly..... but not sign voice frames.
Could it be the problem with the Hardware/serial cable i use.....?
or
Running osmocombb, mobile application and wireshark is not sufficient to get
the voice frames??
How can I also see the voice frames. ?
Thanx
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
11 Jun
11 Jun
10:40 a.m.
Is there any Howto connect OsmocomBB with LCR guide available..?
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
12 Jun
12 Jun
2:02 p.m.
Hello...
I read in the ML that a voice.raw file is generated when we make a call and
when i am using sylvain/testing branch. But i dont get that file.. Where is
it generated.?
The dsp_sniff patch is removed from the source code..
/src/target_dsp/calypso/dsp_sniff.patch...
Is it true.?
Thanx
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
2:08 p.m.
Hi,
I read in the ML that a voice.raw file is generated
when we make a call and
when i am using sylvain/testing branch. But i dont get that file.. Where is
it generated.?
Nowhere, that was some test code from a long time ago.
That was for sending/receiving voice frames when you use the _normal_
firmware to make a phone call. The capability is now merged and can be
used if you use your own custom MNCC control application (i.e. like
the LCR integration).
The dsp_sniff patch is removed from the source code..
/src/target_dsp/calypso/dsp_sniff.patch...
Is it true.?
The sniff patch is only in the burst_ind branch and that branch is
_NOT_ usable as a normal phone (i.e. the 'mobile' application won't do
anything coherent), only the ccch_scan application will do some
sniffing demo (and I emphasize _DEMO_, it's by no mean a complete
tool). See the http://bb.osmocom.org/trac/wiki/Sniffing and the
linked pages for details.
Cheers,
Sylvain
29 Jun
29 Jun
11:35 a.m.
Hello everybody.
I make the LCR integration and encounter this error.
root@cwm-LIFEBOOK-S7110:~/project/lcr-1.10# lcr start
** LCR Version 1.10
000000 DEBUG (in getrulesetbyname() line 1871): ruleset main found.
000000 DEBUG (in mISDNloop_open() line 36): Open external interface of
loopback.
000000 DEBUG (in mISDNport_open() line 2388): Port has 20 b-channels.
000000 DEBUG (in mISDNport_open() line 2409): using 'mISDN_dsp.o' module
000000 TRACE 29.06.12 11:28:12.620 CH: PORT (open) port 1 mode network
channels 20
000000 DEBUG (in gsm_ms_new() line 805): GSM: interface for MS '1
/tmp/osmocom_l2' is created
000000 ERROR (in mncc_socket_retry_cb() line 1101): Could not connect to
MNCC socket /tmp/ms_mncc_1 /tmp/osmocom_l2, retrying in 5 seconds
000000 DEBUG (in mISDNport_open() line 2388): Port has 20 b-channels.
000000 DEBUG (in mISDNport_open() line 2409): using 'mISDN_dsp.o' module
000000 TRACE 29.06.12 11:28:12.621 CH: PORT (open) port 0 mode terminal
channels 20
LCR 1.10 started, waiting for calls...
000000 TRACE 29.06.12 11:28:12.635 --: LCR 1.10 started, waiting for
calls...
000000 DEBUG (in mISDN_upqueue() line 1869): Received MPH_INFORMATION_IND
for port 0 (Ext).
000000 TRACE 29.06.12 11:28:12.635 CH: PH_DEACTIVATE INDICATION U<-N port 0
000000 DEBUG (in mISDN_upqueue() line 1869): Received MPH_INFORMATION_IND
for port 0 (Ext).
000000 DEBUG (in mISDN_upqueue() line 1869): Received MPH_INFORMATION_IND
for port 0 (Ext).
000000 ERROR (in mncc_socket_retry_cb() line 1101): Could not connect to
MNCC socket /tmp/ms_mncc_1 /tmp/osmocom_l2, retrying in 5 seconds
$ lcradmin state
GSM(port 1: mISDN_l1loop.2) NT ptmp use:0 L1 UP
Ext(port 0: mISDN_l1loop.1) TE ptmp use:0 L2 unkn L1 down
can you give some hint where i am going wrong.
thank you
altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
12 Jul
12 Jul
7:10 p.m.
Hello.
What does it mean by starting osmocomBB in an external socket mode. In the
above post I had a problem with linking OS_BB with LCR.
I start OS_BB with the usual command
./osmocon -p /dev/ttyUSB0 -m c123xor
../../target/firmware/board/compal_e88/loader.compalram.bin
and on starting LCR it says
000000 ERROR (in mncc_socket_retry_cb() line 1101): Could not connect to
MNCC socket /tmp/ms_mncc_1 /tmp/osmocom_l2, retrying in 5 seconds
I read in one of openBSC mailing lists that starting osmo_nitb with -m is
needed to connect it to LCR.
And in the command above -m is already there. Is it the same.?
How would the command be then to launch the OS_BB firmware so as to connect
it to OS_BB.
Kindly give me some hint..
regards
Altaf
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
12 Jun
12 Jun
2:15 p.m.
voice.raw is generated by l1ctl.c (without the dsp_sniff patch).
perhaps u missed that code :
http://cgit.osmocom.org/cgit/osmocom-bb/commit/?h=sylvain/testing&id=60…
http://cgit.osmocom.org/cgit/osmocom-bb/commit/?h=sylvain/testing&id=60…
--
View this message in context:
http://baseband-devel.722152.n3.nabble.com/Osmocom-bb-Making-a-call-tp39972…
Sent from the baseband-devel mailing list archive at Nabble.com.
2:18 p.m.
voice.raw is generated by l1ctl.c (without the
dsp_sniff patch).
perhaps u missed that code :
http://cgit.osmocom.org/cgit/osmocom-bb/commit/?h=sylvain/testing&id=60…
That code doesn't exist anymore, in any branch.
13 Jun
13 Jun
1:44 p.m.
New subject: SIM driver question
Hi.
Is there any reason why in the sim_handler() function, in
case SIM_STATE_TX_DATA:
if (!txDoneFlag)
break; /* wait until data is transmitted */
/* Disable all interrupt driven functions */
writew(0xFF, REG_SIM_MASKIT);
/* Ignore waiting char for RUN GSM ALGORITHM */
/* TODO: implement proper handling of the "Procedure Bytes"
than this is no longer needed */
if(sim_data[1] == 0x88)
sim_ignore_waiting_char = 1;
sim_state = SIM_STATE_RX_STATUS;
calypso_sim_receive(response + length + 1, 2);
break;
we do "calypso_sim_receive(response + length + 1, 2);" instead of
"calypso_sim_receive(response + 1, 2);".
Seems an unnecessary overhead sending back some junk chars there. Or I'm missing
something?
Cheers,
Mihai.
15 Jun
15 Jun
9:08 a.m.
New subject: SIM driver question
eisencah eisenach wrote:
Hi.
Is there any reason why in the sim_handler() function, in
case SIM_STATE_TX_DATA:
if (!txDoneFlag)
break; /* wait until data is transmitted */
/* Disable all interrupt driven functions */
writew(0xFF, REG_SIM_MASKIT);
/* Ignore waiting char for RUN GSM ALGORITHM */
/* TODO: implement proper handling of the "Procedure Bytes"
than this is no longer needed */
if(sim_data[1] == 0x88)
sim_ignore_waiting_char = 1;
sim_state = SIM_STATE_RX_STATUS;
calypso_sim_receive(response + length + 1, 2);
break;
we do "calypso_sim_receive(response + length + 1, 2);" instead of
"calypso_sim_receive(response + 1, 2);".
Seems an unnecessary overhead sending back some junk chars there. Or
I'm missing something?
Cheers,
Mihai.
hi mihai,
iirc, there is a reason for that. the response is allocated with length
+ 1 + 2. at the end of the response string, there are the status bytes,
so "length + 1" is added, so the status will appear at the end of the
response message. the upper layer always reads the status from the last
two bytes. if you would remove the length, the status would be at the
wrong place.
regards,
andreas
21 May
21 May
10:32 p.m.
Hi Rasak,
On Mon, May 21, 2012 at 10:16:39AM -0700, rola wrote:
I stay in US where GSM band is a bit different from
the rest of the World
and as well the phone rf radio in some cases differ. The bands around me are
850 and PCS1900. My SIM career uses PCS1900. Also Motorola c123 with the
radio band serving my area is hard to come by. So I guess, that is where my
predicament lies. Hopefully I might get help eventually.
you could always use a european band version and do the filter re-work.
After that, the phone should work in all bands, as there are no band
filters anymore. Of course the phone will be sensitive to out-of-band
interference from other strong transmitters, but apart from that it
should solve the difficulty obtaining US-band versions of the phone.
--
- 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)
10:37 p.m.
Hi all,
I would also suggest the Pirelli DP-l10 since it works on PCS too (IIRC).
Cheers,
Luca
I stay in US
where GSM band is a bit different from the rest of the World
and as well the phone rf radio in some cases differ. The bands around me are
850 and PCS1900. My SIM career uses PCS1900. Also Motorola c123 with the
radio band serving my area is hard to come by. So I guess, that is where my
predicament lies. Hopefully I might get help eventually.
you could always use a european band version and do the filter re-work.
After that, the phone should work in all bands, as there are no band
filters anymore. Of course the phone will be sensitive to out-of-band
interference from other strong transmitters, but apart from that it
should solve the difficulty obtaining US-band versions of the phone.
4365
days inactive
4370
days old
baseband-devel@lists.osmocom.org
26 comments
10 participants
participants (10)
-
Altaf -
Andreas Eversberg -
eisencah eisenach -
Harald Welte -
Jonas Heinrich -
Joshua Pereyda -
lonelysurfer -
Luca Bongiorni -
rola -
Sylvain Munaut