Recent Posts

Pages: [1] 2 3 ... 10
1
YateBTS / Re: how to send sms outside the yate network
« Last post by Monica Tepelus on March 17, 2017, 05:37:51 AM »
Hi,

You need to connect yatebts to a YateUCN that connects to a SMSC/YateSMSC to could send this over MAP (if you have interconnect) or over SMPP (there are various services).
Yatebts would  be configured in roaming mode.

Another way would be to modify nib/add additional script that would send SMS over SMPP to one of the available services or SIP  to your voip provider (if it offers this service).
2
YateBTS / how to send sms outside the yate network
« Last post by abdullah689 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
Hi,

I suppose you are using nib. Add the subscribers and set the number you want.
4
YateBTS / Re: Phone not registering in network
« Last post by rooby on March 11, 2017, 11:49:22 PM »
Hello,
I think you should try to change the mnc and mcc. In your config I saw that you kept the ones which were there by default. Try to fing the rights ones according toyour country and let's see.
5
YateBTS / How to disable the auto MSISDN or phone number allocation in YateBTS
« Last post by rooby on March 11, 2017, 07:31:38 AM »
Hello everyone,
Is there any way to disable the auto allocation of MSISDN number in yate BTS, as i want to keep the same MSISDN or the real phone number of the MS. Am strugling and always getting a random number for each mobile who join my BTS. If I could keep the real number will be fine.

Please which file should I edit in order to do that or what should be done?

Thank you.
6
YateBTS / Compatibility with or usability of LimeSDR
« Last post by bdheeman on March 09, 2017, 01:50:39 PM »
Hi,

Anyone tested https://en.wikipedia.org/wiki/LimeSDR? I'm not sure, but seems it's UHD compatible and usable with YateBTS https://discourse.myriadrf.org/t/compatibility-with-openbts-yatebts-and-osmobts/333

IMHO, It could, comparatively, be good alternative/choice for low budget projects.
7
YateBTS / Build errors on ARM architecture GCC 6.3.1
« Last post by bdheeman on March 09, 2017, 01:00:05 PM »
Hi,

Today, when attempted to build YateBTS after an 'svn update' at 601 now, for Rasberry Pi 3 Model B running ArchLinux-ARM using GCC/G++ 6.3.1 the build failed with following errors:

Code: [Select]
MAC.cpp: In member function 'GPRS::PDCHL1FEC* GPRS::L2MAC::macPickChannel()':
MAC.cpp:838:28: error: 'ch' cannot appear in a constant-expression
  for (RListIterator<typeof(ch)> itr(macPacchs); itr.next(ch); ) {
                            ^~
MAC.cpp:838:30: error: a function call cannot appear in a constant-expression
  for (RListIterator<typeof(ch)> itr(macPacchs); itr.next(ch); ) {
                              ^
MAC.cpp:838:31: error: template argument 1 is invalid
  for (RListIterator<typeof(ch)> itr(macPacchs); itr.next(ch); ) {
                               ^
MAC.cpp:838:46: error: cannot convert 'GPRS::PDCHL1FECList_t {aka RList<GPRS::PDCHL1FEC*>}' to 'int' in initialization
  for (RListIterator<typeof(ch)> itr(macPacchs); itr.next(ch); ) {
                                              ^
MAC.cpp:838:53: error: request for member 'next' in 'itr', which is of non-class type 'int'
  for (RListIterator<typeof(ch)> itr(macPacchs); itr.next(ch); ) {
                                                     ^~~~
MAC.cpp: At global scope:
MAC.cpp:655:13: warning: 'void GPRS::dumpPdch()' defined but not used [-Wunused-function]
 static void dumpPdch()
             ^~~~~~~~
make[2]: *** [Makefile:122: MAC.o] Error 1
make[2]: Leaving directory '/home/bdheeman/devel/abs/local/yatebts-svn/src/yatebts-svn/mbts/GPRS'
make[1]: *** [Makefile:140: ../GPRS/libGPRS.a] Error 2
make[1]: Leaving directory '/home/bdheeman/devel/abs/local/yatebts-svn/src/yatebts-svn/mbts/apps'
make: *** [Makefile:54: all] Error 2

FYI, I'm forced to override defaults in your Makefile(s), for the reasons of compatibility; the build otherwise was failing a lot and that's how I successfully build Yate and YateBTS a few days ago:

Code: [Select]
export CC="gcc -std=c90 -Wall"
export CXX="g++ -std=c++98 -Wall"
8
Yate server for Google Voice / Re: "Jingle call failed. Incomplete caller"
« Last post by robotwin on March 09, 2017, 09:31:24 AM »
Aha! Thank you for helping me understand that the client and server use the same configuration files if they are in the same directory. That fact was not clearly in the how-to guide. It's easy to make this mistake because the windows installer puts everything in the same directory by default.

It works correctly now that I changed that. Thank you all again.
9
Yate server for Google Voice / Re: "Jingle call failed. Incomplete caller"
« Last post by Ioana Stanciu on March 09, 2017, 09:05:10 AM »
clientlog.txt shows that you are routing in client to Google. See :

Quote
Sniffed 'call.route' time=1488989110.984375
  thread=02FF4A68 'Call Router'
  data=00000000
  retval='(null)'
  param['id'] = 'client/4'
  param['module'] = 'client'
  param['status'] = 'incoming'
  param['billid'] = '1488988375-4'
  param['answered'] = 'false'
  param['direction'] = 'incoming'
  param['called'] = '18005551212'
  param['line'] = 'sip:200@192.168.0.9'
  param['account'] = 'sip:200@192.168.0.9'
Returned true 'call.route' delay=0.000000
  thread=02FF4A68 'Call Router'
  data=00000000
  retval='jingle/18005551212@voice.google.com'
  param['id'] = 'client/4'
  param['module'] = 'client'
  param['status'] = 'incoming'
  param['billid'] = '1488988375-4'
  param['answered'] = 'false'
  param['direction'] = 'incoming'
  param['called'] = '18005551212'
  param['line'] = 'GoogleVoice'
  param['account'] = 'sip:200@192.168.0.9'
  param['handlers'] = 'javascript:15,cdrbuild:50,fileinfo:


So you either modified the configuration for the client. Or the client and server read configuration from the same place.
If you have installed both Yate and YateClient on the same machine, please start one with a different configuration directory. The default one is /etc/yate. Please check the '-c' command line option.

10
Yate server for Google Voice / Re: "Jingle call failed. Incomplete caller"
« Last post by robotwin on March 09, 2017, 08:56:53 AM »
That makes sense and I did follow those instructions. Where in my logs does it show a GV account is configured in the Yate Client?

Here is the SIP entry in regfile.conf:
Code: [Select]
[200]
password=mysecret2

And here is the client setting screenshot:
Pages: [1] 2 3 ... 10