Messages

16

Yate users hangout place / Re: Billid in call.answered

« on: October 17, 2013, 06:54:07 AM »

Use copy param function. When you use sniffer the copy param should look like this:

Code: [Select]

param['copyparams'] = 'rtp_addr,rtp_port,billid, ANY OTHER parameter'


17

Yate users hangout place / Re: Yate service

« on: October 17, 2013, 06:50:30 AM »

Hi,

yate is fully opensource, there are modules which are not opensource which are mainly related to Enterprise/Carrier solutions.
If you want a simple PBX use Freesentral, which is also opensource and developed by null team. As I know there is no commercial version of Freesentral out there.
We are running yate in productive, with hunderts of concurrent calls, with no problem. So I guess 20 clients are no problem.

You also can use the mail group, the wiki page, irc channel or use the search function of the forum.

18

Yate users hangout place / Re: Extracting Specific data from SIP Message Header (INVITE)

« on: October 17, 2013, 06:16:42 AM »

Hi,
you can access almost any SIP message part. Connect to via telnet to rmanager. Then start debug and sniffer. Now you can see all parameters available.

Code: [Select]

Sniffed 'call.preroute' time=1382008032.149810
  thread=0x7fbc5400b950 'Call Router'
  data=(nil)
  retval='(null)'
  param['id'] = 'sip/521638'
  param['module'] = 'sip'
  param['status'] = 'incoming'
  param['address'] = '10.20.30.40:5061'
  param['billid'] = '1381224392-201494'
  param['answered'] = 'false'
  param['direction'] = 'incoming'
  param['callid'] = 'sip/45d4d208371c11e3b9fc0025907d0298@10.20.30.40/3939619909-3809549367-620821689-2550300048/'
  param['caller'] = '123456789'
  param['called'] = '987654321'
  param['antiloop'] = '19'
  param['ip_host'] = '10.20.30.40'
  param['ip_port'] = '5061'
  param['ip_transport'] = 'UDP'
  param['sip_uri'] = 'sip:987654321@10.50.60.70;user=phone'
  param['sip_from'] = 'sip:123456789@10.20.30.40:5061;user=phone'
  param['sip_to'] = '<sip:987654321@10.50.60.70;user=phone>'
  param['sip_callid'] = '45d4d208371c11e3b9fc0025907d0298@10.20.30.40'
  param['device'] = 'XXXXXX'
  param['sip_contact'] = '<sip:123456789@10.20.30.40:5061;user=phone>'
  param['sip_content-type'] = 'application/sdp'
  param['sip_allow'] = 'ACK, BYE, CANCEL, INFO, INVITE, OPTIONS, REFER, REGISTER, UPDATE'
  param['sip_user-agent'] = 'XXXXXXXXX'
  param['sip_cisco-guid'] = '3089045420-924520931-2583232549-2426535383'
  param['sip_p-asserted-identity'] = '<sip:123456789@10.20.30.40:5061;user=phone>'
  .....

As you see there all delivered parameters accessible.

19

Yate IVR / Javascript High System Load

« on: August 27, 2013, 11:20:34 AM »

Hi,

we are currently testing IVR with javascript. Now that everything works like expected from routing and js perspective, the next problem pops ups. Have a look at the graphs, they show system and yate monitoring for the last 7 Days. As you can see the overall load and the context switches all increase over time, also the total mutex used by yate increase pretty linear. The system has almost no load on it...for the last 7 days there was only about 300 calls to process. So I guess for every call my IVR is loaded but not onloaded correctly, so after 300 calls we have too many mutex open and the system load gets 100%

I'm not sure if my script is the problem or yate.. need some more testing?


 

20

Yate bugs / Re: Yate dead in sipp test

« on: August 17, 2013, 03:40:58 PM »

Hi,

could you post your scenario file for sipp and some yate logs with debugging sip on level 9. We also use sipp to test our yate servers, with success.

21

Yate users hangout place / Re: voicemail phone numbers

« on: August 05, 2013, 05:27:31 PM »

You can find the caller parameter in the cdrs. If you can't find a caller there, then the calling party hasn't transferred one or you may check the incoming signaling from your uplink.
I'm not sure if the caller parameter is saved in the default voicemail.php. You may have a look at http://www.freesentral.com/ it is yate server + web gui, pretty cool.

22

Linux / Re: adding a call

« on: August 05, 2013, 05:19:49 PM »

have look at http://docs.yate.ro/wiki/Conference_room_module

23

Yate bugs / Re: SNMP and Database

« on: July 24, 2013, 01:50:27 PM »

Hi,

oana thx for the patch now ysnmp is working great! But I still have problems with the MIB

I've run smilint on the new MIB and there are some error. smilint has many debug levels as you can see

Code: [Select]

0 Internal error, no recovery possible. Examples are memory allocation failures. Errors of this level usually cause the application to abort.

1 Major SMI/SPPI error, recovery somehow possible but may lead to severe problems. Examples are lexically unexpected characters or unknown keywords. Errors of this kind usually lead to follow-on errors.

2 SMI/SPPI error which is probably tolerated by some implementations. Examples are MIB/PIB modules which mix constructs from different SMI/SPPI versions.

3 SMI/SPPI error which is likely tolerated by many implementations. Examples are misplaced SMIv2 MODULE-IDENTITY invocations or SMIv2 textual conventions derived from other textual conventions.

4 Something which is not strictly an error but which is recommended to be changed. Warnings of this level are usually considered during MIB reviews.

5 Something that is basically correct but might be problematic in certain environments or usage scenarios. Examples are warnings that identifiers only differ in case or that type definitions are not used within the defining module.

6 Messages of this level are auxiliary notices. Examples are messages that point to a previous definition in case of a redefinition.

So up to level 2 all errors are more or less critical for smilint

Code: [Select]

sudo smilint -s -e -l 2 YATE-MIB.original.txt                   
YATE-MIB.original.txt:302: [2] {identifier-redefined} redefinition of identifier `moduleInfo'
YATE-MIB.original.txt:394: [2] {sequence-type-mismatch} type of `callEntryDuration' in sequence and object type definition do not match
YATE-MIB.original.txt:911: [2] {subtype-illegal} subtyping not allowed
YATE-MIB.original.txt:912: [2] {subtype-illegal} subtyping not allowed
YATE-MIB.original.txt:913: [2] {subtype-illegal} subtyping not allowed
YATE-MIB.original.txt:914: [2] {subtype-illegal} subtyping not allowed
YATE-MIB.original.txt:996: [2] {subtype-illegal} subtyping not allowed
YATE-MIB.original.txt:997: [2] {subtype-illegal} subtyping not allowed
YATE-MIB.original.txt:998: [2] {subtype-illegal} subtyping not allowed
YATE-MIB.original.txt:1887: [1] {internal-other} syntax error, unexpected OBJECTS, expecting DESCRIPTION
YATE-MIB.original.txt:1888: [1] {internal-other} syntax error, unexpected DESCRIPTION
YATE-MIB.original.txt:112: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:128: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:263: [2] {row-index-missing} row `moduleEntry' lacks index definition
YATE-MIB.original.txt:329: [2] {row-index-missing} row `activeCallEntry' lacks index definition
YATE-MIB.original.txt:425: [2] {row-index-missing} row `trunkEntry' lacks index definition
YATE-MIB.original.txt:529: [2] {row-index-missing} row `linksetEntry' lacks index definition
YATE-MIB.original.txt:607: [2] {row-index-missing} row `linkEntry' lacks index definition
YATE-MIB.original.txt:693: [2] {row-index-missing} row `interfaceEntry' lacks index definition
YATE-MIB.original.txt:764: [2] {row-index-missing} row `accountEntry' lacks index definition
YATE-MIB.original.txt:870: [2] {row-index-missing} row `qosEntry' lacks index definition
YATE-MIB.original.txt:902: [2] {basetype-unknown} type `ASRData' of node `asrData' does not resolve to a known base type
YATE-MIB.original.txt:987: [2] {basetype-unknown} type `NERData' of node `nerData' does not resolve to a known base type
YATE-MIB.original.txt:1045: [2] {basetype-unknown} type `EndCauseCounters' of node `callEndCauseCounters' does not resolve to a known base type
YATE-MIB.original.txt:921: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:929: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:937: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:946: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:955: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:963: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:971: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:979: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1003: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1011: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1020: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1029: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1037: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1076: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1084: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1092: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1100: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1108: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1116: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1124: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1132: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1140: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1148: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1156: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1164: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1172: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1180: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1188: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1196: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1204: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1212: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1220: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1228: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1259: [2] {row-index-missing} row `databaseEntry' lacks index definition
YATE-MIB.original.txt:1327: [2] {basetype-unknown} type `DatabaseAlarmCounters' of node `databaseAlarmCounters' does not resolve to a known base type
YATE-MIB.original.txt:1383: [2] {basetype-unknown} type `DatabaseThresholds' of node `databaseThresholds' does not resolve to a known base type
YATE-MIB.original.txt:1343: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1351: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1359: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1367: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1375: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1398: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1406: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1414: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1422: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.original.txt:1452: [2] {row-index-missing} row `rtpEntry' lacks index definition
YATE-MIB.original.txt:1276: [2] {type-unknown} unknown type `DatabaseThresholds'

Additional descriptions of some error/warning messages:

Error:       internal-other (level 1)
Message:     %s
Description: An unspecified error occured. Please submit a detailed bug report
             to the libsmi maintainer or the libsmi mailing list at
             <libsmi@ibr.cs.tu-bs.de>.

Error:       subtype-illegal (level 2)
Message:     subtyping not allowed
Description: The types OBJECT IDENTIFIER, IpAddress, Counter32, Counter64,
             and TimeTicks, and any types in a SEQUENCE clause must not be
             sub-typed (RFC 2578, Sections 7.1.12 and 9).

As you can see we have some erros. I guess the errors on level [1] are all related to smilint parsing(and may bee some other snmp agents) and can easy be fixed. This should have no side effects as we just change the order, not any OIDs/Names

Code: [Select]

@@ -1883,8 +1883,8 @@
 genericAlarms OBJECT IDENTIFIER ::= { alarms 7 }
 
 genericAlarm NOTIFICATION-TYPE
- STATUS current
  OBJECTS { alarmSource, alarmLevel, alarmText }
+ STATUS current
  DESCRIPTION
  "A generic YATE alarm."
  ::= { genericAlarms 1 }

Then we have some errors on level [2], most important for smilint is the use of subtypes in SEQUENCE which violates the RFC.
See https://tools.ietf.org/html/rfc2578 on 7.1.12, 9 and 11. This also can bee fixed pretty easy with no side effects and any changes to the OIDs

Code: [Select]

@@ -908,10 +908,10 @@
  ::= { qosEntry 3 }
 
 ASRData ::= SEQUENCE {
- lowASRThreshold INTEGER (-1..100),
- highASRThreshold INTEGER (-1..100),
- currentASR INTEGER (-1..100),
- overallASR INTEGER (-1..100),
+ lowASRThreshold INTEGER,
+ highASRThreshold INTEGER,
+ currentASR INTEGER,
+ overallASR INTEGER,
  currentLowASRAlarmCount Counter32,
  currentHighASRAlarmCount Counter32,
  overallLowASRAlarmCount Counter32,

@@ -993,15 +993,15 @@
  ::= { qosEntry 4 }
 
 NERData ::= SEQUENCE {
- lowNERThreshold INTEGER (-1..100),
- currentNER INTEGER (-1..100),
- overallNER INTEGER (-1..100),
+ lowNERThreshold INTEGER,
+ currentNER INTEGER,
+ overallNER INTEGER,
  currentLowNERAlarmCount Counter32,
  overallLowNERAlarmCount Counter32
 }
 

And there is a type miss-match for callEntryDuration. In the SEQUENCE we have type Counter32, in the key definition we have DisplayString, also in snmp_mib.conf So I've fixed that in the SEQUENCE in DisplayString also.

Code: [Select]

@@ -340,7 +340,7 @@
  callEntryStatus DisplayString,
  callEntryCaller DisplayString,
  callEntryCalled DisplayString,
- callEntryDuration Counter32,
+ callEntryDuration DisplayString,
  callEntryPeerChan DisplayString
 }

And we have moduleInfo defined two times one as a section name and one as a cell, this can also cause errors. I've changed the section name from moduleInfo to moduleInfos

All errors like "{row-index-missing} row `moduleEntry' lacks index definition" are easy to fix as the only need INDEX {...}parameter, no side effects.
Like https://tools.ietf.org/html/rfc2578#section-7.11
Tables Rows:
* moduleEntry
* activeCallEntry
* trunkEntry
* linksetEntry
* linkEntry
* interfaceEntry
* accountEntry
* qosEntry
* databaseEntry
* rtpEntry

This error "[2] {type-unknown} unknown type `DatabaseThresholds'" is because of a copy and past bug I guess
On line 1391 the SEQUENCE DatabaseAlarmCounters should be DatabaseThresholds to match. DatabaseAlarmCounters was defined twice.

After those changes smilint is more friendly

Code: [Select]

sudo smilint -s -e -l 2 YATE-MIB.new.txt
YATE-MIB.new.txt:112: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:128: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:910: [2] {basetype-unknown} type `ASRData' of node `asrData' does not resolve to a known base type
YATE-MIB.new.txt:995: [2] {basetype-unknown} type `NERData' of node `nerData' does not resolve to a known base type
YATE-MIB.new.txt:1053: [2] {basetype-unknown} type `EndCauseCounters' of node `callEndCauseCounters' does not resolve to a known base type
YATE-MIB.new.txt:929: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:937: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:945: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:954: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:963: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:971: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:979: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:987: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1011: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1019: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1028: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1037: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1045: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1084: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1092: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1100: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1108: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1116: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1124: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1132: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1140: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1148: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1156: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1164: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1172: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1180: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1188: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1196: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1204: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1212: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1220: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1228: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1236: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1336: [2] {basetype-unknown} type `DatabaseAlarmCounters' of node `databaseAlarmCounters' does not resolve to a known base type
YATE-MIB.new.txt:1392: [2] {basetype-unknown} type `DatabaseThresholds' of node `databaseThresholds' does not resolve to a known base type
YATE-MIB.new.txt:1352: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1360: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1368: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1376: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1384: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1407: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1415: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1423: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:1431: [2] {parent-scalar} scalar's parent node must be simple node

Ok we still have errors... as I mentioned before nesting SEQUENCES / Tables is wrong.

[11:50pm] vankooch: can a sequence be an element from an other sequence, nested sequence, in a mib file?
[11:50pm] rstory-work: nope.. you use multiple tables, each of which adds and additional index..
[11:51pm] vankooch: so nested tables work?
[11:51pm] rstory-work: no, you can't nest.. you aproximate with multiple tables...
[11:51pm] rstory-work: see http://stackoverflow.com/questions/2510211/snmp-asn-1-mib-definitions-referencing-a-table-within-a-table

Have look at here

So I've removed the nested SEQUENCES and have created child tables instead, this comes along with changes in OIDs and names.

But now we have only two errors left..which is great

Code: [Select]

sudo smilint -s -e -l 2 YATE-MIB.new.txt                   
YATE-MIB.new.txt:112: [2] {parent-scalar} scalar's parent node must be simple node
YATE-MIB.new.txt:128: [2] {parent-scalar} scalar's parent node must be simple node

And this errors are similar to the nested SEQUENCES stuff. It is also wrong to fork OBJECT-TYPE with OBJECT-TYPE. OBJECT-TYPE can only have parents like OBJECT IDENTIFIER. So I have changed that also.

Now we have no error up to level 3....we still have some errors on level 4 and 5 which are mostly related to Conformance Statements
see https://tools.ietf.org/html/rfc2580, but this is an other story

Update 1

Ok I've tried that out... everything works great now, tables, walks, get, get next. I need to check the traps and alarms later

I also would recommend to search and replace all INTERGER with Interger32. INTERGER is snmpv1 and Interger32 is snmpv2, which the mib uses and imports from SNMPv2-SMI.

I've attached some patches. The first one only have the changes which do not affect any OID only one section name moduleInfo -> moduleInfos
The full patches have all changes so far..
There is also a svg with a overview of the fixed mibs... could not create on for the original

Update 2

I've created a simple Zabbix Template for Yate. It works with the fully fixed mib. You just need to import it and assign the {$SNMP_COMMUNITY} macro.
It has most information imported, trap and alarms are missing.

24

Yate based projects / Re: Yate System - Need Advice

« on: June 19, 2013, 06:03:59 AM »

As I know there is only the YateClient GUI and no special GUI for the server. There is  Freesentral a web based software for soho pbx functions based on yate and from the null team.
If you are looking for a wholesale system, then the company I work for has some products.

You can find prebuild debs for ubuntu on launchpad http://yate.null.ro/pmwiki/index.php?n=Main.Download

25

Installation from packets/SVN/.exe/AppStore / MOVED: Yate System - Need Advice

« on: June 19, 2013, 05:57:32 AM »

This topic has been moved to Yate based projects.

http://forum.yate.ro/index.php?topic=177.0

26

Yate based projects / Re: Yate System - Need Advice

« on: June 17, 2013, 06:08:57 AM »

All functions are aval. in yate. Have look at the docs.
There are also ready to use solutions with yate out there.. which have database routing and billing.

27

Installation from packets/SVN/.exe/AppStore / Re: [SOLVED] cannot start yate as service un 12.04 ubuntu (debian).

« on: June 11, 2013, 07:20:05 PM »

I've added a note in the wiki.

28

Installation from packets/SVN/.exe/AppStore / Re: Ubuntu Packages

« on: June 11, 2013, 07:10:23 PM »

Hi,

I'll try to create a raring deb in the next days

Update:

raring support is now in the ppa, let me know if you have any problems

29

Installation from packets/SVN/.exe/AppStore / Re: cannot start yate as service un 12.04 ubuntu (debian).

« on: June 10, 2013, 02:24:14 PM »

Hi,

maybe your init script is not working. Have run make install after compiling? You also can try one of the ppa's which offer yate debs for ubuntu.

You also can try to use a upstart job like this:

Code: [Select]

description "yate upstart job"
version "0.2"
author "null team"
emits voip

start on filesystem
stop on shutdown

expect fork
respawn
respawn limit 10 300
umask 022
oom 0

limit nofile 32768 32768
limit rtprio 0 12
nice -10

pre-start script
if [ ! -d /var/log/yate ]; then
mkdir -p -m0755 /var/log/yate
fi
end script

script
exec /usr/bin/yate -d -vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv -Ddf -l /var/log/yate/messages
end script


30

Yate users hangout place / Re: Send SIP call to gsm mobile

« on: April 24, 2013, 05:40:30 PM »

If no sip client is installed you need to send your sip calls to a sip upstream provider so that they terminate they call for you.