Recent Posts

11

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

12

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.

13

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'

14

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.

15

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

« Last post by takeshi on March 31, 2023, 05:09:18 PM »

I would say the VoIP provider is offering/answering with an unknown payload type.
Do the SIP messages exchanged with the VoIP provider show up in the logs?
If not, are you able to get a SIP capture (tcpdump, sngrep etc)?

16

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

« Last post by Barney on March 30, 2023, 01:42:33 PM »

I've installed YATE 6.4.0-1-2 on an OpenWRT router. There are 2 IP phones connected to the router.

A call from one IP phone to the other (no VoIP provider involved) works as expected: caller and callee can hear and talk to each other.

But an external call via the VoIP provider fails: the caller hears the ringing tone forever; the callee hears the ringing tone, answers but hears nothing.

The YATE log (debug level 9) shows the following entries:

2023-03-30_21:03:24.663961 <INFO> DataTranslator::attachChain [0xb6aa6d70] '(null)' -> [0xb69d5020] 'alaw' not possible
2023-03-30_21:03:24.664134 <INFO> DataTranslator::attachChain [0xb6aa6c70] 'alaw' -> [0xb69d52c0] '(null)' not possible


I have no idea, where to look in the conf files. Can anybody give a useful hint? If you need more information, let me know.

Thanks for reading and have a nice day.

17

Yate bugs / Duplicate billid

« Last post by rukavinamilan on December 07, 2022, 01:31:42 AM »

We started to get duplicate billid for different calls which happen in like same 10s. Can you please help what could be the reason. We depend a lot on this id and it produces a lot of mess. CDRs are stored in postgres.

Thanks

18

Yate users hangout place / Re: logging call details in yate

« Last post by takeshi on August 29, 2022, 08:07:05 PM »

You should set up a CDR module:
  https://docs.yate.ro/wiki/Call_Detail_Records_Modules

19

Yate users hangout place / logging call details in yate

« Last post by manit123 on August 25, 2022, 11:10:29 PM »

I am using
$yate --version
Yate 6.4.1 devel1 r6556
on
$ lsb_release  -a
No LSB modules are available.
Distributor ID:   Ubuntu
Description:   Ubuntu 20.04.3 LTS
Release:   20.04
Codename:   focal

I want to obtain following information
which number called which number at what time and what was the call duration if call was picked

Please provide useful links in this regard .

Thanks.

20

Other Yate server issues / Re: No audio

« Last post by argentum on February 14, 2022, 07:56:58 AM »

yate receives rtp from profider and local user and do not transmit to remote side.
config almost default.