[OpenSIPS-Users] Presence Error messages

[Peter Kust]

I'm running a rotating packet capture right now, but at the moment that error hasn't resurfaced since I started the capture.

What is perplexing to me is that I have never seen in my logs a PUBLISH with that particular etag (as pulled from the sip-if-tag header on the received PUBLISH).  Only once have I even seen that etag in the presentity table.   Yet somewhere that etag has survived complete reboots of the involved phones and opensips itself.  Where do I look to see what might be hanging on to that etag (presumably erroneously)?

Also, it seems that the update_presentity is being called by SUBSCRIBE, not PUBLISH

Mar 20 10:20:31 proxy-2 o[21911]: [83693] SUBSCRIBE [line-seize:15] sip:SLA-4103855210-1 at X.X.X.X From:sip:SLA-4103855210-1@ X.X.X.X To:sip:SLA-4103855210-1@ X.X.X.X Call-ID:4925925-382640b2@ Y.Y.Y.Y Cseq:40035 Contact:"5210" <sip:SLA-4103855210-1 at Y.Y.Y.Y:5062> < Y.Y.Y.Y:5062>
Mar 20 10:20:31 proxy-2 o[21911]: ERROR:presence:update_presentity: No E_Tag match [ff5ad69c9be06cffaa136492f4fb3b50]
Mar 20 10:20:31 proxy-2 o[21911]: INFO:presence:update_subscription: notify
Mar 20 10:20:31 proxy-2 o[21911]: INFO:presence:send_notify_request: NOTIFY sip:SLA-4103855210-1@@ X.X.X.X via sip:SLA-4103855210-1@ Y.Y.Y.Y:5062 on behalf of sip:SLA-4103855210-1@@ X.X.X.X for event line-seize, to_tag=e92fa9072a6867d6d6f7ec7d0c504ad5-5cd1, cseq=1

So I am trying to figure out where that etag is hiding.  Because from what I can see it shouldn't be getting referenced at all.

Cordially,

Peter Nayland Kust
Director of Technologies
BusinesSuites
24624 Interstate 45 North, Suite 200
Houston, TX 77386
Tel:  281.378.8051
Fax:  855.287.6961
peter.kust at businessuites.com
From: Bogdan-Andrei Iancu [mailto:bogdan at opensips.org]
Sent: Friday, March 20, 2015 11:49 AM
To: OpenSIPS users mailling list; Peter Kust
Subject: Re: [OpenSIPS-Users] Presence Error messages

Hi Peter,

The first error means: the presentity your PUBLISH tries to update (using etag as reference) does not exist anymore. The etag is created on the first PUBLISH and sent back to publisher - it will use this etag each time it wants to update that particular presentity.

Maybe the re-publishing is too late and the presentity is already expired in opensips memory.

Do you have dbg logs + pcap for this ?

Best regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer

http://www.opensips-solutions.com
On 19.03.2015 17:10, Peter Kust wrote:
I am attempting to troubleshoot what I think is a presence/b2b_sca issue.

I keep getting an error message from presence as follows:
ERROR:presence:update_presentity: No E_Tag match [ff5ad69c9be06cffaa136492f4fb3b50]

At some point during the day, I will see this error message:
ERROR:presence:handle_subscribe: in event specific subscription handling

At this point, an outbound call from a line appearance provisioned to the b2b_sca module fails.  The outbound call is being attempted from a Cisco SPA525G2, and the message on the phone screen shows "no line"-despite happening at a time when it is known there are no calls on the system that I can see.  The observed behavior of the phone is to show "No line", and the phone itself gets a

What do these error messages mean?  What is the system trying to tell me?  I am trying to get my brain around what the error messages are saying so I can figure out where to look next in my troubleshooting.  The proxy is functioning well in all other respects.

Cordially,

Peter Nayland Kust
Director of Technologies
BusinesSuites
24624 Interstate 45 North, Suite 200
Houston, TX 77386
Tel:  281.378.8051
Fax:  855.287.6961
peter.kust at businessuites.com<mailto:peter.kust at businessuites.com>




_______________________________________________

Users mailing list

Users at lists.opensips.org<mailto:Users at lists.opensips.org>

http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150320/4c460e16/attachment.htm>