RFC4235 support for SPA500 series

[ovidiusas]

Hello,

I'm trying to configure SLA feature for a CISCO SPA525G phone to work using the RFC4235.

In the "Att Console" tab, I have set the "Server Type" to "RFC3265_4235".

Upon registration, the phone is sending a SUBSCRIBE, but the SUBSCRIBE message is not RFC4235 compliant.

Here's the SUBSCRIBE sent by the phone:

SUBSCRIBE sip:290@192.168.2.2 SIP/2.0.
Via: SIP/2.0/UDP 192.168.2.109:5060;branch=z9hG4bK-286f3d6f.
From: <sip:290@192.168.2.2>;tag=a96d3a59d811171e.
To: <sip:291@192.168.2.2>.
Call-ID: bc087cb-615a39a6@192.168.2.109.
CSeq: 1001 SUBSCRIBE.
Max-Forwards: 70.
Contact: <sip:291@192.168.2.109:5060>.
Expires: 3600.
Event: call-info.
User-Agent: Cisco/SPA525G-7.4.3.
Content-Length: 0.
.

The Event is set to "call-info" and according to the RFC4235 the Event should be set to "dialog".

Is it the "dialog" event package supported by the phone?

If yes, are there extra specific settings other then "Server Type" in "Att Console" that must be set?

Regards,

Ovidiu Sas

[henrydogger]

Hi,

I am having sort of the same problem.

I'm using sipxecs together with spa504G phones.

I want to make presence possible at a reception desk using the voice operator panel of JoHer.

But it seems this phone does not support the subscription for event type dialog (RFC4235)

Now my question is, do i need to adjust a setting or isn't this going to work at all?

And if it's not going to work at all, will there be a fix in the near future?

I'm currently running firmware 7.4.8

I hope someone can shed some light on this

Greetings,

Henry Dogger

Telecats