Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
Actually, I am not using defined users. I am using  " .* "  in the regex to allow users to connect to the box and they automatically get numbers assigned to them. Can you please tell me how do I define the outbound rule if should not use the regexroute. Moreover, I am getting 405 "METHOD NOT ALLOWED"  errors.
22
YateBTS / Difference of the USIMS
« Last post by smlee on November 27, 2017, 06:19:08 AM »
I have 2 USIM and 8 USIM.
2 USIM cards was in test phone from the time of receipt.
When i use 2 USIM card at other device(no test phone, embedded device), they work well.
But 8 USIM don't work at other device. They only work at test phone.
How can i use the 8 USIM at other devices?
What is the difference of the USIM?
23
If the Outbound connection is up, then all calls that can't be routed inside the network (defined subscribers phone numbers - msisdns  or their short numbers) will be routed to the outbound connection.

The regexroute is wrong. You should not need to define anything in regexroute to get calls to go to the outbound connection.

Can you post a log with "sniffer on" and "debug sip level 9" from telnet?
http://docs.yate.ro/wiki/Debugging_and,_or_Investigation_of_messages
24
Hello, 

 I have made some progress from this but not completely successful ... Yes I did get the trunk registered in peer as well as registered mode but the problem is I am unable to set routes from inside the Yate network to the PBX server.

    I have edited the regexroute.conf file to enter  a route (which might be wrong)

^.*$=sip/sip:\910501664@192.168.2.1:5060

910501664 is the local Yate number from which I am trying to call to the PBX numbers .. Calls from the PBX to the Yate numbers is successful.. Please help me with this.

Thanks
Anindya

25
Hi.

Did you configure the NiPC  Outbound connection? Please check the status of the registration:
Telnet to yate console and type "status accfile". If outbound connection is up you shoud see: outbound=set_username in below line

yate-sdr@ybts-UNCONFIG> status accfile
name=accfile,type=misc;users=2;outbound=1291121

26
Linux / Re: Unique ringtone device or action - how?
« Last post by marian on November 21, 2017, 02:19:36 AM »
YateClient has no support for separate audio device for incoming call alert.

You may implement some script to track incoming calls and play some alert on a device you want.
Audio device modules are located in modules/client (for various platforms there are alsa/oss (Linux), coreaudio (Mac) and dsound (Windows)).
Your script should track incoming calls, play a sound on a device at your choice and stop it when call is answered.

You may find some documentation at docs.yate.ro
You may want to look at chan.* and call.* messages.
27
Linux / Unique ringtone device or action - how?
« Last post by JohnSuykerbuyk on November 20, 2017, 02:32:40 PM »
Incredibly impressed with all the power that is yate, and yet I seem to be totally humbled by the challenge of having my PC speakers "ring" upon an incoming call while using my USB headset to handle the call audio.

I'm sure there's some module conf file somewhere that will allow the ring tone to be played on one device and the call audio handled by another - but damned if several days of pouring through the threads and google search results turns up anything intelligible to me.

I'm running yate-qt4 version 5.5 on a fully up to date Arch Linux system (as of 20 Nov 2017).  Pulse audio is up and running and I have no problems routing ALL audio through the Plantronics USB headset I use.  However, I never hear an incoming call as the ring tone also goes through the USB headset.

Ideally I'd love to be able to hook an inbound call event to a script or some such to do exactly what I'd like but I would most certainly settle for having the ring sound go out on the loudest device on my system.
28
Linux / Re: bladerf...cant find tower with my mobile device
« Last post by mati335 on November 20, 2017, 01:33:19 PM »
running on ubuntu 16.04
29
Linux / bladerf...cant find tower with my mobile device
« Last post by mati335 on November 20, 2017, 01:23:47 PM »
so i installed everything like this sudo apt-get install gnuradio libboost-all-dev gr-osmosdr gqrx-sdr apache2 -y
sudo add-apt-repository ppa:ondrej/php
sudo apt-get update
sudo apt-get install php5.6 -y
sudo apt-get install subversion make autoconf gcc libusb-1.0-0-dev libgsm1-dev -y
sudo addgroup yate
sudo usermod -a -G yate zab
sudo apt-get install doxygen build-essential -y
cd /usr/src
sudo svn checkout http://voip.null.ro/svn/yate/trunk yate
cd yate
sudo ./autogen.sh ; ./configure --prefix=/usr/local ; make ; make install ; ldconfig
sudo chmod -R a+rw /usr/local/etc/yate
cd ..
sudo svn checkout http://voip.null.ro/svn/yatebts/trunk yatebts
cd yatebts
sudo ./autogen.sh ; ./configure --prefix=/usr/local ; make ; make install ; ldconfig
cd /var/www/html
sudo ln -s /usr/local/share/yate/nipc_web/ nipc
/etc/init.d/apache2 start

and when i run yate -s it shows

root@zab-N55SF:/home/zab# yate -s
Supervisor (13205) is starting, max sanity 5
Yate (13206) is starting Mon Nov 20 21:11:43 2017
Loaded module Conference
Loaded module File Transfer
Loaded module MsgSniffer
Loaded module iLBC - based on iLBC reference library
Loaded module GVoice
Loaded module FileInfo
Loaded module PBX
Loaded module RegexRoute
Loaded module ExtModule
Loaded module GSM - based on libgsm-1.0.10
Loaded module MUX
Loaded module SIP Channel
Loaded module WaveFile
Loaded module iLBC - based on WebRTC iLBC library version 1.1.1
Loaded module CdrCombine
Loaded module DumbChannel
Loaded module RManager
Loaded module YJingle
Loaded module ToneDetector
Loaded module YRTP
Loaded module Call Forker
Loaded module CdrFile
Loaded module Javascript
Loaded module iSAC floating point - based on WebRTC iSAC library version 4.3.0 (SPL version 1.2.0)
Loaded module Call Generator
Loaded module CdrBuild
Loaded module ToneGen
Loaded module YSTUN
Loaded module YSOCKS
Loaded module YIAX
Loaded module Analyzer
Loaded module MOH
Loaded module Event Logs
Loaded module Subscriptions
Loaded module Late Router
Loaded module Call Parking
Loaded module SIP Features
Loaded module Users Management
Loaded module DbWave
Loaded module Radius client
Loaded module SigTransport
Loaded module Heartbeat
Loaded module Queues
Loaded module Clustering
Loaded module YBTS
Loaded module Analog Channel
Loaded module GSM Transceiver
Loaded module CCongestion
Loaded module Queues Notify
Loaded module Register for database
Loaded module Monitoring
Loaded module MGCP-GW
Loaded module Cisco SM
Loaded module Signalling Channel
Loaded module CallCounters
Loaded module MRCP
Loaded module MGCP-CA
Loaded module PBX for database
Loaded module SNMP Agent
Loaded module Registration from file
Loaded module Cpu
Loaded module Cache
Loaded module Accounts from file
Loaded module Presence
Loaded module Analog Detector
Loaded module Jabber Server
Loaded module Jabber Server Features
Loaded module Radio Test
Loaded module DummyRadio
Loaded module BladeRF using libusb 1.0.20.11004 desc='http://libusb.info'
Initializing plugins
Initializing module BladeRF
Initializing module DummyRadio
Initializing module Jabber Server Features
Initializing module Jabber Server
2017-11-20_21:11:43.202106 <jbserverengine:NOTE> Failed to load entity caps from '/usr/local/etc/yate/jabberentitycaps.xml': I/O error 2 'No such file or directory'
2017-11-20_21:11:43.202135 <jbserverengine:NOTE> No domains configured
Initializing module Analog Detector
Initializing module Cpu
2017-11-20_21:11:43.202420 <cpuload:NOTE> Updating CPU core number from 1 to 8
Initializing module MGCP Call Agent
Initializing module Cisco SM
Initializing module Clustering
Initializing module SigTransport
Initializing module DbWave
Initializing module Subscriptions
Initializing module Event Logs
Initializing module YSOCKS
Initializing module Javascript
Initializing module CdrFile
Initializing module MUX
Initializing module Conference
Initializing module File Transfer
Initializing module MsgSniffer
Initializing module GVoice
Initializing module FileInfo
Initializing module PBX
Initializing module RegexRoute
Initializing module ExtModule
Initializing module SIP Channel
Initializing module WaveFile
Initializing module iLBC webrtc
Initializing module CdrCombine
Initializing module DumbChannel
DumbChannel initialized
Initializing module RManager
Initializing module YJingle
2017-11-20_21:11:43.208366 <jingle:NOTE> Module initialized: localip=MISSING jingle_version=1 singletone=true pending_timeout=10000 anonymous_caller=unk_caller codecs=mulaw,alaw
Initializing module ToneDetector
Initializing module YRTP
Initializing module Call Forker
Initializing module iSAC
Initializing module Call Generator
Initializing module CdrBuild
Initializing module ToneGen
Initializing module YSTUN
Initializing module YIAX
Initializing module Analyzer
Initializing module MOH
Initializing module Late Router
Initializing module Call Parking
Initializing module SIP Features
Initializing module Users Management
Initializing module Radius client
2017-11-20_21:11:43.269887 <yradius:NOTE> Local address not set or invalid. Radius functions disabled
Initializing module Queues for database
Initializing module YBTS
Initializing module Analog Channel
Initializing module GSM Transceiver
Initializing module CCongestion
Initializing module Queues Notify
Initializing module Register for database
Initializing module Monitoring
Initializing module MGCP Gateway
Initializing module Signalling Channel
2017-11-20_21:11:43.271820 <sig:NOTE> Section 'tcapuser_test'. Unknown/missing type '(null)'
Initializing module MrcpSpeech
Initializing module PBX for database
Initializing module SNMP Agent
Initializing module Register from file
Initializing module Cache
Initializing module Accounts from file
Initializing module Presence
Initializing module Radio Test
Initialization complete
2017-11-20_21:11:43.277802 <jabber:NOTE> Changing supported compression formats to '(null)' old='zlib'
2017-11-20_21:11:43.277820 <jbserverengine:NOTE> TLS not available for outgoing streams
2017-11-20_21:11:43.277856 <ybts:NOTE> State changed Idle -> Starting restart counter 1/10
2017-11-20_21:11:43.278373 <ybts:NOTE> State changed Starting -> WaitHandshake
MBTS connected to YBTS
Yate-BTS MBTS Component
Copyright 2008, 2009, 2010 Free Software Foundation, Inc.
Copyright 2010 Kestrel Signal Processing, Inc.
Copyright 2011, 2012, 2013 Range Networks, Inc.
Copyright 2013, 2014 Null Team Impex SRL
Copyright 2014 Legba, Inc.
"OpenBTS" is a registered trademark of Range Networks, Inc.

Contributors:
  SC Null Team Impex SRL:
    Paul Chitescu
  Legba, Inc.
    David Burgess
  Range Networks, Inc.:
    David Burgess, Harvind Samra, Donald Kirker, Doug Brown,
    Pat Thompson, Kurtis Heimerl
  Kestrel Signal Processing, Inc.:
    David Burgess, Harvind Samra, Raffi Sevlian, Roshan Baliga
  GNU Radio:
    Johnathan Corgan
  Others:
    Anne Kwong, Jacob Appelbaum, Joshua Lackey, Alon Levy
    Alexander Chemeris, Alberto Escudero-Pascual
Incorporated L/GPL libraries and components:
  libusb, LGPL 2.1, various copyright holders, www.libusb.org
Incorporated BSD/MIT-style libraries and components:
  A5/1 Pedagogical Implementation, Simplified BSD License,
    Copyright 1998-1999 Marc Briceno, Ian Goldberg, and David Wagner
Incorporated public domain libraries and components:
  sqlite3, released to public domain 15 Sept 2001, www.sqlite.org


This program comes with ABSOLUTELY NO WARRANTY.

Use of this software may be subject to other legal restrictions,
including patent licensing and radio spectrum licensing.
All users of this software are expected to comply with applicable
regulations and laws.  See the LEGAL file in the source code for
more information.

Release 6.0.1 formal build date Nov 20 2017 rev656
2017-11-20_21:11:43.285047 <mbts:NOTE> GSMConfig.cpp:80:regenerateBeacon: regenerating system information messages, changemark 1
Starting MBTS...
2017-11-20_21:11:43.285343 <ybts:NOTE> State changed WaitHandshake -> Running
2017-11-20_21:11:43.303888 <NOTE> Failed to open config file '/usr/local/etc/yate/tmsidata.conf', using defaults (2: No such file or directory)
Yate engine is initialized and starting up on zab-N55SF
2017-11-20_21:11:43.643841 <gsmtrx:NOTE> State changed Invalid -> Idle [0x7fd55c0155f0]
2017-11-20_21:11:43.643988 <gsmtrx:NOTE> State changed Idle -> PowerOff [0x7fd55c0155f0]
2017-11-20_21:11:43.666331 <bladerf/1:NOTE> Powered ON the radio [0x7fd55c000eb0]
2017-11-20_21:11:43.668466 <gsmtrx:NOTE> State changed PowerOff -> PowerOn [0x7fd55c0155f0]
2017-11-20_21:11:43.676465 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T1
2017-11-20_21:11:43.678060 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T2
2017-11-20_21:11:43.679181 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T3
2017-11-20_21:11:43.680809 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T4
2017-11-20_21:11:43.682101 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T5
2017-11-20_21:11:43.682763 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T6
2017-11-20_21:11:43.683588 <mbts:NOTE> GSMConfig.cpp:532:createCombinationI: Configuring combination I on C0T7
2017-11-20_21:11:43.937172 <mbts:MILD> iputils.cpp:456:ip_finddns: GGSN: DNS servers: 127.0.1.1 0.0.0.0
RTNETLINK answers: File exists
2017-11-20_21:11:44.205035 <cpuload:NOTE> Updating CPU core number from 1 to 8
MBTS ready
2017-11-20_21:11:44.440644 <ybts:NOTE> State changed Running -> RadioUp
30
Yate users hangout place / Deploy Yate behind AWS
« Last post by ankur on November 17, 2017, 10:01:50 AM »
Hi,
i am deploying yate behind NAT in AWS,
is there a way to specify the public ip of the box in yate config file so that the contact header is set as contact@publicip rather than contact@privateip.
all SIP messages from the box have contact header set as contact@privateip,
this is causing some SIP clients to misbehave
Pages: 1 2 [3] 4 5 ... 10