Recent Posts

1

Yate users hangout place / Re: docs.yate.ro - broken links!

« Last post by hecatae on July 20, 2023, 06:59:06 AM »

Latest updated Yate can be found here:
https://github.com/yatevoip 6.4.1
It looks like yate.null.ro no longer exists which makes everything harder to work with 

2

Yate bugs / Unable to start SCTP listener

« Last post by Anton on July 20, 2023, 02:20:19 AM »

None of these examples start a SCTP listener:
https://docs.yate.ro/wiki/Configure_M2UA
https://docs.yate.ro/wiki/Configure_M3UA
https://docs.yate.ro/wiki/Miscellaneous_configurations

For example:

sigtransport.conf
-------------------
[sctp-gw]
type=sctp
stream=true
local=127.0.0.1:2904
endpoint=false <-- not affected!

ysigchan.conf
-------------------
[m3ua-gw]
type=ss7-m3ua-gateway
sig=sctp-gw

It does not start sctp listener:

#lsmod|grep sctp
sctp                  278528  2
libcrc32c              16384  1 sctp

# cat /proc/net/sctp/eps
 ENDPT     SOCK   STY SST HBKT LPORT   UID INODE LADDRS

# netstat -pnla
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1783/sshd                   
tcp        0      0 127.0.0.1:5038          0.0.0.0:*               LISTEN      1995/yate


After doing many tests, I made sure that yate successfully creates only m2pa and m3ua-client connections.
Any ideas how to make a m3ua-gateway ?

Best regards, Anton

3

Yate users hangout place / docs.yate.ro - broken links!

« Last post by Anton on July 19, 2023, 06:02:23 AM »

I see a lot of broken links of image files on docs.yate.ro

https://docs.yate.ro/wiki/index.php?title=Special%3AAllPages&from=&to=&namespace=6

4

Other Yate server issues / Re: Different DTMF per leg on same Call

« Last post by rodrigopassos on May 20, 2023, 11:55:00 AM »

Solved!

Code: [Select]

msg["odtmfmethods"]="rfc2833";
msg["tonedetect_in"]="yes";
msg["tonedetect_out"]="yes";


5

Other Yate server issues / Re: Different DTMF per leg on same Call

« Last post by rodrigopassos on May 20, 2023, 07:50:48 AM »

In yate log I could see:
2023-05-20_10:30:36.072021 <sip/1515732:NOTE> Failed to send tones '4' methods=rfc2833 [0x7f847c01fc40]
Returned false 'chan.dtmf' delay=0.003155
  thread=0x28755e0 'Engine Worker'
  data=0x7f874c0dced0
  retval='(null)'
  param['id'] = 'sip/1515731'
  param['text'] = '4'
  param['detected'] = 'inband'
  param['handlers'] = 'sip:10,pbxassist:15,conf:75,sip:100,dumb:100,callfork:100,filetransfer:100,wave:100,iax:100,jingle:100,analog:100,mgcpgw:100,sig:100,yrtp:150'
  param['sequence'] = '1'
  param['duplicate'] = 'false'
  param['module'] = 'sip'
  param['status'] = 'answered'
  param['address'] = '10.11.255.249:64989'
  param['targetid'] = 'sip/1515732'
  param['billid'] = '1677205349-772582'
  param['peerid'] = 'sip/1515732'
  param['lastpeerid'] = 'sip/1515732'
  param['answered'] = 'true'
  param['direction'] = 'incoming'
  param['domain'] = '10.11.255.131'
  param['callid'] = 'sip/R3ArPBnexQwoArpH35rEcA../7665b20a/1797993596'

6

Other Yate server issues / Re: Different DTMF per leg on same Call

« Last post by rodrigopassos on May 20, 2023, 06:07:44 AM »

Only to clarify, this about dtmf transcoding.
Br,

Rodrigo

7

Other Yate server issues / Different DTMF per leg on same Call

« Last post by rodrigopassos on May 12, 2023, 08:39:36 AM »

Hi everyone, we have an yate server, and have two clients running with different DTMF types. A side A uses Inband, and side B uses RFC 2833 because the type os your cpe. Side B have a IVR, and when Side A calls to B, Yate need to offer RFC2833 because the limitantion of this IVR Server. Yate, is a B2BUA server on this scenario. Could Yate support  different DTMF Types for each call leg? Receive from A inband and send to B RFC2833? Today, we can't see it woking correctly. Inband clients work only Inband and RFC with RFC. Anyone could help about this scenario?

BR,
Rodrigo Passos

8

Other Yate server issues / Re: DataTranslator::attachChain [0xb6aa6d70] (null)->[0xb69d5020] alaw not possible

« Last post by Barney on April 10, 2023, 03:32:33 PM »

Mea culpa. The error is based on a configuration error. Sorry, it's my fault.

9

Other Yate server issues / Yate-Error when SIP port other than 5060

« Last post by Barney on April 10, 2023, 03:29:48 PM »

I've installed yate 6.4.0-1-2 on an OpenWRT router. My current configuration: 4 VoIP accounts with 2 VoIP provider (yate connects as client), within my home network there are 2 IP phones with 5 extensions (they connect to yate as server). This configuration works flawlessly with 5060 as yate's SIP port (default).

Because I watched several connects to my router's port 5060 from IPs, which do not belong to my VoIP providers, I decided to change yate's SIP port from 5060 to 4711. Therefore I added the line 'port=4711' in ysipchan.conf within the [general] section and restarted yate.

Outgoing calls are okay, but not incoming calls. When I fork an incoming call to 2 or more extensions, yate fails to establish a connection to these extensions.

I turned on the sniffer and noticed, that yate propagates port 5060 and not 4711. The client acknowledges the request at port 5060, but yate is listing on port 4711. Therefore the fork fails with a timeout.

Following a snippet of my sniffer logs (yate listens for SIP traffic on 172.19.50.1:4711, my VoIP provider listens for SIP traffic on 195.185.37.60:5060, the incoming call should be forked to extension 12 and 22):

Sniffed 'call.cdr' time=1681154255.687560 age=0.001121 (broadcast)
  thread=0xb6952550 'Engine Worker'
  data=0
  retval='(null)'
  param['operation'] = 'combined'
  param['billid'] = '1681148041-3'
  param['time'] = '1681154248'
  param['chan'] = 'sip/6'
  param['runid'] = '1681148041'
  param['duration'] = '8'
  param['billtime'] = '0'
  param['ringtime'] = '0'
  param['status'] = 'accepted'
  param['external'] = '0471123456789'
  param['cdrwrite'] = 'true'
  param['address'] = '195.185.37.60:5060'
  param['caller'] = '0471123456789'
  param['called'] = '0049471198765432'
  param['username'] = '0049471198765432'
  param['reason'] = 'Service Unavailable'
  param['out_leg.time'] = '1681154248'
  param['out_leg.chan'] = 'sip/8'
  param['out_leg.duration'] = '8'
  param['out_leg.billtime'] = '0'
  param['out_leg.ringtime'] = '0'
  param['out_leg.status'] = 'outgoing'
  param['out_leg.external'] = '0049471198765432'
  param['out_leg.address'] = '172.19.50.1:5060'
  param['out_leg.caller'] = '0471123456789'
  param['out_leg.called'] = '0049471198765432'
  param['out_leg.username'] = '0049471198765432'
  param['out_leg.calledfull'] = '22'
  param['out_leg.reason'] = 'Request Timeout'
  param['out_leg.1.time'] = '1681154248'
  param['out_leg.1.chan'] = 'sip/7'
  param['out_leg.1.duration'] = '8'
  param['out_leg.1.billtime'] = '0'
  param['out_leg.1.ringtime'] = '0'
  param['out_leg.1.status'] = 'outgoing'
  param['out_leg.1.external'] = '0049471198765432'
  param['out_leg.1.address'] = '172.19.50.1:5060'
  param['out_leg.1.caller'] = '0471123456789'
  param['out_leg.1.called'] = '0049471198765432'
  param['out_leg.1.username'] = '0049471198765432'
  param['out_leg.1.calledfull'] = '12'
  param['out_leg.1.reason'] = 'Request Timeout'
Returned false 'call.cdr' delay=0.003338 (broadcast)
  thread=0xb6952550 'Engine Worker'
  data=0
  retval='(null)'
  param['operation'] = 'combined'
  param['billid'] = '1681148041-3'
  param['time'] = '1681154248'
  param['chan'] = 'sip/6'
  param['runid'] = '1681148041'
  param['duration'] = '8'
  param['billtime'] = '0'
  param['ringtime'] = '0'
  param['status'] = 'accepted'
  param['external'] = '0471123456789'
  param['cdrwrite'] = 'true'
  param['address'] = '195.185.37.60:5060'
  param['caller'] = '0471123456789'
  param['called'] = '0049471198765432'
  param['username'] = '0049471198765432'
  param['reason'] = 'Service Unavailable'
  param['out_leg.time'] = '1681154248'
  param['out_leg.chan'] = 'sip/8'
  param['out_leg.duration'] = '8'
  param['out_leg.billtime'] = '0'
  param['out_leg.ringtime'] = '0'
  param['out_leg.status'] = 'outgoing'
  param['out_leg.external'] = '0049471198765432'
  param['out_leg.address'] = '172.19.50.1:5060'
  param['out_leg.caller'] = '0471123456789'
  param['out_leg.called'] = '0049471198765432'
  param['out_leg.username'] = '0049471198765432'
  param['out_leg.calledfull'] = '22'
  param['out_leg.reason'] = 'Request Timeout'
  param['out_leg.1.time'] = '1681154248'
  param['out_leg.1.chan'] = 'sip/7'
  param['out_leg.1.duration'] = '8'
  param['out_leg.1.billtime'] = '0'
  param['out_leg.1.ringtime'] = '0'
  param['out_leg.1.status'] = 'outgoing'
  param['out_leg.1.external'] = '0049471198765432'
  param['out_leg.1.address'] = '172.19.50.1:5060'
  param['out_leg.1.caller'] = '0471123456789'
  param['out_leg.1.called'] = '0049471198765432'
  param['out_leg.1.username'] = '0049471198765432'
  param['out_leg.1.calledfull'] = '12'
  param['out_leg.1.reason'] = 'Request Timeout'
  param['handlers'] = 'cdrfile:100,cdrcombine:100'

10

Other Yate server issues / Re: DataTranslator::attachChain [0xb6aa6d70] (null)->[0xb69d5020] alaw not possible

« Last post by Barney on April 02, 2023, 03:31:02 PM »

Thanks for your reply.

I'll check with tcpdump and report back.