Hi ,
So, is the problem solved (by your findings in the UAS side) ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 24.08.2015 18:25, Nabeel wrote:
I just discovered that the SIP client logs show an error message only
on the recipient side, not on the caller's side. I missed this
previously because the caller's side log does not show any error:
java.lang.Exception: No DNS SRV or A results found for:
162.242.153.259 (IP address of OpenSIPS server).
I have the SRV records set on the actual hostname/domain, but it seems
to be looking for SRV at the actual IP address itself.
On 21 August 2015 at 17:57, Nabeel <[email protected]
<mailto:[email protected]>> wrote:
The log doesn't show any errors when the Timeout occurs, it only
shows this:
opensips[1842]: ACC: call missed:
timestamp=1440174643;method=INVITE;from_tag=z9hG4bK04147190;to_tag=;[email protected]
<mailto:[email protected]>;code=408;reason=Request
Timeout
This seems to occur sporadically; some calls connect without
problem but others don't; so perhaps it is a genuine timeout...
maybe it simply longer to connect on some calls?
On 21 August 2015 at 17:46, Nabeel <[email protected]
<mailto:[email protected]>> wrote:
Sorry to bring this up again, but I still get the 408 Request
Timeout on some calls.
Isn't there just a way to increase the request timeout limit?
Here is the trace:
http://pastebin.com/jvCPGYDu
There is even an ACK in the trace after the request timeout
message, but the call doesn't connect.
On 7 August 2015 at 18:10, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Indeed,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 07.08.2015 20:08, Nabeel wrote:
You mean like this, right?
if (is_method("REGISTER"))
{
if ( 0 ) setflag(TCP_PERSISTENT);
setbflag(SIP_PING_FLAG);
if (!save("location"))
sl_reply_error();
exit;
}
On 7 August 2015 at 17:52, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hi Nabeel,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 07.08.2015 19:39, Nabeel wrote:
[........]
Bogdan,
Regarding UDP, I realised that the UDP port could
not be in LISTEN state and this was probably
preventing my server from fully opening that port.
Running nmap on that port showed result
"open|filtered", unlike with TCP which showed fully
open. I am not running any firewalls on my server,
so this seems to be the default behaviour of my network.
A bidirectional traffic through the NAT will keep the
NAT pinhole open, while a unidirectional one may not.
This is the advantage of the SIP pinging versus
simple UDP pinging.
I would like to clarify one thing. You mentioned
adding setbflag(SIP_PING_FLAG) before doing save(),
but in my config file I don't see save() anywhere,
there is only this line: "if (!save("location"))".
Where exactly do I add this line?
exactly.
Regards,
Bogdan
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
