[Freeswitch-users] SUBSCRIBE - Bad Event
Bote Man
botelist at gmail.com
Tue Oct 13 08:23:48 UTC 2020
I had that with some Poly(com) VVX501 phones.
The solution was to set every occurrence of .regevent="0" so
reg.1.regevent="0", reg.2.regevent="0", and so on.
>From their docs:
voIpProt.SIP.regevent
0 (default) - The phone is not subscribed to registration state change
notifications for all phone lines.
1 - The phone is subscribed to registration state change notifications for
all phone lines.
This parameter is overridden by the per-phone parameter reg.x.regevent.
I did not troubleshoot it, I simply set it to 0 and moved on. I have no idea
what the equivalent would be on a Cisco phone, but if you see a related
setting maybe it's worth toggling it to see what the result is.
Hope this helps.
---
John Boteler
BnC Group U.S.A.
From: FreeSWITCH-users <freeswitch-users-bounces at lists.freeswitch.org> On
Behalf Of Sean Devoy
Sent: Monday, 12 October, 2020 17:51
To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
Subject: [Freeswitch-users] SUBSCRIBE - Bad Event
Hi,
I am getting 489 Bad Event for my users "SUBSCRIBE" packets. SUBSCRIBE is
clearly listed in ALLOW. 2 Sample packets below.
Any ideas?
Thanks,
Sean
recv 524 bytes from tcp/[73.555.94.74]:1024 at 17:52:51.791847:
------------------------------------------------------------------------
SUBSCRIBE sip:214 at clientdomain.com <sip:214 at fs-esta2.bizfocused.com>
SIP/2.0
Via: SIP/2.0/TCP 192.168.2.124:5075;branch=z9hG4bK-1d541664;rport
From: "214" <sip:214 at clientdomain.com <sip:214 at fs-esta2.bizfocused.com>
>;tag=59cf9549d7610470
To: "214" <sip:214 at clientdomain.com <sip:214 at fs-esta2.bizfocused.com> >
Call-ID: b36ae378-cf9d3789 at 192.168.2.124
<mailto:b36ae378-cf9d3789 at 192.168.2.124>
CSeq: 1001 SUBSCRIBE
Max-Forwards: 70
Contact: "214" <sip:214 at 192.168.2.124:5075;transport=tcp>
Accept: application/x-broadworks-callpark-info+xml
Expires: 1800
Event: x-broadworks-callpark
User-Agent: Cisco/SPA504G-7.6.2e
Content-Length: 0
send 717 bytes to tcp/[73.555.94.74]:1024 at 17:52:51.791962:
------------------------------------------------------------------------
SIP/2.0 489 Bad Event
Via: SIP/2.0/TCP
192.168.2.124:5075;branch=z9hG4bK-1d541664;rport=1024;received=73.555.94.74
From: "214" <sip:214 at clientdomain.com <sip:214 at fs-esta2.bizfocused.com>
>;tag=59cf9549d7610470
To: "214" <sip:214 at clientdomain.com <sip:214 at fs-esta2.bizfocused.com>
>;tag=279QBZZaKS7cr
Call-ID: b36ae378-cf9d3789 at 192.168.2.124
<mailto:b36ae378-cf9d3789 at 192.168.2.124>
CSeq: 1001 SUBSCRIBE
User-Agent: FreeSWITCH-mod_sofia/1.10.2-release-14-f7bdd3845a~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER,
REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, presence, as-feature-event, dialog,
line-seize, call-info, sla, include-session-description, presence.winfo,
message-summary, refer
Content-Length: 0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20201013/8b7fa1e4/attachment.html>
More information about the FreeSWITCH-users
mailing list