Messages

1

YateBTS / YateBTS GPRS not working with USRP2

« on: April 03, 2017, 04:52:58 AM »

Hi,

I have setup YateBTS on PC, with Ubuntu 16.04 and NI-USRP 2922. Unfortunately GPRS isn't working. Sometimes G signs appears showing GPRS is available but when i browse, it is gone. The logs are given below. Kindly tell me what can be cause of this issue and how to fix it?

The yate,log is here

http://pastebin.ca/3790877

While ggsn.log is this

 15:35:14.9:Initializing Mini GGSN Mon Apr  3 15:35:14 2017

 15:35:14.9:GGSN logging to file ggsn.log
 15:35:14.9:GGSN Configuration:
 15:35:14.9:  GGSN.MS.IP.Base=192.168.99.1
 15:35:14.9:  GGSN.MS.IP.MaxCount=254
 15:35:14.9:  GGSN.MS.IP.Route=192.168.99.0/24
 15:35:14.9:  GGSN.IP.MaxPacketSize=1520
 15:35:14.9:  GGSN.IP.ReuseTimeout=180
 15:35:14.9:  GGSN.Firewall.Enable=0
 15:35:14.9:  GGSN.IP.TossDuplicatePackets=1
 15:35:14.9:GGSN: DNS servers: 8.8.8.8 0.0.0.0
 15:35:14.9:ip link set sgsntun up
 15:35:15.2:ip route add to 192.168.99.0/24 dev sgsntun
 15:35:15.4:SGSN:service loop policy=0 priority=0
 15:35:15.4:SGSN:service loop policy=0 priority=0
 15:50:57.4:SGSN:Received GPRS SuspensionRequest for tlli=0xc286c8cf

2

YateBTS / how to send sms outside the yate network

« on: March 17, 2017, 03:38:14 AM »

Hi,

I have setup yatebts, internal network is working great. Now i want to send sms to phones connected to external gsm network.
I have a goip. How I can achieve this in yatebts. Kindly guide.

Thanks in advance,
Regards,
Abdullah

3

YateBTS / Re: GPRS : cannot find pdp context

« on: March 01, 2017, 05:07:02 AM »

My phone is not doing anything and ggsn.log are appending this frequently..
12:36:52.7:SGSN:Received GPRS SuspensionRequest for tlli=0x855ab328

4

YateBTS / Re: GPRS : cannot find pdp context

« on: March 01, 2017, 04:40:33 AM »

Hi,

Thanks for answering again.

But my phone isn't doing any activity like that. It is idle, and i am waiting for GPRS sign to come but no use.  The logs
cannot find PDP context for incoming packet for IP keep on appending... 

Any guidance will be appreciated

5

YateBTS / Re: GPRS : cannot find pdp context

« on: March 01, 2017, 02:20:36 AM »

Thanks for replying. Here are the logs.

GGSN.log

12:35:15.9:Initializing Mini GGSN Wed Mar  1 12:35:15 2017
 12:35:15.9:GGSN logging to file ggsn.log
 12:35:15.9:GGSN Configuration:
 12:35:15.9:  GGSN.MS.IP.Base=192.168.99.1
 12:35:15.9:  GGSN.MS.IP.MaxCount=254
 12:35:15.9:  GGSN.MS.IP.Route=192.168.99.0/24
 12:35:15.9:  GGSN.IP.MaxPacketSize=1520
 12:35:15.9:  GGSN.IP.ReuseTimeout=180
 12:35:15.9:  GGSN.Firewall.Enable=0
 12:35:15.9:  GGSN.IP.TossDuplicatePackets=1
 12:35:15.9:GGSN: DNS servers: 8.8.8.8 0.0.0.0
 12:35:15.9:ip link set sgsntun up
 12:35:16.2:ip route add to 192.168.99.0/24 dev sgsntun
 12:35:16.4:SGSN:service loop policy=0 priority=0
 12:35:16.4:SGSN:service loop policy=0 priority=0
 12:36:52.7:SGSN:Received GPRS SuspensionRequest for tlli=0x855ab328
 12:37:35.5:ggsn: received proto=icmp 84 byte packet from 192.168.10.13 to 192.168.99.1 at  12:37:35.5
 12:37:35.5:ggsn: error: cannot find PDP context for incoming packet for IP dstaddr=192.168.99.1
 12:37:36.5:ggsn: received proto=icmp 84 byte packet from 192.168.10.13 to 192.168.99.1 at  12:37:36.5
 12:37:36.5:ggsn: error: cannot find PDP context for incoming packet for IP dstaddr=192.168.99.1
 12:37:37.5:ggsn: received proto=icmp 84 byte packet from 192.168.10.13 to 192.168.99.1 at  12:37:37.5
 12:37:37.5:ggsn: error: cannot find PDP context for incoming packet for IP dstaddr=192.168.99.1
 12:37:38.5:ggsn: received proto=icmp 84 byte packet from 192.168.10.13 to 192.168.99.1 at  12:37:38.5
 12:37:38.5:ggsn: error: cannot find PDP context for incoming packet for IP dstaddr=192.168.99.1
 12:37:39.5:ggsn: received proto=icmp 84 byte packet from 192.168.10.13 to 192.168.99.1 at  12:37:39.5
 12:37:39.5:ggsn: error: cannot find PDP context for incoming packet for IP dstaddr=192.168.99.1

yate.log
http://pastebin.ca/3774387

6

YateBTS / yatebts not starting properly

« on: February 28, 2017, 04:30:12 AM »

Hi,

I am trying to start yatebts (with usrp) after setting it up using official wiki, but it is giving a strange error. On another system i repeated the same steps and it is working fine there. Kindly tell me what is the cause and how to deal with it


ALERT 140148530104128 15:23:04.1 TRXManager.cpp:603:getFactoryCalibration: READFACTORY failed with status 1
2017-02-28_15:23:04.118358 <mbts:WARN> TRXManager.cpp:603:getFactoryCalibration: READFACTORY failed with status 1
2017-02-28_15:23:04.133261 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.133925 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.133982 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.134012 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.134038 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.134064 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.135809 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.135863 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.136981 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.137911 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.138987 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.139031 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.139398 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.139457 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.139835 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.139885 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.139977 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.140021 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.140416 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.140485 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.140681 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.140841 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.141009 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.141358 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.141538 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.141723 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.141915 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.142250 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.142431 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T1
2017-02-28_15:23:04.142615 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.142807 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.143141 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.143357 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.143541 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T2
2017-02-28_15:23:04.143758 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.146229 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.146376 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.146436 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.146489 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T3
2017-02-28_15:23:04.146542 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.146593 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.146651 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.146704 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.146755 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T4
2017-02-28_15:23:04.148831 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.148932 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.148999 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.149059 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.149113 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T5
2017-02-28_15:23:04.149504 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.149582 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.150064 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.150146 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.150202 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T6
2017-02-28_15:23:04.150804 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.150886 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.151122 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.151195 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.151466 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T7
2017-02-28_15:23:04.154243 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.155256 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.155359 <mbts:MILD> TRXManager.cpp:547:clearHandover: NOHANDOVER failed with status 1
2017-02-28_15:23:04.155425 <mbts:MILD> GSML1FEC.cpp:474:handoverPending: handover clear failed
2017-02-28_15:23:04.940452 <mbts:INFO> Ggsn.cpp:104:sethighpri: SGSN:service loop policy=0 priority=0
2017-02-28_15:23:04.940551 <mbts:INFO> Ggsn.cpp:104:sethighpri: SGSN:service loop policy=0 priority=0
MBTS ready
2017-02-28_15:23:04.940589 <ybts-signalling:INFO> Received [0x12312a0]
-----
Primitive: RadioReady


Thanks.

7

YateBTS / GPRS : cannot find pdp context

« on: February 28, 2017, 12:47:54 AM »

Hi,

I am setting up YateBTS GPRS, it shows data or G sign on mobile sometimes but othertimes it doesn't work.  Call works fine.
Log shows following error.

017-02-27_22:41:39.758056 <mbts:MILD> miniggsn.cpp:381:miniggsn_handle_read: ggsn: error: cannot find PDP context for incoming packet for IP dstaddr=192.168.99.1
2017-02-27_22:41:40.760288 <mbts:MILD> miniggsn.cpp:381:miniggsn_handle_read: ggsn: error: cannot find PDP context for incoming packet for IP dstaddr=192.168.99.1

What can be wrong?

8

Installation from packets/SVN/.exe/AppStore / Setting up YateBTS with NI USRP 2922

« on: February 27, 2017, 12:37:33 AM »

Hi everyone,

I want to test YateBTS GPRS feature with NI USRP 2922. I know YateBTS doesn't officially support Non BladeRF devices but I want to give it a try and make it work. I want your help in answering these questions.

1. What version should I use exactly for bringing this setup.
2.  Is there any guide or steps to bring this setup, if yes please share.

Thanks and Regards,