Chris Clifton wrote:
So do the 7960's have to be on the same subnet as the * box ?
This seems like a major detriment to using them in a typical wan
environment.
- Chris Clifton
----- Original Message -----
From: "Brian West" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 04, 2004 1:58 PM
Subject: Re: [Asterisk-Users] Cisco 7960 bug in 6.1 evident in Asterisk
Does the first line, backup and emergency proxy go to the * box on the
same wire? Malcolm and I figured out the 7960's freak smooth out if the
asterisk server isn't on the same subnet his phones kept rebooting over
and over and over till we took them off the switch they were on and move
them to the one with the aterisk server.
bkw
On Wed, 4 Feb 2004, John Todd wrote:
Yes and no. The Cisco phone is on a NAT network that is quite
distant from one of the Asterisk servers, but on the same wire as the
other. Three lines go to the remote *, and three lines remain local
on the network to the other * server. I'm running CVS as of this
morning on both servers. Strangely, today the phone hasn't locked up
or rebooted, though now I am getting one or two of the lines failing
to REGISTER - they're simply not sending out a request, according to
the network dump. <sigh>
JT
At 7:43 AM -0600 2/4/04, Brian West wrote:
Question.. is the 7960 on the same subnet as your asterisk server? I
have
a 7960 registered with 3 diffrent asterisk servers. All 6 lines.
Running
6.1 and has 12 days of uptime.
bkw
On Wed, 4 Feb 2004, John Todd wrote:
So, I've managed to consistently lock up my Cisco 7960 (SIP 6.1) to
the point where it needs to be unplugged, due to software errors.
This is a first.
My suspicions are that this bug in Asterisk is causing the lockups:
http://bugs.digium.com/bug_view_page.php?bug_id=0000889
It seems unusual to me that a low volume of bogus SIP messages
should
lock up the 7960, but that seems to be the case. It seems this
only
happens on my 7960 that I have completely full of extensions (all
six
line buttons are lit, two of them are auto-answer.) I think this
is
one bug tickling another bug; bad messages from * are killing the
7960.
I'd like anyone else with experiences with this type of failure
with
Asterisk to give me a shout; I'm going to report this to Cisco
somehow, but don't have enough evidence.
> JT
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
My remote 15 seat call center uses 79xx phones and a point to point T1.
Your millage may vary with the number of users/applications your
bandwidth supports. You may need to install QoS for your network to
give SIP traffic top priority. It's best to have a low latency connection!
Regards, TL
_______________________________________________
Asterisk-Users mailing list
[EMAIL PROTECTED]
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
