Messages

436

Other Yate server issues / Re: How can RTP transport directly from client to client?

« on: March 10, 2014, 05:29:41 AM »

In the same way.
The document IS NOT about h.323 to sip interworking, even if the included image shows an example of h.323 to sip call.

437

Other Yate server issues / Re: How can RTP transport directly from client to client?

« on: March 10, 2014, 02:02:58 AM »

See http://docs.yate.ro/wiki/RTP_Forwarding

438

Yate server for Google Voice / Re: Beginner in need of help!

« on: February 28, 2014, 08:22:29 AM »

Hi,
Sorry to be so late, I didn't noticed the new page and didn't saw your post!

The log is showing the call being terminated by yate due to OK timeout.
The jingle channel is responded, yate sends OK on incoming sip and retransmits it.
Finally the call is dropped because OK is not confirmed.

This may indicate network errors.
The caller may be behind a NAT.

439

Other Yate server issues / Re: Parrallel resolving any REGISTER packets

« on: February 03, 2014, 07:42:36 AM »

I don't understand you post. Can you rephrase it?

When you install a message handler you don't return the result to yate engine, you return it to message dispatcher.
In our case the result is returned to sip module.

440

Other Yate server issues / Re: Parrallel resolving any REGISTER packets

« on: January 31, 2014, 03:01:35 AM »

In javascript you can install handlers using a message parameters:

Message.install(func,"user.register",90,"param_name","param_value");

This will install a handler for user.register with priority 90.
The handler will be called only if the message will carry a parameter 'param_name' with value 'param_value'.

You can run 2 scripts, the first may install the handler for, let's say, a parameter instance=1 and the second for instance=2.
From outside, maybe regexroute or another java script you can install a handler for user.register to be handled before the ones with filters.
There you can rotate the instance parameter to distribute the handling.

441

Other Yate server issues / Re: SIP Routing Issue: Call rejected error='noconn' reason='Invalid Address'

« on: January 29, 2014, 01:55:49 AM »

The log is created by passing a -l command line parameter (extra -t will truncate the log file at each start).

Example:
yate -tl c:\yate.log

More at http://docs.yate.ro/wiki/Starting_on_windows

442

Other Yate server issues / Re: SIP Routing Issue: Call rejected error='noconn' reason='Invalid Address'

« on: January 28, 2014, 02:18:39 AM »

Can you post a yate log from startup?
Please start message sniffer also:

yate.conf:

[general]
msgsniff=yes

I would like to see the log when the line is trying to register.

443

Linux / Re: yate won't start

« on: January 27, 2014, 02:00:19 AM »

Does the log file exists?

444

Apple / BSD client / Re: ekiga.net

« on: January 24, 2014, 09:22:15 AM »

Use provider is applied when selected. It is used to fill protocol and other data.
On subsequent account edit the original provider data is ignored: you can change data as you wish.

Maybe you have to set different server/username?

Can you post a log?

445

Linux / Re: yate won't start

« on: January 23, 2014, 02:02:24 AM »

There is no need to paste the output.

I was asking for the log file.
It is created?
If so, can you show it?

446

Other Yate server issues / Re: Parrallel resolving any REGISTER packets

« on: January 23, 2014, 01:59:00 AM »

regRun() is called from regReq() -> sync process and from YateSIPRegister::run() -> async process.

447

Other Yate server issues / Re: Parrallel resolving any REGISTER packets

« on: January 22, 2014, 02:50:27 AM »

I checked again: you can't use php in this way.

The first script will install a handler for user.unregister, the second one will also install a handler for it.
The first handler will be always called by yate engine before the second one.
A second user.unregister message will always wait for the first one to be handled.

If you want to asychronously handle the same message you must:
1. Write a c++ module
2. Use javascript:
- You can set a filter for handled message's parameter
- Each instance will set the filter to a different value
- You can catch the message in regexroute before javascript and rotate the filter parameter value. This way you can distribute the processing. Each script will handle messages one by one
If you want a real multithreaded handling you need a c++ module

448

Other Yate server issues / Re: Parrallel resolving any REGISTER packets

« on: January 22, 2014, 02:25:45 AM »

extmodule will serialize messages for a single script, so, yes, a php script is not multi threaded.

sip will send user.(un)register using a separate thread so the sip module processes register asynchronously.

2 php scripts should process asynchronously.
Can you attach a log to show your issue?
The log should include the messages:
yate.conf:
[general]
msgsniff=yes

449

Other Yate server issues / Re: SIP User=Phone

« on: January 17, 2014, 01:57:25 AM »

You can ask Diana for features.

It is possible to add custom sip headers in REGISTER response:
Just handle user.register message and add them with 'osip_' prefix!

450

Linux / Re: yate won't start

« on: January 17, 2014, 01:51:40 AM »

I didn't expected otherwise.
I just want to see the log content!