4 Feb
2006
4 Feb
'06
5:55 p.m.
Hi,
I just wonder about one thing.
I had my dispatcher proxy layer working before the last cvs update.
Now I see in my logs:
BUG: get_send_socket: unknown proto 0
Feb 4 16:50:04 proxy-01 /usr/sbin/openser[8192]: forward_req: ERROR:
cannot forward to af 2, proto 0 no corresponding listening socket
I just wonder what these messages mean.
I'm forwarding messages to another OpenSER.....
br hw
--
Helge Waastad
Senior Konsulent
Systemavdelingen
Smartnet
6 Feb
6 Feb
12:39 p.m.
Hello,
On 02/04/06 17:55, Helge Waastad wrote:
Hi,
I just wonder about one thing.
I had my dispatcher proxy layer working before the last cvs update.
Now I see in my logs:
BUG: get_send_socket: unknown proto 0
Feb 4 16:50:04 proxy-01 /usr/sbin/openser[8192]: forward_req: ERROR:
cannot forward to af 2, proto 0 no corresponding listening socket
what is the function you use to relay the message? The problem could be
due to last changes for NAPTR and we like to trace it.
Cheers,
Daniel
I just wonder what these messages mean.
I'm forwarding messages to another OpenSER.....
br hw
1:27 p.m.
Hi,
I'm using:
forward(uri:host, uri:port)
(BTW, I though there migh be a problem with my NAPTR dns settings so I
removed them from my domain....so now only DNS SRV records are
avaliable..)
br hw
man, 06,.02.2006 kl. 12.39 +0200, skrev Daniel-Constantin Mierla:
--
Helge Waastad
Senior Konsulent
Systemavdelingen
Smartnet
2:03 p.m.
Hi Helge,
indeed there was a bug in the sip resolver related to setting the
default proto and port in unable to determine them. Ex: if host is IP,
no NAPTR/SRV is done, but the default proto and port must be set if not
specified.
please update form CVS and let me know if there are any more issues.
Thanks for report,
Bogdan
Helge Waastad wrote:
Hi,
I'm using:
forward(uri:host, uri:port)
(BTW, I though there migh be a problem with my NAPTR dns settings so I
removed them from my domain....so now only DNS SRV records are
avaliable..)
br hw
man, 06,.02.2006 kl. 12.39 +0200, skrev Daniel-Constantin Mierla:
8 Feb
8 Feb
11:58 a.m.
Hi,
that made it work.
thank's.
regards, hw
man, 06,.02.2006 kl. 14.03 +0200, skrev Bogdan-Andrei Iancu:
Hi Helge,
indeed there was a bug in the sip resolver related to setting the
default proto and port in unable to determine them. Ex: if host is IP,
no NAPTR/SRV is done, but the default proto and port must be set if not
specified.
please update form CVS and let me know if there are any more issues.
Thanks for report,
Bogdan
Helge Waastad wrote:
--
Helge Waastad
Senior Konsulent
Systemavdelingen
Smartnet
Hi,
I'm using:
forward(uri:host, uri:port)
(BTW, I though there migh be a problem with my NAPTR dns settings so I
removed them from my domain....so now only DNS SRV records are
avaliable..)
br hw
man, 06,.02.2006 kl. 12.39 +0200, skrev Daniel-Constantin Mierla:
6864
days inactive
6868
days old
4 comments
3 participants
participants (3)
-
Bogdan-Andrei Iancu -
Daniel-Constantin Mierla -
Helge Waastad