- Joined
- Jun 14, 2012
- Messages
- 12
- Reaction score
- 0
Good Morning,
I have a working 3CX system with 2 Cisco phones we had from a old UC520 deploy. The phones are the Cisco 7931G and the Cisco 7970. I have the phones configured and registering however I am attempting to get the BLF working and I have two problems:
The SIP SUBSCRIBE message that is initially sent by the phones contains no authentication so it is filling the logs with the below message and occassionally blacklisting the phones.
The second problem is that the phones return a 500 Internal Server Error once the subscribe is authenticated. I have looked into this and after reviewing the Wireshark trace, the messages are sent VIA TCP, which is required, and the content types appear to be formatted properly according to the documentation I have found.
Thanks,
Dan
I have a working 3CX system with 2 Cisco phones we had from a old UC520 deploy. The phones are the Cisco 7931G and the Cisco 7970. I have the phones configured and registering however I am attempting to get the BLF working and I have two problems:
The SIP SUBSCRIBE message that is initially sent by the phones contains no authentication so it is filling the logs with the below message and occassionally blacklisting the phones.
Code:
16-08-2012 09:22:12.997 [CM302001]: Authorization system can not identify source of: SUBSCRIBE sip:[email protected] SIP/2.0
Via: SIP/2.0/TCP 10.0.0.145:49583;branch=z9hG4bK66094012
Max-Forwards: 70
Contact: <sip:[email protected]:49583;transport=TCP>
To: <sip:[email protected]>
From: <sip:[email protected]>;tag=001bd501977a25f01eda7652-6b78bb12
Call-ID: [email protected]
CSeq: 1000 SUBSCRIBE
Expires: 2147483647
Accept: application/cpim-pidf+xml
Allow: ACK, BYE, CANCEL, INVITE, NOTIFY, OPTIONS, REFER, REGISTER, UPDATE, SUBSCRIBE
Date: Tue, 09 Nov 2010 15:14:11 GMT
User-Agent: Cisco-CP7931G/9.1.1
Event: presence
Content-Length: 0
The second problem is that the phones return a 500 Internal Server Error once the subscribe is authenticated. I have looked into this and after reviewing the Wireshark trace, the messages are sent VIA TCP, which is required, and the content types appear to be formatted properly according to the documentation I have found.
Thanks,
Dan