Hi all. I have been tasked with performing a SIP interop with the Cisco 7941 model IP phone. I've failed to get it working with the latest SIP 9.x which is still available from Cisco w/o a contract.
From what I've found in my research, an older version 8.5.4 might be the way to go but I can't download it from Cisco without a contract. I'm not sure why they chose to protect the older versions but not the newer.
Anyway, would any of you happen to know an alternate place for me to download the file? I'm not sure I'll be able to purchase a contract to allow me to download the file since this model went EOS so long ago. I'm looking for: cmterm-7941_7961-sip.8-5-4.zip Feel free to direct message me if you prefer. Thanks -Adam
Hi Adam, So...if you value your time and sanity... don't support sip with cisco 79xx series. If you wish to do this purely for Fun.... Good luck, hopefully you have a lot of time on your hands and a great amount of patience. :) Faisal Imtiaz Snappy Internet & Telecom 7266 SW 48 Street Miami, Fl 33155 Tel: 305 663 5518 x 232 Helpdesk: 305 663 5518 option 2 Email: Support at Snappydsl.net On 3/18/2013 6:37 PM, Adam Baird wrote:
Hi all.
I have been tasked with performing a SIP interop with the Cisco 7941 model IP phone. I've failed to get it working with the latest SIP 9.x which is still available from Cisco w/o a contract.
From what I've found in my research, an older version 8.5.4 might be the way to go but I can't download it from Cisco without a contract. I'm not sure why they chose to protect the older versions but not the newer.
Anyway, would any of you happen to know an alternate place for me to download the file? I'm not sure I'll be able to purchase a contract to allow me to download the file since this model went EOS so long ago.
I'm looking for: cmterm-7941_7961-sip.8-5-4.zip
Feel free to direct message me if you prefer.
Thanks -Adam
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On 03/18/2013 11:45 PM, Faisal Imtiaz wrote:
So...if you value your time and sanity... don't support sip with cisco 79xx series.
If you wish to do this purely for Fun.... Good luck, hopefully you have a lot of time on your hands and a great amount of patience.
Eh, it's not so bad with the 7960s. A bit of a pain, but the high-quality hardware makes it worth it. The 7940s? Yeah, I wouldn't touch that. -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
The 7940 and 7960 are the exact same thing except for the line key count. They both are fairly reliable with "Non-CM" SIP in 8.X and on as long as you stay away from any remotely fancy features like shared lines (SUBSCRIBE) or such. The 7941 and 61 however I've never seen the non-CM SIP FW for. If it is a CM-SIP FW, you may want to check this 7970 reference and some of the related articles for XML config help: http://www.voip-info.org/wiki/view/Asterisk+phone+cisco+7970+SIP -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov Sent: Monday, March 18, 2013 7:40 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Older Cisco SIP firmware download On 03/18/2013 11:45 PM, Faisal Imtiaz wrote:
So...if you value your time and sanity... don't support sip with cisco 79xx series.
If you wish to do this purely for Fun.... Good luck, hopefully you have a lot of time on your hands and a great amount of patience.
Eh, it's not so bad with the 7960s. A bit of a pain, but the high-quality hardware makes it worth it. The 7940s? Yeah, I wouldn't touch that. -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Just keep in mind that on newer versions of the SIP firmware, like the 9.X series, SIP signalling is done via TCP - only -. There is also somechanges that require you to set some NAT xml value to NO. You can easily find it around... Other then that, they are very solid handsets. Regards On 20-03-2013 01:51, Scott Berkman wrote:
The 7940 and 7960 are the exact same thing except for the line key count. They both are fairly reliable with "Non-CM" SIP in 8.X and on as long as you stay away from any remotely fancy features like shared lines (SUBSCRIBE) or such.
The 7941 and 61 however I've never seen the non-CM SIP FW for. If it is a CM-SIP FW, you may want to check this 7970 reference and some of the related articles for XML config help:
http://www.voip-info.org/wiki/view/Asterisk+phone+cisco+7970+SIP
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov Sent: Monday, March 18, 2013 7:40 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Older Cisco SIP firmware download
On 03/18/2013 11:45 PM, Faisal Imtiaz wrote:
So...if you value your time and sanity... don't support sip with cisco 79xx series.
If you wish to do this purely for Fun.... Good luck, hopefully you have a lot of time on your hands and a great amount of patience. Eh, it's not so bad with the 7960s. A bit of a pain, but the high-quality hardware makes it worth it.
The 7940s? Yeah, I wouldn't touch that.
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
The lack of support for modern features -- Line State Monitoring, Feature Key Synchronization, Shared Lines / Shared Call Appearance, N-Way conferencing -- have convinced me that the best thing to do with a Cisco 79x0 phone is to Ebay them to someone using Call Manager. Then buy a modern SIP phone.
mark at ecg.co +12293160013 http://ecg.co/lindsey
On Mar 19, 2013, at 21:51 , "Scott Berkman" <scott at sberkman.net> wrote:
The 7940 and 7960 are the exact same thing except for the line key count. They both are fairly reliable with "Non-CM" SIP in 8.X and on as long as you stay away from any remotely fancy features like shared lines (SUBSCRIBE) or such.
The 7941 and 61 however I've never seen the non-CM SIP FW for. If it is a CM-SIP FW, you may want to check this 7970 reference and some of the related articles for XML config help:
http://www.voip-info.org/wiki/view/Asterisk+phone+cisco+7970+SIP
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Alex Balashov Sent: Monday, March 18, 2013 7:40 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] Older Cisco SIP firmware download
On 03/18/2013 11:45 PM, Faisal Imtiaz wrote:
So...if you value your time and sanity... don't support sip with cisco 79xx series.
If you wish to do this purely for Fun.... Good luck, hopefully you have a lot of time on your hands and a great amount of patience.
Eh, it's not so bad with the 7960s. A bit of a pain, but the high-quality hardware makes it worth it.
The 7940s? Yeah, I wouldn't touch that.
-- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On Wed, Mar 20, 2013 at 8:06 AM, Mark R Lindsey <lindsey at e-c-group.com>wrote:
The lack of support for modern features -- Line State Monitoring, Feature Key Synchronization, Shared Lines / Shared Call Appearance, N-Way conferencing -- have convinced me that the best thing to do with a Cisco 79x0 phone is to Ebay them to someone using Call Manager.
Then buy a modern SIP phone.
This is our company policy. -- Carlos Alvarez TelEvolve 602-889-3003
----- Original Message -----
From: "Carlos Alvarez" <carlos at televolve.com>
79x0 phone is to Ebay them to someone using Call Manager.
Then buy a modern SIP phone.
This is our company policy.
Ok, so what *is* a modern SIP phone set? Polycom? The big fancy AAstra? Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
On Wed, Mar 20, 2013 at 8:27 AM, Jay Ashworth <jra at baylink.com> wrote:
Ok, so what *is* a modern SIP phone set?
Polycom? The big fancy AAstra?
Sure, those probably qualify. We currently recommend the Cisco SPA series and Grandstream; we don't recommend but will support Polycom. The one on my desk currently is a GXP2200 and I rather like it. -- Carlos Alvarez TelEvolve 602-889-3003
On Wed, 20 Mar 2013, Carlos Alvarez wrote:
On Wed, Mar 20, 2013 at 8:27 AM, Jay Ashworth <jra at baylink.com> wrote:
Ok, so what *is* a modern SIP phone set?
Polycom? ?The big fancy AAstra?
Sure, those probably qualify. ?We currently recommend the Cisco SPA series and Grandstream; we don't recommend but will support Polycom. ?The one on my desk currently is a GXP2200 and I rather like it.
We like Polycom as it integrates with Broadsoft nicely. Con: Expensive. We have been testing Yealink and they seem like a nice phone that just works. I have a T28-P next to me. Con: The manufacturer name of the phone sounds cheap. We would buy in bulk and get them rebadged with a different name if we follow through with them. matt
-- Carlos Alvarez TelEvolve 602-889-3003
On Wed, Mar 20, 2013 at 9:18 AM, Matt Yaklin <myaklin at g4.net> wrote:
We like Polycom as it integrates with Broadsoft nicely. Con: Expensive.
We don't run Broadsoft, so no big deal for us. Aside from cost, we really hated dealing with Polycom provisioning and boot times (yeah, they've improved somewhat over the years).
We have been testing Yealink and they seem like a nice phone that just works. I have a T28-P next to me. Con: The manufacturer name of the phone sounds cheap. We would buy in bulk and get them rebadged with a different name if we follow through with them.
I'd recommend a trial of the latest Grandstreams if you're considering a low-cost phone line. Customer acceptance has been extremely positive with them, and like I said, it's what I have on my desk, and I could grab anything I want. -- Carlos Alvarez TelEvolve 602-889-3003
We have over 2000 installations of yealink phones for the past one year and a half. They are amazing! Stable, feature rich, durable and nice finish. Forget about the name thing...! Siwangu Sent from my BlackBerry? smartphone -----Original Message----- From: Carlos Alvarez <carlos at televolve.com> Sender: voiceops-bounces at voiceops.orgDate: Wed, 20 Mar 2013 09:24:29 To: <voiceops at voiceops.org> Subject: Re: [VoiceOps] What is a Modern SIP Phone? _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
I find the Yealinks good for one thing...target practice. I've never in my life run into a more buggy unreliable phone. One order we had 20% of the phones were dead right out of the box. David Thompson Network Services Support Technician (O) 858.357.8794 (F) 858-225-1882 (E) david.thompson at vintalk.com (W) www.vintalk.com -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of svmgata at sihebs.co.tz Sent: Wednesday, March 20, 2013 09:36 To: Carlos Alvarez; voiceops-bounces at voiceops.org; voiceops at voiceops.org Subject: Re: [VoiceOps] What is a Modern SIP Phone? We have over 2000 installations of yealink phones for the past one year and a half. They are amazing! Stable, feature rich, durable and nice finish. Forget about the name thing...! Siwangu Sent from my BlackBerry(r) smartphone -----Original Message----- From: Carlos Alvarez <carlos at televolve.com> Sender: voiceops-bounces at voiceops.orgDate: Wed, 20 Mar 2013 09:24:29 To: <voiceops at voiceops.org> Subject: Re: [VoiceOps] What is a Modern SIP Phone? _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
----- Original Message -----
From: "Matt Yaklin" <myaklin at g4.net>
We like Polycom as it integrates with Broadsoft nicely. Con: Expensive.
I'm at the other end of the market from you, so I can buy my Poly's used; I generally pay about $40-60 for a 601, and I like the 601; easy phone to sell to office people, cause it works like a phone. Bit harder to config, though. Cheers, - jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
Grandstream? Have they somehow gotten exponentially better in the last 3 years or something? All I remember of them the last time I tried them is preferring 2 cans and a string... -Blake On Wed, Mar 20, 2013 at 10:39 AM, Carlos Alvarez <carlos at televolve.com>wrote:
On Wed, Mar 20, 2013 at 8:27 AM, Jay Ashworth <jra at baylink.com> wrote:
Ok, so what *is* a modern SIP phone set?
Polycom? The big fancy AAstra?
Sure, those probably qualify. We currently recommend the Cisco SPA series and Grandstream; we don't recommend but will support Polycom. The one on my desk currently is a GXP2200 and I rather like it.
-- Carlos Alvarez TelEvolve 602-889-3003
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On Wed, Mar 20, 2013 at 9:25 AM, Blake Dunlap <ikiris at gmail.com> wrote:
Grandstream?
Have they somehow gotten exponentially better in the last 3 years or something?
Yes, exactly that. Huge change.
All I remember of them the last time I tried them is preferring 2 cans and a string...
Same here. They convinced me to accept a few demos at no charge, and they are decent. Heavy on features and low on cost, with good quality. Maybe not Polycom quality sound, but we're talking 1/5th the price in some cases. An HD phone with 24-button BLF costs $100-ish. They aren't perfect. They aren't "the best." But when you talk about charging five times for something a little better, you really have to look closely at the benefits. -- Carlos Alvarez TelEvolve 602-889-3003
----- Original Message -----
From: "Carlos Alvarez" <carlos at televolve.com>
They aren't perfect. They aren't "the best." But when you talk about charging five times for something a little better, you really have to look closely at the benefits.
No, we have to look at all. "They don't suck near as bad as they used to" is the cue line there; thanks Carlos. Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
----- Original Message -----
From: "Blake Dunlap" <ikiris at gmail.com>
Grandstream?
Have they somehow gotten exponentially better in the last 3 years or something?
All I remember of them the last time I tried them is preferring 2 cans and a string...
Ok, see, now that was my response as well... and someone else mentioned Cisco, the avoiding of which was what I though we started with on this subthread. :-) Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
Wonder if the SPA's are officially Belkin devices now given their Linksys/Sipura heritage: http://news.cnet.com/8301-1001_3-57565748-92/belkin-buying-linksys/ From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Blake Dunlap Sent: Wednesday, March 20, 2013 12:26 PM To: Carlos Alvarez Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] What is a Modern SIP Phone? Grandstream? Have they somehow gotten exponentially better in the last 3 years or something? All I remember of them the last time I tried them is preferring 2 cans and a string... -Blake On Wed, Mar 20, 2013 at 10:39 AM, Carlos Alvarez <carlos at televolve.com> wrote: On Wed, Mar 20, 2013 at 8:27 AM, Jay Ashworth <jra at baylink.com> wrote: Ok, so what *is* a modern SIP phone set? Polycom? The big fancy AAstra? Sure, those probably qualify. We currently recommend the Cisco SPA series and Grandstream; we don't recommend but will support Polycom. The one on my desk currently is a GXP2200 and I rather like it. -- Carlos Alvarez TelEvolve 602-889-3003 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
Cisco has been proudly branding them as Cisco for a few years. I'd be shocked if those came with the purchase. On 03/20/2013 03:54 PM, Scott Berkman wrote:
Wonder if the SPA's are officially Belkin devices now given their Linksys/Sipura heritage:
http://news.cnet.com/8301-1001_3-57565748-92/belkin-buying-linksys/
*From:*voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Blake Dunlap *Sent:* Wednesday, March 20, 2013 12:26 PM *To:* Carlos Alvarez *Cc:* voiceops at voiceops.org *Subject:* Re: [VoiceOps] What is a Modern SIP Phone?
Grandstream?
Have they somehow gotten exponentially better in the last 3 years or something?
All I remember of them the last time I tried them is preferring 2 cans and a string...
-Blake
On Wed, Mar 20, 2013 at 10:39 AM, Carlos Alvarez <carlos at televolve.com <mailto:carlos at televolve.com>> wrote:
On Wed, Mar 20, 2013 at 8:27 AM, Jay Ashworth <jra at baylink.com <mailto:jra at baylink.com>> wrote:
Ok, so what *is* a modern SIP phone set?
Polycom? The big fancy AAstra?
Sure, those probably qualify. We currently recommend the Cisco SPA series and Grandstream; we don't recommend but will support Polycom. The one on my desk currently is a GXP2200 and I rather like it.
--
Carlos Alvarez
TelEvolve
602-889-3003 <tel:602-889-3003>
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
I emailed Linksys and Belkin to confirm that the SPA's had left the building; neither company would take ownership of the line. IMHO, Cisco is gonna hang on to the SPA phones, but that's just my opinion, no facts to back that up. When we talk about modern SIP phones here at 2600hz, we really like the vvx polycoms and the yealinks (trying to get my hands on the 4x series of yealink handsets now). We try to be as agnostic as possible about the handsets, but there's a couple things that I personally dislike about Cisco's (specifically their questionable SIP implementations and their somewhat bizarre security practices). In short, a modern SIP phone is one that speaks SIP in an RFC compliant manner and plays nicely with most hardware. IMHO, and this is strictly personal opinion, the Cisco 79x0 series is not something I would include in this category. Cheers, Joshua Joshua Goldbard VP of Marketing, 2600hz 116 Natoma Street, Floor 2 San Francisco, CA, 94104 415.886.7923 | j at 2600hz.com<mailto:j at 2600hz.com> On Mar 20, 2013, at 12:54 PM, Scott Berkman <scott at sberkman.net<mailto:scott at sberkman.net>> wrote: Wonder if the SPA?s are officially Belkin devices now given their Linksys/Sipura heritage: http://news.cnet.com/8301-1001_3-57565748-92/belkin-buying-linksys/ From: voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org> [mailto:voiceops-bounces at voiceops.org<mailto:bounces at voiceops.org>] On Behalf Of Blake Dunlap Sent: Wednesday, March 20, 2013 12:26 PM To: Carlos Alvarez Cc: voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: Re: [VoiceOps] What is a Modern SIP Phone? Grandstream? Have they somehow gotten exponentially better in the last 3 years or something? All I remember of them the last time I tried them is preferring 2 cans and a string... -Blake On Wed, Mar 20, 2013 at 10:39 AM, Carlos Alvarez <carlos at televolve.com<mailto:carlos at televolve.com>> wrote: On Wed, Mar 20, 2013 at 8:27 AM, Jay Ashworth <jra at baylink.com<mailto:jra at baylink.com>> wrote: Ok, so what *is* a modern SIP phone set? Polycom? The big fancy AAstra? Sure, those probably qualify. We currently recommend the Cisco SPA series and Grandstream; we don't recommend but will support Polycom. The one on my desk currently is a GXP2200 and I rather like it. -- Carlos Alvarez TelEvolve 602-889-3003<tel:602-889-3003> _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
On Mar 20, 2013, at 16:06 , Joshua Goldbard <j at 2600hz.com> wrote:
In short, a modern SIP phone is one that speaks SIP in an RFC compliant manner and plays nicely with most hardware. IMHO, and this is strictly personal opinion, the Cisco 79x0 series is not something I would include in this category.
If all you need is basic calling with G.711, INVITE> 180< 200< ACK> then lots of phones will do it. Unfortunately, that's where many of the vendors seem to complete their testing. The "plays nicely with most hardware" part is quite a loaded clause! I'd expand that to say that you need your SIP phones to be compatible with the features of YOUR feature server; the trouble spots all relate to the important PBX-replacement features, such as: -- Shared Call Appearance / Shared Lines -- Busy Lamp Field / Line State Monitoring -- Feature Key (DND, CF, etc.) Synchronization -- Message Waiting Indicator -- N-Way Conferencing -- Call Hold Style (mentioned only because The Cisco 7960s still use RFC2543 call hold, IIRC). -- 100rel support -- Proper handling 183 followed by 180 response But here's the problem with looking for standards compliance: some of the important SIP features have never made it to standards-track RFCs. The process often seems to go like this: (1) Big customer wants something (2) Big vendor wants Big Customer's money (3) Big vendor implements proprietary version of feature (4) Customer Satisfied (5) Big vendor publishes IETF draft (6) IETF draft expires (7) Big vendor 2 wants Big Customer. Also implements expired IETF draft. The process can be a lot worse if Big Vendor skips steps 5 and 6, just leaving their implementation as proprietary and barely published. Or the process can go better, where a real standard comes out of it. Sometimes, the IETF standard actually does precede a commercial implementation. (There are some interesting points buried in this area about the fundamental "end to end argument in system design" and how that works for dynamically negotiated features. We'd all like to believe that we humans could specify standards and the two endpoints could negotiate the best common set of compatible features on each individual call. But we haven't proven that it's even possible.) When you're evaluating a SIP access device -- phone or PBX -- you're working in this weird milieux of non-standardized-yet-important features, for which interop testing is the only compliance that matters.
mark at ecg.co +12293160013 http://ecg.co/lindsey
I'd say two things: 1. Anything that passes your interop test is acceptable 2. If you don't test it, it is broken David From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Mark R Lindsey Sent: Wednesday, March 20, 2013 14:08 To: Joshua Goldbard Cc: <voiceops at voiceops.org> Subject: Re: [VoiceOps] What is a Modern SIP Phone? On Mar 20, 2013, at 16:06 , Joshua Goldbard <j at 2600hz.com<mailto:j at 2600hz.com>> wrote: In short, a modern SIP phone is one that speaks SIP in an RFC compliant manner and plays nicely with most hardware. IMHO, and this is strictly personal opinion, the Cisco 79x0 series is not something I would include in this category. If all you need is basic calling with G.711, INVITE> 180< 200< ACK> then lots of phones will do it. Unfortunately, that's where many of the vendors seem to complete their testing. The "plays nicely with most hardware" part is quite a loaded clause! I'd expand that to say that you need your SIP phones to be compatible with the features of YOUR feature server; the trouble spots all relate to the important PBX-replacement features, such as: -- Shared Call Appearance / Shared Lines -- Busy Lamp Field / Line State Monitoring -- Feature Key (DND, CF, etc.) Synchronization -- Message Waiting Indicator -- N-Way Conferencing -- Call Hold Style (mentioned only because The Cisco 7960s still use RFC2543 call hold, IIRC). -- 100rel support -- Proper handling 183 followed by 180 response But here's the problem with looking for standards compliance: some of the important SIP features have never made it to standards-track RFCs. The process often seems to go like this: (1) Big customer wants something (2) Big vendor wants Big Customer's money (3) Big vendor implements proprietary version of feature (4) Customer Satisfied (5) Big vendor publishes IETF draft (6) IETF draft expires (7) Big vendor 2 wants Big Customer. Also implements expired IETF draft. The process can be a lot worse if Big Vendor skips steps 5 and 6, just leaving their implementation as proprietary and barely published. Or the process can go better, where a real standard comes out of it. Sometimes, the IETF standard actually does precede a commercial implementation. (There are some interesting points buried in this area about the fundamental "end to end argument in system design" and how that works for dynamically negotiated features. We'd all like to believe that we humans could specify standards and the two endpoints could negotiate the best common set of compatible features on each individual call. But we haven't proven that it's even possible.) When you're evaluating a SIP access device -- phone or PBX -- you're working in this weird milieux of non-standardized-yet-important features, for which interop testing is the only compliance that matters.
mark at ecg.co<mailto:mark at ecg.co> +12293160013 http://ecg.co/lindsey
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
----- Original Message -----
From: "Mark R Lindsey" <lindsey at e-c-group.com>
(There are some interesting points buried in this area about the fundamental "end to end argument in system design" and how that works for dynamically negotiated features. We'd all like to believe that we humans could specify standards and the two endpoints could negotiate the best common set of compatible features on each individual call. But we haven't proven that it's even possible.)
When you're evaluating a SIP access device -- phone or PBX -- you're working in this weird milieux of non-standardized-yet-important features, for which interop testing is the only compliance that matters.
I love Starting Conversations. :-) At that point, Mark, I should probably remind everyone why Interop got started. I went to a very early one, at the Georgia World Congress Center, and let me tell you, it was pretty impressive back then. I don't see why someone isn't doing a well publicized shootout at an annual event of some type, where each PBX vendor brings along their best people, and each phone vendor brings *their* best people, and a set of independent VoIP/PBX guys judge a shootout. Bring programming talent along and have a hackathon between first day and last day, and see how much you can fix. This isn't... rocket science. (NASA has a big Cisco install, presumably CM :-). Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
-----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Jay Ashworth Sent: Thursday, March 21, 2013 1:42 PM To: voiceops at voiceops.org Subject: Re: [VoiceOps] What is a Modern SIP Phone? This isn't... rocket science. (NASA has a big Cisco install, presumably CM :-). I'm often heard to say that, "I live in Houston. I know rocket science when I see it." Michael
----- Original Message -----
From: "Michael Graves" <mgraves at mstvp.com>
I'm often heard to say that, "I live in Houston. I know rocket science when I see it."
Hee. Dragging this back on topic by force, it seems the Yealink phones may be being built by Cortelco, possibly even in the US, if this thread is to be believed"" http://www.pbxinaflash.com/community/index.php?threads/under-20-sip-phones.1... Cheers, -- jra -- Jay R. Ashworth Baylink jra at baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274
I also have the gxp2200 on my desk. I feel like its too many extra steps to make a call compared to past non android based ip desk phones. I'm a big fan of the acrobits sip client on my iOS device though. On Mar 20, 2013, at 11:39 AM, Carlos Alvarez <carlos at televolve.com> wrote:
On Wed, Mar 20, 2013 at 8:27 AM, Jay Ashworth <jra at baylink.com> wrote:
Ok, so what *is* a modern SIP phone set?
Polycom? The big fancy AAstra?
Sure, those probably qualify. We currently recommend the Cisco SPA series and Grandstream; we don't recommend but will support Polycom. The one on my desk currently is a GXP2200 and I rather like it.
-- Carlos Alvarez TelEvolve 602-889-3003
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
On Wed, Mar 20, 2013 at 9:26 AM, Colin Brown <zavoid at gmail.com> wrote:
I also have the gxp2200 on my desk. I feel like its too many extra steps to make a call compared to past non android based ip desk phones.
I don't understand that. There's only one extra step; press a button to wake the display, then just dial like any other. -- Carlos Alvarez TelEvolve 602-889-3003
participants (17)
-
abaird＠telesphere.com -
abalashov＠evaristesys.com -
admin＠marcoteixeira.com -
carlos＠televolve.com -
David.Hiers＠adp.com -
David.Thompson＠vintalk.com -
faisal＠snappydsl.net -
ikiris＠gmail.com -
j＠2600hz.com -
jra＠baylink.com -
lindsey＠e-c-group.com -
mgraves＠mstvp.com -
myaklin＠g4.net -
paul＠timmins.net -
scott＠sberkman.net -
svmgata＠sihebs.co.tz -
zavoid＠gmail.com