On Fri, May 8, 2009 at 10:04 AM, [email protected] <[email protected]> wrote: > On Thu, 2009-05-07 at 12:58 -0400, M. Ranganathan wrote: >> On Thu, May 7, 2009 at 8:43 AM, [email protected] <[email protected]> >> wrote: >> > Hi, >> > first i want to thank you for reply. >> > >> > I tried with this experiment, but i got the same result. >> > >> > I will attach sipxbridge.xml and natraversalrules.xml files from this >> > experiment and also the error part from sipxbridge.log. >> > >> > I just cannot understand why this happen. >> > >> >> >> Your system appears to be misconfigured. >> >> 1. Your nattraversalrules has mediarelaynativeaddress : 212.227.52.184 >> >> This address is publicly routable. >> >> If you are behind NAT then why are you putting a pulicly routable >> address as your native adderss? Please put your private address there. >> If you are not behind NAT do not check the box for behind NAT. >> >> Your mediarelay native addresss should be your private address where >> your media relay is running. >> There is an http server running there for handling xml rpc requests. >> Sipxbridge will send xml rpc requests there. >> >> >> 2. What addresses does asgard.iguanait.com resolve to? Do a dig on >> that and see. Perhaps you would want to set things up in a VM. >> >> I am afraid I dont know how else to help you further here. Something >> is not resolved correctly. I strongly suspect a DNS configuration >> issue. Run wireshark and see where the XML RPC request from sipxbridge >> is realy going. >> >> >> Ranga > > Hi, > > is it possible the problem to come from provider dhcp configurations? > > when i Configuration tests, all tests to hostname included are with > status "success", but the rest of tests "DHCP Test, DHCP (Option 120 > Test), DNS Test, NTP Test, TFTP Test, FTP Test and HTTP Test) return > this message: > > Missing mandatory DHCP configuration parameters. > The DHCP server responded with an IP address assignment but did not > include one of the mandatory network configuration parameters. Please > see the test log for further details. > * Hide details > Starting DHCP server test. > Sending DHCPDISCOVER request. > Multiple responses. Server: 87.106.240.250 > Multiple responses. Server: 87.106.240.249 > DHCPOFFER responce received. > Message Type: DHCPOFFER > Server Identifier: 10.0.0.1 > Lease Time: 360 > Subnet Mask: 255.128.0.0 > DNS Server: 10.0.0.1 > Domain Name: test > > Sending DHCPREQUEST for: 10.0.248.217 > Multiple responses. Server: 87.106.240.249 > Multiple responses. Server: 87.106.240.250 > DHCPACK responce received. > Message Type: DHCPACK > Server Identifier: 10.0.0.1 > Lease Time: 360 > Subnet Mask: 255.128.0.0 > Domain Name: test > DNS Server: 10.0.0.1 > Missing ROUTER option from DHCPACK. > Missing NTP SERVER option from DHCPACK. > Missing TFTP SERVER option from DHCPACK. > > All of them are in state "warning". Is it possible this misconfiguration to > be the problem for sipxbridge? >
I do not believe this to be the cause of the issue you are seeing. It would be worthwhile to run wireshark on the machine to make sure that the SSL handshake is actually happening between sipxbridge and sipxrelay and not some other host. I have never seen this error happen so I dont know what to make of it. Once this has been verified, please send me the wireshark capture of the handshake that is failing. Perhaps I can see something there. Thanks Ranga > > > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
