46
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)
For safety you should always check pointers (dd)
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.
47
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
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
48
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.
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.
49
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.
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.
50
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.
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.
51
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;
- 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;
52
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
Please specify which one is the one to track and what it's suppose to happen
53
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
Please raise the debug level
Connect to yate using telnet and type the following commands:
debug sip level 10
sniffer on
54
Yate bugs / Re: YateBTS freezes randomly
« on: October 18, 2018, 11:50:43 PM »
Please attach more log before heartbeat timeout.
55
Yate users hangout place / Re: record files auto deleted
« on: October 11, 2018, 11:48:37 PM »
Yate does not delete any recordings.
Check the location you are saving the files: it may be temporary directory cleaned by the OS or a directory mapped into memory whose contents are lost on reboot.
Check the location you are saving the files: it may be temporary directory cleaned by the OS or a directory mapped into memory whose contents are lost on reboot.
56
Other Yate server issues / Re: Record all call
« on: October 11, 2018, 11:48:26 PM »
Yate does not delete any recordings.
Check the location you are saving the files: it may be temporary directory cleaned by the OS or a directory mapped into memory whose contents are lost on reboot.
Check the location you are saving the files: it may be temporary directory cleaned by the OS or a directory mapped into memory whose contents are lost on reboot.
57
Yate users hangout place / Re: Call Queue Dropping automatically
« on: October 10, 2018, 04:22:25 AM »
Hi,
Remember that maxcall value is expected to be in milliseconds.
There is a very large log.
Maybe you should describe what are you trying to do and what exactly is the issue (which call fails?).
Remember that maxcall value is expected to be in milliseconds.
There is a very large log.
Maybe you should describe what are you trying to do and what exactly is the issue (which call fails?).
58
Yate users hangout place / Re: Audio files as Loop Instead of call ringing
« on: October 02, 2018, 12:07:17 AM »
When a call leg is connected to another one data endpoints are connected to each other.
You have 2 solutions:
- track chan.connected and re-attach the play data source when call leg is connected
- make 2 separate calls and connect to each other when appropriate (you may use chan.connect message for this. See docs.yate.ro)
You have 2 solutions:
- track chan.connected and re-attach the play data source when call leg is connected
- make 2 separate calls and connect to each other when appropriate (you may use chan.connect message for this. See docs.yate.ro)
59
Yate users hangout place / Re: Channel Message Direction Modification
« on: September 25, 2018, 11:57:29 PM »
No.
You may use another parameter that can be updated in cdrbuild.
You may use another parameter that can be updated in cdrbuild.
60
Yate users hangout place / Re: Channel Message Direction Modification
« on: September 25, 2018, 12:31:02 AM »
You are allowing changing this parameter after creation.
Set it to false.
Set it to false.