Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - marian

Pages: [1] 2 3 ... 34
1
Yate bugs / Re: Routing Area Identification Not Set Correctly
« on: May 24, 2019, 08:09:11 AM »
Bug fixed: it was related to wrong handling MCC/MNC in GPRS AttachAccept

2
YateBTS / Re: yateBTS network operator name of 712712
« on: May 24, 2019, 08:08:24 AM »
Bug fixed: it was related to wrong handling MCC/MNC in GPRS AttachAccept

3
Yate users hangout place / Re: RSC message
« on: May 21, 2019, 11:49:41 PM »
Most probably the circuit is reset due to REL timeout.

4
Hi,

Try to increase the t1 timer value (default is 500ms).
This timer controls various transaction timers including INVITE timeout.

ysipchan.conf:

[general]
t1=600


Marian

5
YateBTS / Re: Yate Failed to open usb Device
« on: February 22, 2019, 12:46:12 AM »
The device with id 2cf0:5250 is not currently detected by bladerf module as supported.

For nonce: you also don't have the bladerf module.
See the log line: Failed to create radio interface: Message not handled.
Most probably it wasn't built at all.

6
Yate bugs / Re: XMPP Support (windows)?
« on: February 20, 2019, 12:37:33 AM »
Seems there is an issue after TLS is started.
There may be a problem with openssl.
Unfortunately this may be investigated only by using a newer version of the library and build yate on your Windows.
I may try a connection to your server if you post here its domain name.

7
Yate bugs / Re: XMPP Support (windows)?
« on: February 14, 2019, 12:37:52 AM »
Please select Settings -> Debug window
Make sure the 'Debug Here' and 'JABBER' options are checked.
Try to connect.
Post here the contents of the output.

8
Windows / Re: Disable external ip detection
« on: January 31, 2019, 01:36:04 AM »
Linux YateClient accounts file is:
/home/<username>/.yate/client_accounts.conf

9
Yate users hangout place / Re: RTP Over TCP
« on: December 21, 2018, 02:19:02 AM »
No

10
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: December 18, 2018, 12:38:02 AM »
Most probably call.ringing is not forwarded on incoming call leg.

11
YateBTS / Re: YateBTS USRP support
« on: December 14, 2018, 12:49:15 AM »
The new transceiver is using separate module for radio interface.
Currently only bladeRF is supported.

12
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: December 14, 2018, 12:47:22 AM »
Message* m = new Message("chan.masquerade");
....
Engine::dispatch(m);

Engine::dispatch() don't release the object.
Dispatch is assuming you need data on return!
You must delete it after dispatch or call Engine::enqueue()

13
Other Yate server issues / Re: send keepalives only during SIP calls
« on: December 10, 2018, 02:54:28 AM »
Custom parameters configured in cdrbuild.conf and set via copyparams in call.execute will be available in all call.cdr messages related a given call leg.

You must track the number of calls related to a given parameter (line ?)
call.cdr with operation=initialize. Increase counter. Start keep alive if counter=1
call.cdr with operation=finalize. Decrease counter. Stop keep alive if counter=0

14
Yate users hangout place / Re: Custom API - NamedList
« on: December 10, 2018, 02:08:18 AM »
You should take a look at
CdrBuilder class
and
CdrBuilder::update(const Message& msg ...) method.

15
Other Yate server issues / Re: send keepalives only during SIP calls
« on: December 10, 2018, 01:15:58 AM »
You may set the 'keepalive' parameter if want to change the interval (value in seconds).
See:
https://docs.yate.ro/wiki/Accfile

In an external or javascript module you may track call.cdr messages with operation=initialize/finalize.
Track channels belonging to your line. You don't need to logout the line. Just send same parameters as login with changed keepalive
The line parameter can be added to CDR.
See:
https://docs.yate.ro/wiki/CDR_Build_Module
https://docs.yate.ro/wiki/How_to_add_custom_parameters_in_CDR_from_routing

If your last phrase means you want to have some parameters set in outbound/inbound calls using a line you may set them.
All line parameters starting with 'out:' prefix will be set for outbound call legs using them (prefix stripped).
Same for 'inb:' parameters for inbound calls.

Pages: [1] 2 3 ... 34