Hello Saúl, 

Thank you for your reply!

> Thanks for your report! Unfortunately I've been unable to continue 
> fixing the existing bugs in OpenXCAP, but I can tell you that shortly 
> we'll have a new release with the existing bugs fixed. If you find any 
> other bug just open a new bug report :)

Looking forward to it!

> Have you correctly configured the connection to OpenXCAP and allowed the 
> user to subscribe?

You mean regarding eyebeam? I think so, I've changed the Storage tab to use 
XCAP, used the same sip credentials and set as the root url 
http://10.1.1.1/xcap-root/ (which is the same used on the test.py)

> Can you paste the PUBLISH request that caused this?

Sure,

PUBLISH sip:123456...@10.1.1.2:5060 SIP/2.0
Record-Route: <sip:10.1.1.1;lr=on>
Via: SIP/2.0/UDP 10.1.1.1;branch=z9hG4bKcf35.754fc7d4.0
Via: SIP/2.0/UDP 
10.1.1.144:31204;received=10.1.1.144;branch=z9hG4bK-d8754z-d95cd7735f2f5e69-1---d8754z-;rport=31204
Max-Forwards: 69
Contact: <sip:123456...@10.1.1.144:31204>
To: "123456789"<sip:123456...@10.1.1.1>
From: "123456789"<sip:123456...@10.1.1.1>;tag=4c0f2a39
Call-ID: YjI2ODRjMGUzZGFiYmIzZDRmYTM5NjA4NDZjNTJjYWU.
CSeq: 2 PUBLISH
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, 
INFO
Content-Type: application/pidf+xml
User-Agent: eyeBeam release 1013t stamp 43070
Event: presence
Content-Length: 428

<?xml version='1.0' encoding='UTF-8'?><presence 
xmlns='urn:ietf:params:xml:ns:pidf' 
xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' 
xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' 
xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' 
entity='sip:123456...@10.1.1.1'><tuple 
id='t33415c2f'><status><basic>open</basic></status></tuple><dm:person 
id='pbb5a451a'><rpid:activities><rpid:unknown/></rpid:activities></dm:person></presence>

The route on this request was: Eyebeam on 10.1.1.144 registered on OpenSIPS 
10.1.1.1. OpenSIPS on 10.1.1.1 forwards the request to the Presence OpenSIPS 
server that listens on 10.1.1.2

(10.1.1.1 and 10.1.1.2 are on the same physical hardware)

The message is generated from this part of OpenSIPS-Presence configuration:

if (is_from_local()) {
        if (avp_check("$hdr(Event)", "fm/presence*/i") && ($au != $rU || $ar != 
$rd)) {
                xlog("L_WARN", "Account $...@$ar tried to publish $hdr(Event) 
event for $ru\n");
                sl_send_reply("403", "Publishing $hdr(Event) events for others 
is forbidden");

                return;
        }
}

Regards,
Paris Stamatopoulos
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to