partysip-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Partysip-dev] Not responding to REGISTER message


From: Aymeric Moizard
Subject: Re: [Partysip-dev] Not responding to REGISTER message
Date: Mon, 27 May 2002 10:44:33 +0200 (CEST)

Great thanks for revealing this select issue. Don't know again why linux
is so kind with my errors...

On Mon, 27 May 2002, Tim Na wrote:

> Hi,
> I found the problem in partysip.
> The problem was that in Solaris select() function would not take
> usec value more than 10**6.
> So I changed the value by setting sec = 5 instead and it now works fine in 
> Solaris box.
>
> And one more thing, Aymeric.
> Were you going to change the sendto() to send() in udp.c as you
> mentioned in previous mail?

Where? but you said it... in udp.c?
Do you mean in which release? I think the send() call is already
modified in 0.4.4 release. (official one :)

You can always get the latest CVS developments from the savannah
CVS by following the procedure described there: (follow the CVS
link)

http://savannah.gnu.org/projects/partysip

To use the CVS version of partysip, you have to
also use the CVS version of oSIP:
http://savannah.gnu.org/projects/osip

> With these changes above, it is somewhat(?) compatible in Solaris now.
> (who knows what's next? :-)

somewhat(?)... I hope this is not somewhat compatible...
Can you try thoses cases: (with authentication = off)

1 You send an INVITE to "somebody" which has not registred: you get a 404.
2 "somebody" register and get a 200 OK
3 You send an INVITE to "somebody"and the transaction is forwarded
  statelessly by the "ls_localdb" plugin.
4 You send a deregistration for "somebody" (a REGISTER with contact=*)
  and you get a 200 OK with an empty list of contact.
5 You send an INVITE to somebody and get a 480 Temporarily unvailable
6 For possible memory related issue, it is interesting to leave the
application using the "q" command (you must give the -i for interactive
session of partysip). This may reveal some bugs on releasing memory.

That's all you have to test!
Let me know if something goes wrong...
Thanks for your help
Aymeric

> Regards,
> Tim Na
>
> ----- Original Message -----
> From: "Aymeric Moizard" <address@hidden>
> To: "Tim Na" <address@hidden>
> Cc: <address@hidden>
> Sent: Thursday, May 23, 2002 5:28 PM
> Subject: Re: [Partysip-dev] Not responding to REGISTER message
>
>
> >
> >
> > On Thu, 23 May 2002, Tim Na wrote:
> >
> > > I believe the issue here is not as simple as you said...
> > > When I tried it in Linux, partysip responds to the register message.
> > > I also asked Ralf for he is using the same platform to run the partysip.
> > > He also mentioned of the same symptom.
> > > Somehow partysip is not working properly in Solaris environment.
> >
> > partysip has only been developped on linux since its beginning.
> > I don't have a solaris box, and so can't fix the issue for you...
> >
> > > I am gdbing the partysip and so far I see that it is "hanging" after the 
> > > psp_core_start(),
> > > not returning from read() in pspm_tlp_execute() thread.
> > > I wonder what the difference it makes in Solaris than Linux.
> >
> > May be the pipe man page will tell you! Othing special can be
> > found in the pipe manpage from linux.
> >
> > Hope you can fix it.
> > Aymeric
> >
> > >       if (FD_ISSET(s, &tlp_fdset))
> > >  { /* time to wake up: we receive "q" to quit and any other char to read 
> > > all socket */
> > >    char tmp[2];
> > >    i = ppl_pipe_read(pspm->module->wakeup, tmp, 1);   <======= thread is 
> > > not returning here even after the register message.
> > >    if ( i==1 && tmp[0]=='q')
> > >      {
> > >        TRACE(trace(__FILE__,__LINE__,TRACE_LEVEL1,NULL,"INFO: Exiting tlp 
> > > module!\n"));
> > >        return 0;
> > >      }
> > >  }
> > >
> > >
> > > ----- Original Message -----
> > > From: "Aymeric Moizard" <address@hidden>
> > > To: "Tim Na" <address@hidden>
> > > Cc: <address@hidden>
> > > Sent: Tuesday, May 21, 2002 5:07 PM
> > > Subject: Re: [Partysip-dev] Not responding to REGISTER message
> > >
> > >
> > > >
> > > > partysip is NOT receiving any message.
> > > > Check your linphone configuration.
> > > >
> > > > Also, I tested the CVS version of linphone...
> > > >
> > > > Simon? when do you plan to release the *highly
> > > > wanted* linphone updates?
> > > >
> > > > Aymeric
> > > >
> > > > On Tue, 21 May 2002, Tim Na wrote:
> > > >
> > > > > The below is all the log info that I got.
> > > > > I have already sent a register message from the linphone.
> > > > >
> > > > > htna_view:htna$ more partysip.log
> > > > > L0 -1021942366- <../../partysip-0.4.3/src/psp_utils.c: 171> INFO: 
> > > > > registrar plug
> > > > > in: Number of auth rules: 0. Number of user entries: 5
> > > > > L2 -1021942366- <../../../partysip-0.4.3/plugin/udp/udp_core.c: 61> 
> > > > > INFO: udp pl
> > > > > ugin: plugin_init()!
> > > > > L2 -1021942366- <../../../partysip-0.4.3/plugin/syntax/syntax_core.c: 
> > > > > 51> INFO:
> > > > > syntax plugin: plugin_init()!
> > > > > L2 -1021942366- <../../../partysip-0.4.3/plugin/filter/filter_core.c: 
> > > > > 62> INFO:
> > > > > filter plugin: plugin_init()!
> > > > > L3 -1021942366- <../../../partysip-0.4.3/plugin/filter/filter_core.c: 
> > > > > 141> INFO:
> > > > >  filter plugin: Authentication is turned off!
> > > > > L2 -1021942366- <../../../partysip-0.4.3/plugin/auth/auth_core.c: 64> 
> > > > > INFO: auth
> > > > >  plugin: plugin_init()!
> > > > > L3 -1021942366- <../../../partysip-0.4.3/plugin/auth/auth_core.c: 77> 
> > > > > INFO: auth
> > > > >  plugin: Authentication is turned off!
> > > > > L2 -1021942366- 
> > > > > <../../../partysip-0.4.3/plugin/rgstrar/rgstrar_core.c: 63> INFO
> > > > > : rgstrar plugin: plugin_init()!
> > > > > L2 -1021942366- 
> > > > > <../../../partysip-0.4.3/plugin/ls_sless/ls_sless_core.c: 61> IN
> > > > > FO: ls_sless plugin: plugin_init()!
> > > > > L2 -1021942366- 
> > > > > <../../../partysip-0.4.3/plugin/ls_localdb/ls_localdb_core.c: 54
> > > > > > INFO: ls_localdb plugin: plugin_init()!
> > > > > htna_view:htna$
> > > > >
> > > > > Since there was no message retrieving info, I doubted about the 
> > > > > message reception, but
> > > > > when I used libosip-0.7.3's example_mt ua, the ua was returning OK 
> > > > > for the same register message
> > > > > from linphone. So I assume that the message is reaching to port 5060 
> > > > > for sure, but perhaps the
> > > > > partysip is not respoding to the message..??
> > > > >
> > > > > ----- Original Message -----
> > > > > From: "Aymeric Moizard" <address@hidden>
> > > > > To: "Tim Na" <address@hidden>
> > > > > Cc: <address@hidden>
> > > > > Sent: Monday, May 20, 2002 7:50 PM
> > > > > Subject: Re: [Partysip-dev] Not responding to REGISTER message
> > > > >
> > > > >
> > > > > >
> > > > > > You registrar configuration seems OK.
> > > > > > May be old linphone release does not work?
> > > > > >
> > > > > > Can you run partysip this way
> > > > > > partysip -d 6 -l partysip.log
> > > > > >
> > > > > > and please send the log file?
> > > > > > Ay
> > > > > >
> > > > > > On Mon, 20 May 2002, Tim Na wrote:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I have hard time running partysip as a registrar server.
> > > > > > > I am not sure if the partysip.conf file is wrong or not, would 
> > > > > > > anyone check the
> > > > > > > info below to see what's wrong.
> > > > > > > Thanks in advance. :-)
> > > > > > >
> > > > > > > # global config
> > > > > > >
> > > > > > > serverip       = 165.213.84.84
> > > > > > > servername     = 165.213.84.84
> > > > > > > serverport_udp = 5060
> > > > > > >
> > > > > > > # use this for local test:
> > > > > > > #serverip    = 165.213.84.84
> > > > > > > #serverip2    = 80.32.24.53    this could be the second interface.
> > > > > > >
> > > > > > > # this is used for generating random string and MUST BE AT LEAST 
> > > > > > > 10 characters
> > > > > > > magicstring = partysip_a45bc357
> > > > > > > # this is used for generating random string and MUST BE AT LEAST 
> > > > > > > 10 characters
> > > > > > > serverrealm = "partysip.org"
> > > > > > >
> > > > > > > # ask for authentication  on/off
> > > > > > > authentication = off
> > > > > > >
> > > > > > > # mode for ls_sless plugin
> > > > > > > mode = stateless
> > > > > > >
> > > > > > > # sub configs
> > > > > > > #   - ALL GLOBAL CONFIGURATION MUST BE ABOVE -
> > > > > > >
> > > > > > > <filter>
> > > > > > >
> > > > > > > # the first rule that match is taken!
> > > > > > >
> > > > > > > # <rule>  <return code>  <header>  <string>
> > > > > > >
> > > > > > > # reject request with domain.org in the from header and NOT 
> > > > > > > domain.org in the to
> > > > > > > #reject 404 from !domain.org  to !domain.org
> > > > > > > # reject request with holemail.net in the to header
> > > > > > > #reject 403 to   holemail.net
> > > > > > > # reject request with holemail.net in the rquri header
> > > > > > > #reject 403 to   holemail.net
> > > > > > > # reject request with holemail.net in the rquri header
> > > > > > >
> > > > > > > </filter>
> > > > > > >
> > > > > > > <userinfo>
> > > > > > >
> > > > > > > # static user list of known users
> > > > > > > #      this would be better to retreive some of this config 
> > > > > > > element
> > > > > > > #      from /etc/passwd, an LDAP directory...
> > > > > > > #
> > > > > > > # for "user" type:
> > > > > > > #  <user>       <NAME>  <DOMAINNAME>  <auth_login>   
> > > > > > > <auth_passwd>    <URI>
> > > > > > > #  user  jack   atosc.org   jack secret     
> > > > > > > sip:address@hidden<sip:anod
> > > > > > > e.atosc.org>;lr
> > > > > > >
> > > > > > > #user  sip:address@hidden    ua    ua    sip:address@hidden
> > > > > > > #user  sip:address@hidden   none  none  sip:address@hidden:5080
> > > > > > > #user  sip:address@hidden    ua    ua    sip:address@hidden:5070
> > > > > > > #user  sip:address@hidden   none  none  sip:address@hidden:5080
> > > > > > >
> > > > > > > user  sip:address@hidden    adtech115 adtech115  
> > > > > > > sip:address@hidden
> > > > > > > user  sip:address@hidden    adtech113 adtech113  
> > > > > > > sip:address@hidden
> > > > > > > user  sip:address@hidden    siemens  123456      
> > > > > > > sip:address@hidden
> > > > > > > user  sip:address@hidden    none  none           
> > > > > > > sip:address@hidden:5090
> > > > > > > user  sip:address@hidden    tim      none        
> > > > > > > sip:address@hidden
> > > > > > >
> > > > > > > </userinfo>
> > > > > > >
> > > > > > > #who needs authentication
> > > > > > >
> > > > > > > auth from       sip.wellx.org  INVITE REGISTER
> > > > > > > auth    from    127.0.0.1  INVITE REGISTER
> > > > > > > auth    to      gateway.org INVITE
> > > > > > >
> > > > > > > </registrar>
> > > > > > >
> > > > > > >
> > > > > > > And I am using Linphone's register message as below.
> > > > > > >
> > > > > > > REGISTER sip:165.213.84.84 SIP/2.0
> > > > > > > Via: SIP/2.0/UDP 165.213.84.91:5060
> > > > > > > From: <sip:address@hidden>
> > > > > > > To: <sip:address@hidden>
> > > > > > > Call-ID: address@hidden
> > > > > > > CSeq: 1 REGISTER
> > > > > > > Contact: <sip:address@hidden>
> > > > > > > expires: 60
> > > > > > > user-agent: oSIP/Linphone-0.7.0
> > > > > > > Content-Length: 0
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Partysip-dev mailing list
> > > > > address@hidden
> > > > > http://mail.freesoftware.fsf.org/mailman/listinfo/partysip-dev
> > > > >
> > > >
> > > >
> > >
> > > _______________________________________________
> > > Partysip-dev mailing list
> > > address@hidden
> > > http://mail.freesoftware.fsf.org/mailman/listinfo/partysip-dev
> > >
> >
> >
>
> _______________________________________________
> Partysip-dev mailing list
> address@hidden
> http://mail.freesoftware.fsf.org/mailman/listinfo/partysip-dev
>




reply via email to

[Prev in Thread] Current Thread [Next in Thread]