Hi Raymondin your scenario it's not useful to replicate the socket, since there is no shared IP between your servers. you may try to play at replication with the "received" value (the address where the request was received from) to make one server to point to the other for replicated registrations.
regards, bogdan Raymond Chen wrote:
Hi Bogdan, So we still can't solve the NAT binding problem in the current replicated design? Any other solutions to this ? Thanks Ray -----Original Message-----From: Bogdan-Andrei Iancu [mailto:[EMAIL PROTECTED] Sent: 2005年12月15日 5:26To: Raymond Chen Cc: devel@openser.org Subject: Re: [Devel] multiple replicated servers socket info read error Hi Ray,I guess is a misunderstanding regarding the purpose of this sock_info: the register saves information about the local socket on which the REGISTER was received - it;s useful in multiple interfaces scenario, when to perform proper nat traversal is essential to sent all request from the same interface as register was received on. The NAT bind of the UA will be open to communicate only with that socket/interface.regards, bogdan Raymond Chen wrote:Hi Bogdan, We have setup an environment where UA 1 registered----> openser 1 replicate ----> openser 2. We want to use UA 2 which registered toopenser2 to call UA 1, there is no respond from UA 1, which means the invite message did not get through the UA1 router. We can get through the routerif UA 2 is registered to Openser 1.We thought we can get around the problem by replicate the openser 1 sock_info to openser 2, so when UA 2 calls to UA1 through openser 2, itwillroute back to openser 1 and in turn get pass the router and to UA 1. I am not sure this is the right logic to solve the NAT issue though. Thanks Ray -----Original Message-----From: Bogdan-Andrei Iancu [mailto:[EMAIL PROTECTED] Sent: 2005年12月15日 0:34To: Raymond Chen Cc: devel@openser.org Subject: Re: [Devel] multiple replicated servers socket info read error Hi Raymond, Raymond Chen wrote:here is more a matter of logic. If you replicate the sock_info (the socket the request was received on) to a server which doesn't use that socket, it's really useless - it will not be able to use it to send any requests by using that socket.Hi Bogdan,My bad, I thought make install will overwrite the old modules. Now I got the CVS compiled and installed. Old error message has gone away, but another error occurs in debug:..... 0(21224) grep_sock_info - checking if port 5060 matches port 50600(21224) ERROR:registrar:get_sock_hdr: non-local socket <udp:xxx.xxx.xxx.xxx:5060>0(21224) parse_headers: flags=4000000 0(21224) parse_headers: flags=80000 ....I thought the replicated proxy should store the remote sock_info and should not return the as non-local socket. Correct me if I am wrong about this replicate feature.If you describe what you are trying to achieve, I will be able to understand better you scenario.regards, bogdanThanks Ray -----Original Message----- From: Bogdan-Andrei Iancu [mailto:[EMAIL PROTECTED] Sent: 2005年12月13日 21:40 To: Raymond Chen Cc: devel@openser.org Subject: Re: [Devel] multiple replicated servers socket info read error Hi Raymond, the problem was fixed on CVS. Please give it a try. thanks for report, bogdan Bogdan-Andrei Iancu wrote:Hi Raymond,I guess is not a config issue, but it might be the result of thelatest work on it - proto was added couple of days ago. Please postthe replicated request and I will take a look to see where is theproblem.Regards,BogdanRaymond Chen wrote:Dear all,We’ve setup a multiple replicated servers scenarios, openser 1replicate to openser 2.Openser 1:……add_sock_hdr("Sock-Info");t_replicate(“openser 2”);…….Openser 2:…….modparam("registrar", "sock_flag", 18)modparam("registrar", "sock_hdr_name", "Sock-Info")……setflag(18);………We are expecting the socket info will be stored by register insteadof the received socket info. But from debug we have the followingerror message.0(2599) ERROR: parse_phostport: bad port number inudp:xxx.xxx.xxxx.xxx:50600(2599) ERROR:registrar:get_sock_hdr: bad socket<udp:xxx.xxx.xxx.xxx:5060> in0(2599) parse_headers: flags=40000000(2599) build_contact(): Created Contact HF: Contact:<sip:[EMAIL PROTECTED]:51018>;expires=300Any idea? Is it the configuration we did was wrong?ThanksRay------------------------------------------------------------------------_______________________________________________Devel mailing listDevel@openser.orghttp://openser.org/cgi-bin/mailman/listinfo/devel_______________________________________________Devel mailing listDevel@openser.orghttp://openser.org/cgi-bin/mailman/listinfo/devel
_______________________________________________ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel