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
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.

2
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.

3
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.

4
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

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

6
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.

7
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.

8
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()

9
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

10
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.

11
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.

12
Yate users hangout place / Re: Custom API - NamedList
« on: December 10, 2018, 12:40:20 AM »
You may take a look at modules/cdrbuild.cpp
It tracks call legs and update parameters associated with them.

13
Other Yate server issues / Re: send keepalives only during SIP calls
« on: December 04, 2018, 04:18:24 AM »
There is no keep alive for calls using UDP transport.
For UDP keep alive is only used by registered lines.

If you want to implement a feature to send keep alive for active calls you may
1. Add variable to hold keep alive time
2. Re-implement  'virtual void checkTimers(Message& msg, const Time& tmr)' in YateSIPConnection
    Send keep alive: see YateSIPLine::keepalive() for sending keep alive packet
    Don't forget to call Channel::checkTimers() !!!


14
Yate users hangout place / Re: Custom API - NamedList
« on: November 29, 2018, 05:34:17 AM »
Currently there is no mechanism to set arbitrary parameters to messages sent by Channel.

This is a custom application.
What I understand is you want something cdrbuild module is already doing: store configured parameters and put them in call.cdr messages.

You must write your own application (module) who must:
1. track call legs from creation to destruction
2. store associated parameters
3. intercept channel messages with message handlers at high priority and fill them with stored parameters

15
Yate users hangout place / Re: Custom API - NamedList
« on: November 29, 2018, 02:21:16 AM »
You can use a NamedList to manage your own parameters but you won't be able to access them from other modules like regexroute.

Adding:
NamedList* nl = new NamedList("");
// ... fill 'nl' params
// Add it to a Message
msg.setParam(new NamedPointer("customdataList",nl));

Retrieve from Message:

NamedList* nl = YOBJECT(NamedList,msg.getParam("customdataList"));
if (nl) {
    // Handle it
}
else {
   // Parameter not present or not a NamedList object
}

Pages: [1] 2 3 ... 34