[OpenSIPS-Users] PUA MI and pua_publish

[Anca Vamanu]

Hi Julian,

Can you please try what I indicated in the previous mail - replacing the 
Content-Type header for Notify to Polycom in local route? And then let 
me know if it works. This is to check if it is just a matter of content 
type name or if the body itself should also be different. Then I might 
also include this case in the code as sofia does.

Regards,

-- 
Anca Vamanu
www.voice-system.ro


Julian Yap wrote:
> Hi Anca,
>
> Yeah I upgraded to the latest Polycom firmware 3.2.3 (see User Agent below).
>
> It seems Polycom only accepts application/xpidf+xml and
> text/xml+msrtc.pidf.  If I send if "application/pidf+xml" it doesn't
> work, even it I forward on a ""application/pidf+xml" NOTIFY from valid
> UA like X-Lite.
>
> If you check out:
> http://fisheye.freeswitch.org/browse/~raw,r=17178/FreeSWITCH/src/mod/endpoints/mod_sofia/sofia_presence.c
>
> The search for 'polycom'.  You'll see that it sends out
> "application/xpidf+xml" specifically for Polycom phones.
>
> This is the SUBSCRIBE that a Polycom sends out:
> SUBSCRIBE sip:10001005 at sipdev1.test.com SIP/2.0.
> Via: SIP/2.0/UDP 192.168.1.47:5060;branch=z9hG4bK4f059433100DF28E.
> From: "10001007" <sip:10001007 at sipdev1.test.com>;tag=3965CFF7-15338CF2.
> To: <sip:10001005 at sipdev1.test.com>.
> CSeq: 1 SUBSCRIBE.
> Call-ID: b35e2521-9206c4ac-8639c7ef at 192.168.1.47.
> Contact: <sip:10001007 at 192.168.1.47:5060>.
> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE,
> NOTIFY, PRACK, UPDATE, REFER.
> Event: presence.
> User-Agent: PolycomSoundPointIP-SPIP_450-UA/3.2.3.1734.
> Accept-Language: en.
> Accept: application/xpidf+xml,text/xml+msrtc.pidf.
> Max-Forwards: 70.
> Expires: 3600.
> Content-Length: 0.
>
> - Julian
>
> On Mon, Apr 26, 2010 at 2:31 AM, Anca Vamanu <anca at opensips.org> wrote:
>   
>> Julian Yap wrote:
>>     
>>> I guess Polycom phones only accept application/xpidf+xml.
>>>
>>>
>>>
>>>       
>> Hi Julian,
>>
>> I kept searching what  "application/xpidf+xml" is and it was quite hard to
>> find since it seems to be something not used any more. I found in the ietf
>> draft preceding the PIDF RFC
>> (http://www.jdrosen.net/papers/draft-rosenberg-impp-pidf-00.txt) the
>> following statement:
>>
>> PIDF documents have the MIME type "application/xpidf+xml".
>>
>>
>> So it seems to be a proposition present in the draft but that was latter
>> dropped when passing to the RFC ( now the mime type is application/pidf+xml
>> )
>>
>> Strange that Polycom have such an old implementation of presence  maybe you
>> should update your firmare? ).
>>
>> And related to what you asked, you can not configure presence module to
>> change the Content Type of Notify depending on the destination. But maybe
>> you can hack it in a local route, catch the generated Notify, remove the
>> Content-Type header and add a new one. But I don't know if the this is
>> sufficient and the document itself will be accepted by the phone.
>>
>> Regards,
>>
>> --
>> Anca Vamanu
>> www.voice-system.ro
>>     
>>