Arya,

it means you have a routing error in the script - you need to debug your script to see where the routing logic is broken - try using xlog() messages to see the execution path of your script.

I cannot help you with more than this.

regards, bogdan

Arya wrote:

any idea how I can fix the problem?

On 9/11/07, *Arya* <arya6000@gmail.com mailto:arya6000@gmail.com> wrote:

I used ngrep but it just shows that the massage keeps bouncing
server to client, and eventually it says massage too big


On 9/11/07, * Bogdan-Andrei Iancu* < bogdan@voice-system.ro
<mailto:bogdan@voice-system.ro>> wrote:

    Hi,

    use ngrep or tcpdump to get a network trace from the proxy
    server, on
    the loopback interface.

    Regards,
    Bogdan

    Arya wrote:
    > Can you tell me how I can trace it? could this be an issue
    with my
    > router? its the Linksys Wr54G and its set on DMZ to the server
    >
    > On 9/10/07, *Bogdan-Andrei Iancu * <bogdan@voice-system.ro
    <mailto:bogdan@voice-system.ro>
    > <mailto: bogdan@voice-system.ro
    <mailto:bogdan@voice-system.ro>>> wrote:
    >
    >     Hi Arya,
    >
    >     I suspect you have a routing problem that cause the
    request to loop on
    >     openser (via loopback interface) - openser keeps sending the
    >     request to
    >     itself. That's why you get a "Message to big" or "too
    many hops"....
    >
    >     run a trace on lo to see if this is what's happening.
    >
    >     regards,
    >     bogdan
    >
    >     Arya wrote:
    >     > Hello everyone
    >     >
    >     > I have a problem connecting to OpenSER from my public IP.
    >     >
    >     > I can connect and make calls to OpenSER inside my LAN
    but when I
    >     > connect from outside LAN I get the 513 Massage too big
    massage.
    >     I than
    >     > changed the openSER default config's section that
    checks a message
    >     > size to a bigger number and I got the I get the "483 -
    too many
    >     Hops"
    >     > error.
    >     >
    >     > I changed the config back to default and tested it with
    ngrep and I
    >     > tried connecting to the server from a server in another
    state.
    >     >
    >     > The SIP server is on 192.168.1.109
    <http://192.168.1.109> <http://192.168.1.109
    <http://192.168.1.109>>
    >     <http://192.168.1.109> and the
    >     > computer trying to connect is on 192.168.1.100
    <http://192.168.1.100>
    >     < http://192.168.1.100> <http://192.168.1.100 <
    http://192.168.1.100>>
    >     >
    >     >  And ngrep gave me these massages: