Peers can't register whilst X-Lite can

Help
2013-05-08
2013-05-14
  • Bobbie Smulders

    Bobbie Smulders - 2013-05-08

    I am having some problems with the Peers GUI not being able to register to the SIP server, whilst X-Lite has no problems with it.

    When I look at my network traffic using WireShark, X-Lite has the following pattern:
    Client: REGISTER
    Server: 401 Unauthorized
    Client: REGISTER (this time using auth)
    Server: 200 OK

    When I look at my network traffic using Peers, I get:
    Client: REGISTER
    Server: 401 Unauthorized
    Client: REGISTER (using auth)
    Client: REGISTER (using auth)
    Client: REGISTER (using auth)

    My server is basically giving the silent treatment.

    If I look into the two different REGISTER messages (from X-Lite and Peers):
    Peers: http://tinypic.com/r/4req9x/5
    X-Lite: http://tinypic.com/r/6oik2t/5

    They are different, but all the key components seem to be in the right place. It is rather peculiar that the auth is different. The plain-text password is "kpn".

    The difference in settings (from X-Lite and Peers):
    Peers: http://tinypic.com/r/6ek6dt/5
    X-Lite: http://tinypic.com/r/2zisq6s/5

    I have also tried placing a call without registering by using peers as a library, but then I have the same problem: After the server requests authorization (and peers give in to this demand), the server stops talking to the client.

    Help is much appreciated. I am running into a wall here. Peers is the perfect library for my project because of the ease of use and media possibilities. Thanks in advance.

     
  • mengchunzhi

    mengchunzhi - 2013-05-10

    peers register message don't have the "expires" head, I add this head para then success register on OpenImsCore

     
    • yohannmartineau

      yohannmartineau - 2013-05-10

      in rfc3261 sip specification, a sip client can ask for a specific expires
      using a specific Expires header or a parameter in Contact URI, but in the
      end, it's always the server who gives its preferred expires value. If no
      expires value is asked by client, server has to give its own preferred
      default value.

      On Fri, May 10, 2013 at 4:34 AM, mengchunzhi mengchunzhi@users.sf.netwrote:

      peers register message don't have the "expires" head, I add this head para
      then success register on OpenImsCore


      Peers can't register whilst X-Lite canhttps://sourceforge.net/p/peers/discussion/683024/thread/4e57b62d/?limit=25#8a96

      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/peers/discussion/683024/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       
    • Bobbie Smulders

      Bobbie Smulders - 2013-05-14

      I think this might be it. Could you perhaps point me in the right direction for adding the expires parameter?

       

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks