Re: [Partysip-dev] Problems getting started

[Aymeric Moizard]

On Fri, 17 Jan 2003, Craig Graham wrote:

> Hi. Thanks for the response.
>
> The config file does have "nat = on" and the if_ext and if_lan lines.
>
> I have added manually my internal and external IP addresses , so near the
> start of the config file the relevant lines are now
>
> serverip = 127.0.0.1, 62.49.23.210, 10.1.1.1

Poorly, partysip guess that the first address shown here is
your public one. Rewrite it to:
serverip = 62.49.23.210, 10.1.1.1, 127.0.0.1

If you don't do that, most old UAs will fail to send SIP responses.

> servername  = gate.twolips-translations.co.uk,
> splosh.twolips-translations.co.uk, twolips-translations.co.uk
> serverport_udp = 5060
>
> However I still get the same failure on trying to start partysip. I
> originally did not have the 127.0.0.1 in there- the error message is the
> same whether I have one, two or three numeric IPs specified.
>
> Do I need to specify IP addresses differently in some way to tell it the
> 10.1.1.1 address refers to eth0 and the 62.49.23.210 address to ppp0?

if_ext and if_lan are just that! if_ext is the external interface (the
ip is found automatically) and if_lan is the lan interface which ip is
also found automatically!

> Is there a relationship between the order of addresses in the serverip
> line and in the servername line- must they correspond?

definitly, see my first comment.
In the servername line, the order is only a matter of efficiency.

> I've attached my most recent partysip.conf file,

serverip is not defined in the one you sent! You MUST define them
because else the proxy will loop if it receive an ip targetting
itself in a route or request-uri!

> in which I've removed all but one of the servername entries. Still
> doesn't work. Is there any way of getting more diagnostic output from
> the osip module to find out WHY it is exiting?

In your case, this won't help because you are failing somewhere where
there is no trace. (even if setting -d8 level)

The best way to debug it:

cd partysip-0.X.X
gdb ./src/.libs/partysip
b psp_core_init
run

and type "next" until one call return an error.

Mainly check the call to:
      if (0 != ppl_dns_get_local_fqdn (&tmp_name, &tmp_ip, &tmp_mask, tmp))
        goto mci_error10;

and check tmp_name.

Are you sure about the interface you specified for if_ext and if_lan?
Aymeric

> --
> Dr. Craig Graham, Software Engineer
> Advanced Analysis and Integration Limited, UK. http://www.aail.co.uk/
>
> ----- Original Message -----
> From: "Aymeric Moizard" <address@hidden>
> To: "This is the partysip mailing list" <address@hidden>
> Sent: Thursday, January 16, 2003 10:50 PM
> Subject: Re: [Partysip-dev] Problems getting started
>
>
> >
> >
> > On Thu, 16 Jan 2003, Craig Graham wrote:
> >
> > > I have a Linux box acting as a NAT gateway for a few Windows PCs. I am
> > > trying to use Messenger to talk to people elsewhere via sip.
> >
> > great!
> >
> > > I've downloaded and installed libosip, partysip and the new version of
> > > iptables and cannot get partysip to start if I have nat=on in the config
> > > file.
> >
> > You need to specify three elements:
> >  nat = on
> >  if_ext    = ppp0
> >  if_lan    = eth0
> >
> > if_ext is your external IP public interface.
> > if_lan is your lan interface.
> >
> > > If I comment out the line or change it to nat=off then the server runs
> > > and Messenger can sign into it but cannot connect offsite. This is the
> > > diagnostic output with nat=on
> > >
> > > address@hidden init.d]# /usr/local/bin/partysip -d6
> > > Server:             WellX Telecom/Partysip/0.5.3
> > > Debug level:        6
> > > Config name:        /usr/local/etc/partysip/partysip.conf
> > > ServerIP:           62.49.23.210
> > > ServerName:         gate.twolips-translations.co.uk,
> > > splosh.twolips-translations.co.uk, twolips-translations.co.uk
> > > ServerRealm:        '"twolips-translations.co.uk"'
> > > Log name:           Standard output
> > > | INFO2 | <../../src/psp_core.c: 307> serverip token 0: '62.49.23.210'
> >
> > at least, you have two interface, your public IP and your lan ip.
> > You have to specify both in the serverip list to avoid issue.
> >
> >
> > > | INFO2 | <../../src/psp_core.c: 262> servername token 0:
> > > 'gate.twolips-translations.co.uk'
> > > | INFO2 | <../../src/psp_core.c: 262> servername token 1:
> > > 'splosh.twolips-translations.co.uk'
> > > | INFO2 | <../../src/psp_core.c: 262> servername token 2:
> > > 'twolips-translations.co.uk'
> > > | INFO2 | <../../src/psp_osip.c: 61> osip module: Exiting!
> > > ERROR: Could not initialize partysip!
> > > | INFO1 | <../../src/main.c: 192> program has terminated.
> > >
> > >
> > > I had some problems compiling; setting the shell variable
> "-DALPHA_FIREWALL"
> > > did not seem to do anything, so I had to manually add it in the
> > > config.status file after running configure and before running make. It
> does
> > > not show up in partysip -V, although it does now show up in
> > > partysip-configure. Here is the relevant output;
> > >
> > > address@hidden init.d]# /usr/local/bin/partysip-config --cflags
> >
> > -I/usr/local/include -g -O2 -DOSIP_MT -D_REENTRANT -D_THREAD_SAFE -DXOPEN_
> SO
> > >
> URCE=500 -pedantic -DUSE_TMP_BUFFER -DALPHA_FIREWALL -DDENABLE_DEBUG -g -DEN
> > > ABLE_TRACE -DPSP_SERVER_PREFIX="/usr/local"
> >
> > -DALPHA_FIREWALL is present above!
> >
> > > address@hidden init.d]# /usr/local/bin/partysip -V
> > > Server header:      WellX/partysip-0.5.3
> > > Server version:     Partysip/0.5.3
> > > Global Config File  /usr/local
> > > Server built:       Jan 15 2003 14:49:34
> > > Server's interface: O.1
> > > Architecture:       32-bit
> > > Server compiled with....
> > >  -DSTDC_HEADERS
> > >  -DHAVE_ASSERT_H
> > >  -DHAVE_CTYPE_H
> > >  -DHAVE_DLFCN_H
> > >  -DHAVE_FCNTL_H
> > >  -DHAVE_MALLOC_H
> > >  -DHAVE_SEMAPHORE_H
> > >  -DHAVE_SIGNAL_H
> > >  -DHAVE_STDARG_H
> > >  -DHAVE_STDDEF_H
> > >  -DHAVE_STDIO_H
> > >  -DHAVE_STDLIB_H
> > >  -DHAVE_STRING_H
> > >  -DHAVE_STRINGS_H
> > >  -DHAVE_SYS_SEM_H
> > >  -DHAVE_SYS_SIGNAL_H
> > >  -DHAVE_SYS_SOCKET_H
> > >  -DHAVE_SYS_TIME_H
> > >  -DHAVE_SYS_TYPES_H
> > >  -DHAVE_TIME_H
> > >  -DHAVE_UNISTD_H
> > >  -DHAVE_VARARGS_H
> > >  -DPSP_SERVER_INSTALL_DIR=/usr/local
> >
> > You don't have to worry about the absence of ALPHA_FIREWALL here.
> >
> > If you need more (firewall is an experimental feature), send me
> > your partysip.conf configuration.
> >
> > Even if working, I'd like feeback!
> > Aymeric
> >
> > > address@hidden init.d]#
> > >
> > > Here's the evidence that I have the latest libosip;
> > >
> > > address@hidden init.d]# ls -l /usr/local/lib/libosip*
> > > lrwxrwxrwx    1 root     root           22 Jan  8 22:19
> > > /usr/local/lib/libosip-0.8.8.so.0 -> libosip-0.8.8.so.0.0.0*
> > > -rwxr-xr-x    1 root     root       346785 Jan  8 22:19
> > > /usr/local/lib/libosip-0.8.8.so.0.0.0*
> > > lrwxrwxrwx    2 root     root           22 Jan 15 07:57
> > > /usr/local/lib/libosip-0.9.3.so.0 -> libosip-0.9.3.so.0.0.0*
> > > -rwxr-xr-x    1 root     root       373407 Jan 15 07:57
> > > /usr/local/lib/libosip-0.9.3.so.0.0.0*
> > > -rw-r--r--    1 root     root      1093890 Jan 15 07:57
> > > /usr/local/lib/libosip.a
> > > -rwxr-xr-x    1 root     root          725 Jan 15 07:57
> > > /usr/local/lib/libosip.la*
> > > lrwxrwxrwx    1 root     root           22 Jan 15 07:57
> > > /usr/local/lib/libosip.so -> libosip-0.9.3.so.0.0.0*
> > >
> > > I've now been through everything I can think of and hope you can suggest
> > > something!
> > >
> > > --
> > > Dr. Craig Graham, Software Engineer
> > > Advanced Analysis and Integration Limited, UK. http://www.aail.co.uk/
> > >
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Partysip-dev mailing list
> > > address@hidden
> > > http://mail.nongnu.org/mailman/listinfo/partysip-dev
> > >
> >
> >
> >
> > _______________________________________________
> > Partysip-dev mailing list
> > address@hidden
> > http://mail.nongnu.org/mailman/listinfo/partysip-dev
> >
> >
>