THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#324 - Entity URI in NOTIFY XML body
User who did this - Daniel-Constantin Mierla (miconda)
--
I had no time to dig in specs, I mainly applied the patch with an extra check.
Could be more consisten
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#324 - Entity URI in NOTIFY XML body
User who did this - Pawel Sternal (Sternik)
--
In my situation there is no problem because I only use "sip:" url but Alex
might be right. Maybe instead compose
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#324 - Entity URI in NOTIFY XML body
User who did this - Alex Hermann (axlh)
--
Should "sip:" really be hardcoded?
I would expect the entity to be identical to the presentity in the
corresponding
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#324 - Entity URI in NOTIFY XML body
User who did this - Daniel-Constantin Mierla (miconda)
--
OK. It may make no sense to have a module parameter if using uri schema is the
correct mode. Also will
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#324 - Entity URI in NOTIFY XML body
User who did this - Pawel Sternal (Sternik)
--
Yes, you're right. I forgot to update len check.
And yes, this work with all phones which I test. Polycom seems
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#324 - Entity URI in NOTIFY XML body
User who did this - Daniel-Constantin Mierla (miconda)
--
Does this work with all the phones? I wonder if there has to be a flag to do it
per subscription dialo
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#324 - Entity URI in NOTIFY XML body
User who did this - Pawel Sternal (Sternik)
--
And this is a log before I've patch notify_body.c
--
One or more files have been attached.
More informat
