Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#28 ERROR pua_bla: bla_handle_notify() content length= 0

trunk
closed
Anca Vamanu
modules (454)
5
2008-11-03
2008-10-17
Norm Brandinger
No

First time implementation of BLA (using Polycom phone) using the published documentation as a guide.

The bla_handle_notify() call, throws the following error:

ERROR:pua_bla:bla_handle_notify: content length= 0

This problem was also previously reported as noted in the following post:

http://www.nabble.com/pua_bla-and-presence-td18538692.html

Discussion

  • Anca Vamanu
    Anca Vamanu
    2008-10-22

    Hi Norm,

    What version of pua_bla are you using? OpenSIPS release 1.4.2 or trunk?
    There were quite a lot of changes made from OpenSER 1.3.2 and I would suggest using OpenSIPS.

    regards,
    Anca Vamanu

     
  • Anca Vamanu
    Anca Vamanu
    2008-10-22

    • assigned_to: nobody --> anca_vamanu
     
  • Anca Vamanu
    Anca Vamanu
    2008-10-22

    Hi Norm,

    What version of pua_bla are you using? OpenSIPS release 1.4.2 or trunk?
    There were quite a lot of changes made from OpenSER 1.3.2 and I would suggest using OpenSIPS.

    regards,
    Anca Vamanu

     
  • This error happened using OpenSIPS trunk.

    There wasn't alot of information related to this error. The URL I added to the ticket appeared to be similar. Will run some tests later today.

    Regards,
    Norm

     
  • Anca Vamanu
    Anca Vamanu
    2008-10-23

    Hi Norm,

    I checked and indeed I have designed the pua_bla module not accept Notifies with content length 0. Now, I am not sure if this is a bug or if there really should not be Notifies with no body.
    I see no reference to when a Notify with no body can be sent in general Event Notification RFC 3265 or in draft-bla-anil-sip-03 after which pua_bla module is implemented. The only mention of a Notify without a body is in RFC 3856 for event presence:
    If the resource has no meaningful state at the time that the SUBSCRIBE message is
    processed, this NOTIFY message MAY contain an empty or neutral body.

    Anyhow, logically I don't see any case in which a UA might send a Notify for dialog;sla without any body. It is not difficult to remove this restriction in the server, but I don't see a reason why I should receive Notifies with no body.
    Since I have tested a lot with Polycom phones I wonder how come I have not seen this. Can you please reproduce this and capture the notify you get this error with?
    I am also thinkig there might be something in your configuration. Please check to have your processing as in the example here http://openser.org/index.php?n=Resources.PuaBlaConfig .

    regards,
    Anca

     
  • Anca Vamanu
    Anca Vamanu
    2008-10-23

    Hi Norm,

    I checked and indeed I have designed the pua_bla module not accept Notifies with content length 0. Now, I am not sure if this is a bug or if there really should not be Notifies with no body.
    I see no reference to when a Notify with no body can be sent in general Event Notification RFC 3265 or in draft-bla-anil-sip-03 after which pua_bla module is implemented. The only mention of a Notify without a body is in RFC 3856 for event presence:
    If the resource has no meaningful state at the time that the SUBSCRIBE message is
    processed, this NOTIFY message MAY contain an empty or neutral body.

    Anyhow, logically I don't see any case in which a UA might send a Notify for dialog;sla without any body. It is not difficult to remove this restriction in the server, but I don't see a reason why I should receive Notifies with no body.
    Since I have tested a lot with Polycom phones I wonder how come I have not seen this. Can you please reproduce this and capture the notify you get this error with?
    I am also thinkig there might be something in your configuration. Please check to have your processing as in the example here http://openser.org/index.php?n=Resources.PuaBlaConfig .

    regards,
    Anca

     
  • Hi Anca,

    Thank you for taking the time to look into my problem.

    I'll try to reproduce the error. Your suggestion that the Polycom config might be incorrect may be valid.

    Can you share example settings (or perhaps explain the interaction of the settings below) for two Polycom's configured for BLA ? I'm currently testing with settings listed below:

    Phone1:

    Address: 1000
    Auth User ID: 1000
    Label: 1000
    Third Party Name: 1000

    mac-directory.xml:
    <ct>1000</ct>

    Phone2:

    Address: 1000
    Auth User ID: 1001
    Label: 1000
    Third Party Name: 1000

    mac-directory.xml:
    <ct>1000</ct>
    <ct>1001</ct>

    Regards,
    Norm

     
  • Unable to reproduce this problem. Will reopen if I can again reproduce it.

     
    • status: open --> closed