01-23-2013 09:00 AM - edited 03-21-2019 09:57 AM
Has anyone been able to get the SPA122/112 Report Rule function working on firmware v1.3.1-003? I just tried it and got no results. It looks like it works fine on a SPA525G2 with the same SIP notify request...
My report rule is set to:
[ --status]tftp://10.4.2.1/$MA_status.xml
On the SPA122 In the syslogs I don't see anything showing that it's sending out the report but on the SPA525G2 IP phone it's showing "
<159>Reporting current profile to server (pldlen=84050)" in the syslogs and sending out the report just fine.
Here's my notify message that works fine with the SPA525 IP phone.
"NOTIFY sip:5165551212@10.4.55.21 SIP/2.0
Via: SIP/2.0/UDP 10.11.84.22:6;rport;branch=z9hG4bK518551
From: <sip:5165551212@10.4.55.21>;tag=21090
To: <sip:5165551212@10.4.55.21>
Authorization: Digest username=""xxxxxxx"", realm=""xxxxxxxx"", nonce=""xxxxxxx"", uri=""sip:xxxxx@10.4.55.21"", response=""xxxxxxxxxxxx"", algorithm=MD5, qop=""auth"", nc=""00000001"", cnonce=""xxxxxxxxxxxxxxxxxxxx""
Call-ID: 3b8f0ae7a3026d922be92b7f3e14b62e@10.11.84.22
CSeq: 21 NOTIFY
Contact: <sip:5165551212@10.11.84.22:6>
Max-Forwards: 70
User-Agent: PHP SIP
Event: report status
Content-Length: 0
Edit: I just tried this on firmware v1.2.1-004 (which by the way is a horrible release), the report rule function doesn't work either.
01-31-2013 01:45 PM
As far as I know, the correct event name is just 'report', not "report status".
Your's SIP NOTIFY packet should not work even with SPA525G2. Well, the syslog message "Reporting current profile ..." is suspicious somewhat.
All at all, I tried to trigger Report and it worked for me on both 1.2.1 and 1.3.1. The only difference in my configuration is the event name (as mentioned above) and the report destination. I'm using https://.../... not tftp://
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide