[Spce-user] help needed

[Lorenzo Mangani]

Hey Andreas,

With presence:
      enable: 'yes'
you still get a 407 for SIP MESSAGE from trusted peer - I have it enabled
since release but its not doing the trick - this is something i discussed
with Jon Bonilla some time ago and he produced a patch to test with that
basically extended the trusted_peer validation as it should. Am i offtrack?

Best,

Lorenzo

On Tue, Feb 5, 2013 at 3:54 PM, Andreas Granig <agranig at sipwise.com> wrote:

> Hi Lorenzo,
>
>
> On 02/05/2013 03:21 PM, Lorenzo Mangani wrote:
>
>> Agreeing 101% with Andreas the confusing nature of this post only
>> carrying the results and not the details, but I think what the user is
>> reporting is simply the result of an attempt to deliver a SIP MESSAGE
>> method between registered endpoints. This currently generates a 403
>> error just as described. Recent discussions seemed to indicate the
>> possibility to fix this and other failing scenarios by extending the
>> trusted_peer/allow_trusted implementation to cover all cases.
>> I have not checked the latest revision's compatibility, but up until
>> some release ago the NOTIFY route could be adapted to also deliver p2p
>> SIP MESSAGE methods
>> (http://www.qxip.net/**mediawiki/index.php/NGCP_%2B_**SIP_Message<http://www.qxip.net/mediawiki/index.php/NGCP_%2B_SIP_Message>)
>> but again
>> - this might be not viable anymore in 2.6/2.7 (will check)
>>
>
> Since 2.6 there is a config.yml option "kamailio.proxy.presence.**enable"
> which you can set to "yes", that will implicitly also allow MESSAGE
> requests (beside subscribe/publish/xcap). It's even enabled out of the box.
>
> So it would be interesting which version Lamarana is using.
>
> Andreas
>



-- 


Lorenzo Mangani

HOMER DEV TEAM
QXIP - Network Engineering
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130205/f0f2e298/attachment-0001.html>