17 Aug
2006
17 Aug
'06
5:38 a.m.
hi all,
I'm running two openser instances accessing one central MySQL database
using the usrloc db-only mode. Now I'm getting warnings in the log like
WARNING:usrloc:get_all_db_ucontacts: non-local socket
<udp:xxx.xxx.xxx.xxx:5060>...ignoring
Although this is only a 'warning' level message, I'm a little concerned
what effects this could have. Does anybody know what the 'socket' field
in the location table is actually good for?
thanks,
Christian
17 Aug
17 Aug
9:20 a.m.
Hi Christian,
Am 17.08.2006 um 03:38 schrieb Christian Schlatter:
hi all,
I'm running two openser instances accessing one central MySQL
database using the usrloc db-only mode. Now I'm getting warnings in
the log like
WARNING:usrloc:get_all_db_ucontacts: non-local socket
<udp:xxx.xxx.xxx.xxx:5060>...ignoring
Try setting mhomed=1 in the OpenSER Config, otherwise the Packet will
be ignored.
Although this is only a 'warning' level
message, I'm a little
concerned what effects this could have. Does anybody know what the
'socket' field in the location table is actually good for?
Dunno what it's good for, but after i've set mhomed=1 my two OpenSER
are working and accessing the same Database.
--
Mit freundlichen Grüßen / Kind regards
Dominik Bay
Cablesurf Technik
18 Aug
18 Aug
4:13 a.m.
Dominik Bay wrote:
...
Thanks, Dominik, that made the log warnings go away. I have to dig a bit
more in the source code to find out what this setting actually does.
Right now I can't figure out why it suppresses the log warnings. I'll
post my findings to the list.
Thanks again,
Christian
I'm
running two openser instances accessing one central MySQL database
using the usrloc db-only mode. Now I'm getting warnings in the log like
WARNING:usrloc:get_all_db_ucontacts: non-local socket
<udp:xxx.xxx.xxx.xxx:5060>...ignoring
Try setting mhomed=1 in the OpenSER Config, otherwise the Packet will be
ignored.
6659
days inactive
6660
days old
2 comments
2 participants
participants (2)
-
Christian Schlatter -
Dominik Bay