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] 4 5 ... 34
31
Yate users hangout place / Re: JSON Parser help
« on: November 02, 2018, 01:10:16 AM »
JSON parser is implemented in libyatescript.
You may link your module with it.
Take a look at modules/javascript.cpp on usage.

32
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: November 02, 2018, 01:07:50 AM »
Why would you want to masquerade a message when you already have the channel in hand?
chan.masquerade will be handled by your Driver anyway.
Don't forget to put channel in message's user data.

33
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 30, 2018, 04:48:17 AM »
Sorry, forget about it: missed the part the problem was solved!

34
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 29, 2018, 01:21:56 AM »
Can you please dump a log with an outgoing call?
Just to compare the IPs

35
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 25, 2018, 12:31:29 AM »
2018-10-20_16:58:01.025520 <yrtp:INFO> Guessed local IP '192.168.91.52' for remote '212.9.44.38'
2018-10-20_16:58:01.025980 <yrtp:INFO> Session 'yrtp/1476115015' 0x67b9d8 bound to 192.168.91.52:17442 +RTCP [0x686470]
2018-10-20_16:58:01.035580 <sip:INFO> 'udp:0.0.0.0:5060' sending code 200 0x5d8938 to 217.10.79.9:5060 [0x5d2a98]
------
SIP/2.0 200 OK
...
o=yate 1540047481 1540047481 IN IP4 109.41.64.217
c=IN IP4 109.41.64.217

This shows local RTP addr is different (configured or detected).
May be a NAT issue.
Can you sahre your configuration: ysipchan.conf, yrtpchan.conf, accfile.conf?
If yes you should remove private data (password, username ...)

36
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 24, 2018, 06:00:53 AM »
For calling destructor see response on irc channel.
chan.hangup vever terminates a call leg: it's a notification sent by a call leg that protocol (external) call was terminated.
Use call.drop message to terminate a call leg.

37
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 24, 2018, 03:14:20 AM »
That's it!
For safety you should always check pointers (dd)

38
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 24, 2018, 12:55:42 AM »
Please read https://docs.yate.ro/wiki/Chan.locate
Why do you think that locating a Channel implies building a new one?
You are searching for an item to check if it still exists and obtain some data from it

39
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 24, 2018, 12:33:37 AM »
When you are handling (parking) an incoming call you known its id.
When you are executing an outbound call you have the outgoing call id in call.execute when message returns from dispatch.
Just remember them.
You may track them as needed.

You may use chan.locate to obtain channel pointer.
You may obtain billid using API. See Channel documentation.

40
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 24, 2018, 12:04:44 AM »
Please specify your intention.
What is the working case?
What parameter are you talking about and where do you want to store them?
Remember: chan.connected is automatically sent by a Channel when connected to another one.

41
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 23, 2018, 11:42:45 PM »
I don't understand.
If you are speaking about matching call leg id you may always retrieve a channel in driver list. See Driver class documentation.
There is no memory leak in message handlers: the Engine will remove them on shutdown.
You may track them (keep a pointer) and remove from Engine when necessary.

42
Yate users hangout place / Re: No Ringtone Custom Queue In Handle
« on: October 23, 2018, 12:02:19 AM »
Some notes:
- Delete message after dispatch: memory leak
- Don't install a handler for each call in queue: install a module global one
- msg.getParam(YSTRING("id"))->c_str(): not a good idea if the 'id' parameter is missing this will lead to segfault

What is wrong:
You execute queue chan to tone. This will play ring in queue chan
When you attach queue chan to incoming call you the tone chan will be destroyed: not connected

To play ring you must use chan.attach to set tone source in desired call leg (in queue chan).
You may use the API (CallEndpoint::connect()) instead of call.connect message. Usual procedure of executing a call in a driver:
QueueInChannel* c = new QueueInChannel(dest,msg,false);
c->initChan();
DO_SETUP (attach tone source) ...
if (SETUP_OK) {
    CallEndpoint* ch = YOBJECT(CallEndpoint,msg.userData());
    if (ch && c->connect(ch,msg.getValue(YSTRING("reason")))) {
   c->callConnect(msg);
   msg.setParam("peerid",c->id());
   msg.setParam("targetid",c->id());
   c->deref();
   return true;
    }
}
CLEANUP ....
c->deref();
return false;

43
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 19, 2018, 06:49:13 AM »
The log contains more incoming calls.
Please specify which one is the one to track and what it's suppose to happen

44
Other Yate server issues / Re: Problem: one-way audio connection
« on: October 18, 2018, 11:54:44 PM »
Please attach a log with an incoming call containing SIP signaling and internal message
Please raise the debug level
Connect to yate using telnet and type the following commands:
debug sip level 10
sniffer on





45
Yate bugs / Re: YateBTS freezes randomly
« on: October 18, 2018, 11:50:43 PM »
Please attach more log before heartbeat timeout.

Pages: 1 2 [3] 4 5 ... 34