Re: [Serusers] t_relay results in 483 error

Thank you for reply. It is still not working correctly Im afraid. I have added the lines : alias= xxx.xxx.xxx.xxx (being the public address of my ser server) alias =127.0.0.1 at the start of the config file and added if (uri==myself) { bla } in the middle of my config. Other than that my config is just the default one. As I mentioned previously I have both user agents and ser on public addresses. There is no nat or even authentication in the current setup. It is the simplest scenario, they are all connected via a hub and all have public addresses. A sniff of the eth0 i/f of ser revealed: an invite going from UA1 to SER. A 100 trying message sent back to UA1. Then a 483 too many hops message sent from ser to UA1. A sniff of the loopback i/f revealed an invite message sent from ser address to ser address repeatedly. Any further ideas? Thank you, Pat. --- Marian Dumitru <marian.dumitru(a)voice-sistem.ro> wrote: >Hi Pat, > >Most sure "uri==myself" doesn't match for your RURI >domain. Be sure SER >consider as served domain the RURI domain. At >startup you see the >listing of all served domains by SER. If you want to >add some more, use >the alias config option: > alias=some.new.domain > >Best regards, >Marian > >pat newham wrote: > >>Hello, >> >>I am new to this list and SEr and am trying a very >>simple scenario. I would like to establish a call >>using SER via two grandstream BT100's(UA1 and > >UA2). > >>The two agent and SER are all on public addresses. > >The > >>two agents register with SER ok. However when I > >try to > >>ring UA2 from UA1, I get a 483 error. I know that > >this > >>mean there are too many hops. My config is > >practically > >>the same as the basic (i.e. standard)configuration >>file (except for authorization and I have added a > >line > >>including an alias equal to the public address of >>ser....the "if (uri==myself)" statement is correct > >I > >>think...I checked). >> >>I checked the loopback address as suggested in the >>archives and can see that the invite is repeatedly >>sent to ser itself and 100 trying messages are > >sent to > >>ser itself, therefore the max forwards value value >>must be reached and this is why the error occurs. >> >>I note that when I comment out all the t_relay()'s > >in > >>ser.cfg, the error doesnt occur however the invite >>from UA1 reached ser and thats it.(i.e. its not >>forwarded)...Any help would be greatly > >appreciated(I > >>run the most stable version of ser released i.e >>0.8.14) >> >>Regards, >>Pat. >>