Recent Posts

Pages: 1 2 [3] 4 5 ... 10
Yate users hangout place / Re: [ YATE-6.0.1 ] CDRBuild Initialize & Finalize Issue
« Last post by marian on July 09, 2018, 01:36:17 AM »
You are internally connect 2 call legs with different billing id.

cdrcombine does its job based on billid parameter.
cdrcombine is not designed to track channels with different billid.
This would require a custom logic.

You may store individual CDRs into database and run whatever logic you need for billing.

Keep in mind you must make a decision for the following:
A calls B: billid1
C calls D: billid2
You connect C with B !
You must run a complex logic to look at call time, answer time, duration, channel id ...

Bottom line:
- cdrcombine does not replace a charging application
- For custom logic you may need to build your own cdr combiner
Features requests / SIP UPDATE support
« Last post by idelac3 on July 09, 2018, 12:40:55 AM »

I would like to add support for SIP UPDATE message to Yate.

I see in source code, file ysipchan.cpp need additional line;

Code: [Select]
YateSIPEngine::YateSIPEngine(YateSIPEndPoint* ep) :
SIPEngine(s_cfg.getValue("general", "useragent")), m_ep(ep),
m_prack(false), m_info(false), m_foreignAuth(false) {


But I don't know where to put code which will actually update parameters of media in SIP session when UPDATE message arrives.

Any suggestion ?

Yate based projects / Build YateBTS with BladeRF.
« Last post by ryaquaza on July 08, 2018, 11:50:28 PM »
Hello, im newbie.
I am setting up a small phone network for trail testing that need your help. I use BladeRF and YateBTS, I have followed the instructions and installed successfully.
I can connect internal calls to each other, but my problem is that the phone in my local network canít connect to GPRS and I get the notice "GGSN failed to init". The next issue is the "Identity.MCC", "Identity.MNC" and "Identity.ShortName" values,
can I change from the  public release version to the available network in my country? Finally, What should I do if the phone on my local network can call to other phones of any contries on the world.
What are the configuration steps?
Looking forward to hear from you soon. Thank you.

As i seen that some calls are not finalized properly. Mainly when made a transfer the current call to another local user. Please find the status and logs attached here.

YateBTS / Re: YateBTS Web GUI Blank after fresh install and configuration
« Last post by sheperd_ac on July 04, 2018, 07:10:50 PM »

I am getting the same problem. I have done this process several times with fresh installs and am still getting a blank white screen. Any help would be greatly appreciated
Ok then i guess because of my wave channel and configuration mismatch which was mentioned on this previous replies on this thread may cause this issue and these sip channel is not finalized. Let me observe it current status then would come back if any doubt on this.
Yate users hangout place / Re: [ YATE-6.0.1 ] CDRBuild Initialize & Finalize Issue
« Last post by marian on July 04, 2018, 07:18:40 AM »
If you ever made an utility channel sending a call.cdr this may affect cdr combiner: the utility channel will never send a chan.hangup wich would finalize its cdr.
The result will be the entry in cdrcombiner will remain forever: remember that cdr combiner will keep a record as long as at least one leg is not finalized.
See this is my cdrcombine status , as per this status there are 3 active channel but there is no active channel at the moment.

Code: [Select]

For ex : sip/5951 is shows as active but channel/call closed days before. there is no chan.hangup for this channel. As per your previous reply i thought if channel connected to another channel then it won't terminate, so in that case how to identify the original status of those non-terminated channel to terminate forcefully.

Simply expecting there is no mismatch on channel/cdr status.

As i hope you understand my issue now ?
Yate users hangout place / Re: [ YATE-6.0.1 ] CDRBuild Initialize & Finalize Issue
« Last post by marian on July 04, 2018, 12:53:44 AM »
1. Each channel will send a chan.connected message when internally connected to a new peer channel.
2. What do you mean by 'unused' channel?

You should not need to automate hangup: I suppose the user (human) calling/called party will hangup.
Non utility channels will send a chan.hangup when hung up by remote party. This applies for call legs from external protocols (sip ...).

Maybe you should describe what are you trying to achieve.
But my problem is

  • How to identify when channel is connected to another one.
  • How to identify new channel originally hangup , so that i can hangup old channel as well or forcefully emit the cdr finalize

Is there any special emit message on these cases, so that i can drop old un-used channel. Because as i need to automate the hangup unused channel.
Pages: 1 2 [3] 4 5 ... 10