Hi Chris,
Please make sure that on your reply route x you call rtpproxy_answer()
method.
Regards,
Razvan Crainea
OpenSIPS Developer
On 17.06.2011 20:18, Chris Martineau wrote:
Hi,
On further investigation it would seem that the 183 and 200oks are not being updated by
rtpproxy with the
Hello Brett,
You are right, this was a bug, and I just commited a fix on trunk. Until
now, the reply handler only considered internal OpenSIPS timeouts, and
disregarded explicit 408 replies. Please update and let me know if it is ok.
Regards,
--
Vlad Paiu
OpenSIPS Developer
On
Hello,
This is really bad, seems like a memory corruption problem. It would be
a great deal of help if you would follow the steps here [1] and reply
when the problem reappears.
Regards,
--
Vlad Paiu
OpenSIPS Developer
[1] http://www.opensips.org/Resources/DocsTsMem
On 06/17/2011 09:36
Hi,
This all works fine when not using the invite auth with everything
routing through the correct reply route for 183/200 responses (which
contain the correct rtpproxy_answer setups).
Regards
Chris
-Original Message-
From: users-boun...@lists.opensips.org
Hi Chris,
You will only need to call rtpproxy_offer() for the authenticated INVITE
and register the onreply route that calls rtpproxy_answer() only for
these INVITEs.
Regards,
Razvan Crainea
OpenSIPS Developer
On 20.06.2011 12:04, Chris Martineau wrote:
Hi,
This all works fine when not
Hi,
Figured it out, the order in the failure route was calling
unforce_rtpproxy before the 407 check.
Thanks for your help.
Regards
Chris
-Original Message-
From: users-boun...@lists.opensips.org
[mailto:users-boun...@lists.opensips.org] On Behalf Of Razvan Crainea
Sent: 20 June 2011
Hi all,
It is viable solution to use 30(1|2|5) redirect for REGISTER sip messages ?
Thanks,
Dani
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Hi Duane,
Sure looks like a Bria problem.. If it sends publishes with status closed,
the presence server doesn't have what else to do but to believe that is the
real state that it wants to publish. Maybe something in Bria's configuration
leads to this...
Regards,
Anca Vamanu
On Mon, Jun 20,
Anca,
Doing some more testing it looks like the Bria client is sending PUBLISH
messages and they are open. Only when they bria client is shut down is the
record in the presentity table set to closed. Then when the Bria client is
turned on again a new PUBLISH is sent and entered into the
Anca,
Please ignore. This is a Bria issue it appears. It is true that initially
when you first log in with a Bria client it sends a Publish message and has
statusbasicclosed/basic/status
in the message. I was doing an NGREP and after that message is received if
you wait a little while
10 matches
Mail list logo