Bodin Bruno writes:
> Sending Access-Accept of id 127 to 127.0.0.1 port 32773
> Reply-Message = "Authorized"
if openser receives this and still reports failure, i would suspect your
radiusclient library, since the result testing code in the module is
exactly same as in other radius modules. or perhaps your openser does
no get the reply at all.
-- juha
Dear all,
Does the Open SER support the PRACK-UPDATE method and
if yes in which version?
Thanks in advance.
Best regards,
K.N.
____________________________________________________________________________________
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
http://videogames.yahoo.com/platform?platform=120121
Hi Everyone,
Does anyone know if t_uac_dlg will still be available in OpenSER
1.2.0., either from openserctl or xmlrpc?
We'd like to use this function to send fake byes when billing records
are left open, that is unless there is a better way to acomplish this.
Thoughts?
Regards,
Daryl
Hello,
I am testing 1.2.0-pre8-notls version running with mediaproxy and I
have noticed someting very strange: When a client is behind nat it
never connects to the mediaproxy for the RTP exchange.
I have checked the sip traces, the media IP translation is done
correctly in the SDP body. My setup has already worked some time ago
(with devel version) and I haven't made big changes since.
Were there changes on the way nat is handled that I have missed ? I
tried to set the "received_avp" and "nat_bflag" params but this don't
help.
If somebody have a hint for me, I would be glad to hear it.
Thank you !
--
Regards,
-vma
.
For various (and quite horrible) reasons, I need to do the following
a) Wait '2' seconds after I send an INVITE for *any* response
b) Wait '4' seconds after I get a 100 response for a 18x (or higher) response
c) Wait '60' seconds after the 18x for a 18x (or higher) response
Sooo, can I change the timer *during* the transaction? i.e., something like
fr_inv_timer = 2
if (response == 100) {
reset fr_inv_timer to 4 seconds
} elsif (response == 180) {
reset fr_inv_timer to 60
}
Or, is fr_inv_timer fixed once the transaction is setup?
cheers
--
*******************************************
Mahesh Paolini-Subramanya (703) 386-1500 x9100
CTO mahesh(a)aptela.com
Aptela, Inc. http://www.aptela.com
"Aptela: How Business Answers The Call"
*******************************************
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I found out, that when wesip runs and openser was restartet or openser
was started after wesip wesip doesn't do an auto reconnect to openser
when openser' unix socks are available to wesip again. I think it will
give openser/wesip couple more robustnes when there is a kind of ato
reconnect.
regards
helmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF8VOT4tZeNddg3dwRAqqJAJ9Wa/r6trK9tECVC0M+ivHYjGs8IQCeIjZS
Ay+mT46+ZQDp0wj0D4J+h3I=
=KBLt
-----END PGP SIGNATURE-----
Hi,
just wondering about dispatcher failover in 1.2.0
in 1.1.0 i had:
modparam("dispatcher", "list_file", "/etc/openser/dispatcher.list")
modparam("dispatcher", "force_dst", 0)
modparam("dispatcher","flags", 2)
modparam("dispatcher","use_default", 0)
ds_select_dst("1", "0");
and in failure rout checking 408 timeout an using
ds_mark_dst();
ds_next_dst()
What I see is that the "down" proxy is not put as inactive
ERROR:avp:search_first_avp: 0 ID or NULL NAME AVP!
Any clues?
br hw