Here is the SIP transaction log. Caller called 7176 (Cisco 7960) from outside PSTN line, 7185(polycom 601, ip: 192.168.2.104) is the phone which monitors 7176.Reliably Transmitting (no NAT) to 192.168.2.104:5060:NOTIFY sip:[EMAIL PROTECTED] SIP/2.0Via: SIP/2.0/UDP
Isaac Xiao wrote:
We have the same issue happened to all Asterisk versions of 1.2.X (I
tried all). In CLI, it shows “-- Incoming call: Got SIP response 500
Internal Server Error back from 192.168.2.104”. Once you see this msg,
the buddy watch won’t work any more until you reboot the phone. I
On 2/23/06, Olle E Johansson [EMAIL PROTECTED] wrote:
Isaac Xiao wrote: We have the same issue happened to all Asterisk versions of 1.2.X (I tried all). In CLI, it shows "-- Incoming call: Got SIP response 500
Internal Server Error back from 192.168.2.104". Once you see this msg, the buddy watch
On Thu, 23 Feb 2006, Nathan Bowyer wrote:
It may have something to do with the watch limit on the Polycom firmware.
I have one phone that does this as well, nearly all the time. I believe its
the only one that exceeds the 6-7 buddy watch limit as well.
Now that polycom is committed to
] Polycom IP 601 Buddy Watch problems
On Thu, 23 Feb 2006, Nathan Bowyer wrote:
It may have something to do with the watch limit on the Polycom firmware.
I have one phone that does this as well, nearly all the time. I believe its
the only one that exceeds the 6-7 buddy watch limit as well.
Now
Hi,
I configured Buddy Watch function on my Polycom IP 601. It works well, until I
make a reload of Asterisk. After reload, It can't monitor any lines and I have
to restart the phone to reactivate this function.
Is this a specific problem of asterisk-1.2.3? How can I solve it?
Thank in
We have the same issue happened to all Asterisk versions
of 1.2.X (I tried all). In CLI, it shows -- Incoming call: Got SIP
response 500 Internal Server Error back from 192.168.2.104. Once
you see this msg, the buddy watch wont work any more until you reboot
the phone. I also upgrade
