VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
October 2015
- 49 participants
- 97 messages
Cisco 7941 SIP
by anakaoka@trinet-hi.com
Maybe Polycom will give you a discount for replacing a Cisco.
Aryn H. K. Nakaoka
anakaoka at trinet-hi.com
Direct: 808.356.2901
Fax : 808.356.2919
Tri-net Solutions
733 Bishop St. #1170
Honolulu, HI 96813
http://www.trinet-hi.com
https://twitter.com/AlohaTone
Aloha Tone PBX <https://www.youtube.com/watch?v=96YWPY9wCeU>
https://www.youtube.com/watch?v=96YWPY9wCeU <http://youtu.be/27v2wbnFIDs>
Aloha Tone (HA) High Availability <http://youtu.be/rJsr4k0RBH8>
http://youtu.be/rJsr4k0RBH8
CONFIDENTIALITY NOTICE: The information contained in this email and any
attachments may be privileged, confidential and protected from disclosure.
Any disclosure, distribution or copying of this email or any attachments by
persons or entities other than the intended recipient is prohibited. If you
have received this email in error, please notify the sender immediately by
replying to the message and deleting this email and any attachments from
your system. Thank you for your cooperation.
On Wed, Oct 7, 2015 at 6:11 AM, Aryn Nakaoka 808.356.2901 <
anakaoka at trinet-hi.com> wrote:
> You can get Polycom phones VVX 101/201 probably for less than the labor
> hours you will lose on support, not to mention the marketing on that
> opportunity. I'm sure management would highly consider it.
>
>
>
>
>
> Aryn H. K. Nakaoka
> anakaoka at trinet-hi.com
>
> Direct: 808.356.2901
> Fax : 808.356.2919
>
> Tri-net Solutions
> 733 Bishop St. #1170
> Honolulu, HI 96813
> http://www.trinet-hi.com
>
> https://twitter.com/AlohaTone
>
> Aloha Tone PBX <https://www.youtube.com/watch?v=96YWPY9wCeU>
> https://www.youtube.com/watch?v=96YWPY9wCeU <http://youtu.be/27v2wbnFIDs>
>
> Aloha Tone (HA) High Availability <http://youtu.be/rJsr4k0RBH8>
> http://youtu.be/rJsr4k0RBH8
>
> CONFIDENTIALITY NOTICE: The information contained in this email and any
> attachments may be privileged, confidential and protected from disclosure.
> Any disclosure, distribution or copying of this email or any attachments by
> persons or entities other than the intended recipient is prohibited. If you
> have received this email in error, please notify the sender immediately by
> replying to the message and deleting this email and any attachments from
> your system. Thank you for your cooperation.
>
>
>
>
>
>
>
> On Tue, Oct 6, 2015 at 5:03 PM, Peter E <peeip989 at gmail.com> wrote:
>
>> You're preaching to the choir, Mark. As a company, for BYOD, we take a
>> stance of, we'll supply the SIP credentials but we won't support the
>> device. But anyone in an operations role knows what that really means -- do
>> whatever it takes to get them working and happy.
>>
>> I'll share your comments with those that believe the opposite about BYOD
>> and scale. It will make for an interesting debate.
>>
>>
>>
>>
>>
>> On Oct 6, 2015, at 22:52, Mark Lindsey <lindsey at e-c-group.com> wrote:
>>
>> 1. In Hosted PBX, accommodating new, non-productized devices that the
>> customer just has to keep is the price you pay to enjoy slow growth
>> (because the engineering effort for the customer is immense), poor
>> reliability (because you can test much less), and an unsupportable customer
>> deployments (because the support team isn't equipped to support this
>> "product").
>>
>> 2. In Hosted PBX, the demarc is the audible voice on the speaker and the
>> input to the microphone. Supporting random devices the customer brings you
>> makes it impossible for you to fulfill your end of the bargain: make this
>> voice stuff work every time for every call.
>>
>> 3. The best thing to do with a customer's old device is trade in credit
>> then liquidate.
>>
>> 4. Cisco 79xx SIP has gone back and forth on symmetric sip signaling over
>> the past few decades. But generally, when nat is involved, the sip phone
>> has to do symmetric sip ports -- I.e., it must use the same port numbers
>> for both sending sip and receiving sip. (And when carrier SBCs are
>> involved, it needs to use the same port number for all sip transactions,
>> not just those related to direct call control).
>>
>> But I remember Cisco 79xx configs having a "nat_enable" or similar flag
>> that actually enable the symmetric sip.
>>
>> mailto:mark at ecg.co <mark at ecg.co>
>> tel:+1-229-316-0013 <+1-229-316-0013> http://ecg.co/lindsey
>>
>> On Oct 6, 2015, at 17:10, Pete E <peeip989 at gmail.com> wrote:
>>
>> Greetings Voice Operators,
>>
>>
>> We have an interesting (code word for annoying) challenge that we've
>> never dealt with before, probably because we don't do much with Cisco
>> phones. We have a new customer coming on who wants to keep their very old
>> Cisco 7941 phones. They have a few offices and the phones work as expected
>> behind an Edgemarc. However, they also have 100+ home users, and that's
>> where the issue comes in.
>>
>> Apparently Cisco introduced a security "feature" where they create the
>> session using a random high numbered port (e.g. 49123) but in the Via
>> header, they say to respond to *private IP, port 5060*. So when the SBC
>> sees the private address it assumes it is being NAT'd through a firewall
>> and replies back to *public IP, port 49123*. What we're seeing is that
>> the home router passes the response back to *private IP, port 49123*,
>> which the phone doesn't accept (because it wants it on 5060) and the
>> REGISTER fails.
>>
>> As you know most home routers are poor at handling ALG (and we've tested
>> and found they are equally bad at handling this scenario). We (and the
>> customer) don't want to troubleshoot 100+ individual home routers.
>>
>> We haven't found a way to turn off this really awesome "feature" so we're
>> trying to find other solutions. Anyone been through this and have any
>> suggestions?
>>
>>
>> Thanks,
>> Pete
>>
>> _______________________________________________
>> 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
>>
>>
>
Oct. 7, 2015
Cisco 7941 SIP
by anakaoka@trinet-hi.com
You can get Polycom phones VVX 101/201 probably for less than the labor
hours you will lose on support, not to mention the marketing on that
opportunity. I'm sure management would highly consider it.
Aryn H. K. Nakaoka
anakaoka at trinet-hi.com
Direct: 808.356.2901
Fax : 808.356.2919
Tri-net Solutions
733 Bishop St. #1170
Honolulu, HI 96813
http://www.trinet-hi.com
https://twitter.com/AlohaTone
Aloha Tone PBX <https://www.youtube.com/watch?v=96YWPY9wCeU>
https://www.youtube.com/watch?v=96YWPY9wCeU <http://youtu.be/27v2wbnFIDs>
Aloha Tone (HA) High Availability <http://youtu.be/rJsr4k0RBH8>
http://youtu.be/rJsr4k0RBH8
CONFIDENTIALITY NOTICE: The information contained in this email and any
attachments may be privileged, confidential and protected from disclosure.
Any disclosure, distribution or copying of this email or any attachments by
persons or entities other than the intended recipient is prohibited. If you
have received this email in error, please notify the sender immediately by
replying to the message and deleting this email and any attachments from
your system. Thank you for your cooperation.
On Tue, Oct 6, 2015 at 5:03 PM, Peter E <peeip989 at gmail.com> wrote:
> You're preaching to the choir, Mark. As a company, for BYOD, we take a
> stance of, we'll supply the SIP credentials but we won't support the
> device. But anyone in an operations role knows what that really means -- do
> whatever it takes to get them working and happy.
>
> I'll share your comments with those that believe the opposite about BYOD
> and scale. It will make for an interesting debate.
>
>
>
>
>
> On Oct 6, 2015, at 22:52, Mark Lindsey <lindsey at e-c-group.com> wrote:
>
> 1. In Hosted PBX, accommodating new, non-productized devices that the
> customer just has to keep is the price you pay to enjoy slow growth
> (because the engineering effort for the customer is immense), poor
> reliability (because you can test much less), and an unsupportable customer
> deployments (because the support team isn't equipped to support this
> "product").
>
> 2. In Hosted PBX, the demarc is the audible voice on the speaker and the
> input to the microphone. Supporting random devices the customer brings you
> makes it impossible for you to fulfill your end of the bargain: make this
> voice stuff work every time for every call.
>
> 3. The best thing to do with a customer's old device is trade in credit
> then liquidate.
>
> 4. Cisco 79xx SIP has gone back and forth on symmetric sip signaling over
> the past few decades. But generally, when nat is involved, the sip phone
> has to do symmetric sip ports -- I.e., it must use the same port numbers
> for both sending sip and receiving sip. (And when carrier SBCs are
> involved, it needs to use the same port number for all sip transactions,
> not just those related to direct call control).
>
> But I remember Cisco 79xx configs having a "nat_enable" or similar flag
> that actually enable the symmetric sip.
>
> mailto:mark at ecg.co <mark at ecg.co>
> tel:+1-229-316-0013 <+1-229-316-0013> http://ecg.co/lindsey
>
> On Oct 6, 2015, at 17:10, Pete E <peeip989 at gmail.com> wrote:
>
> Greetings Voice Operators,
>
>
> We have an interesting (code word for annoying) challenge that we've never
> dealt with before, probably because we don't do much with Cisco phones. We
> have a new customer coming on who wants to keep their very old Cisco 7941
> phones. They have a few offices and the phones work as expected behind an
> Edgemarc. However, they also have 100+ home users, and that's where the
> issue comes in.
>
> Apparently Cisco introduced a security "feature" where they create the
> session using a random high numbered port (e.g. 49123) but in the Via
> header, they say to respond to *private IP, port 5060*. So when the SBC
> sees the private address it assumes it is being NAT'd through a firewall
> and replies back to *public IP, port 49123*. What we're seeing is that
> the home router passes the response back to *private IP, port 49123*,
> which the phone doesn't accept (because it wants it on 5060) and the
> REGISTER fails.
>
> As you know most home routers are poor at handling ALG (and we've tested
> and found they are equally bad at handling this scenario). We (and the
> customer) don't want to troubleshoot 100+ individual home routers.
>
> We haven't found a way to turn off this really awesome "feature" so we're
> trying to find other solutions. Anyone been through this and have any
> suggestions?
>
>
> Thanks,
> Pete
>
> _______________________________________________
> 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
>
>
Oct. 7, 2015
Lack of Quality Industry-wide
by anakaoka@trinet-hi.com
Is there a centralized report of Tier 1 ISPs? It would be great to know who
has the best performance... I think mass data like that would be difficult
to analyze.
Something similar to http://www.internettrafficreport.com/ - not sure what
this really shows...
Aryn H. K. Nakaoka
anakaoka at trinet-hi.com
Direct: 808.356.2901
Fax : 808.356.2919
Tri-net Solutions
733 Bishop St. #1170
Honolulu, HI 96813
http://www.trinet-hi.com
https://twitter.com/AlohaTone
Aloha Tone PBX <https://www.youtube.com/watch?v=96YWPY9wCeU>
https://www.youtube.com/watch?v=96YWPY9wCeU <http://youtu.be/27v2wbnFIDs>
Aloha Tone (HA) High Availability <http://youtu.be/rJsr4k0RBH8>
http://youtu.be/rJsr4k0RBH8
CONFIDENTIALITY NOTICE: The information contained in this email and any
attachments may be privileged, confidential and protected from disclosure.
Any disclosure, distribution or copying of this email or any attachments by
persons or entities other than the intended recipient is prohibited. If you
have received this email in error, please notify the sender immediately by
replying to the message and deleting this email and any attachments from
your system. Thank you for your cooperation.
On Tue, Oct 6, 2015 at 5:14 PM, Ivan Kovacevic <
ivan.kovacevic at startelecom.ca> wrote:
>
>
> What would help, and what has been done in other industries (think JD
> Power, Gartner? ok maybe not Gartner) is to have this data aggregated and
> available to view as a part of an industry report.
>
>
>
> So that you can look at Cheap-o-voip.com and say?. ?The rates sure look
> good, but their PDD, completion, etc are dismal, I?ll pass?? That would
> quickly help separate the good from the bad and hopefully drive the
> industry overall to improve those key metrics. I would pay for that sort of
> report, just to avoid wasting time on duds. Or? I would be open to sharing
> data, either as summary data or sanitized CDRs to help drive that sort of
> database.
>
>
>
> Now? if we could only agree on what the key metrics are... it seems that
> everyone has a different measuring stick.
>
>
>
> Best Regards,
>
>
>
> Ivan Kovacevic
>
> Vice President, Client Services
>
> Star Telecom | www.startelecom.ca | SIP Based Services for Contact
> Centers
>
>
>
> *From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Pete
> E
> *Sent:* Tuesday, October 06, 2015 5:14 PM
> *To:* Peter Beckman <beckman at angryox.com>
> *Cc:* VoiceOps <voiceops at voiceops.org>
> *Subject:* Re: [VoiceOps] Lack of Quality Industry-wide
>
>
>
> Ditto. We do the same, but it doesn't get us very far. We've recently
> fired two carriers for performance.
>
>
>
> On Tue, Oct 6, 2015 at 12:34 PM, Peter Beckman <beckman at angryox.com>
> wrote:
>
> That's a great story Anthony! It's similar to my issues. I already do this
> for termination. DID and SMS issues are more difficult to manage. And the
> issues you have with one carrier that drives you to mass port your DIDs
> that you hope to escape start happening with your new carrier.
>
> I wish carriers would have the same level of visibility in their service
> and infrastructure as you seemed to have with Intellisight, and then fix
> the problems proactively when they find them.
>
> "What gets measured gets managed."
>
> So true. So elusive in this business.
>
> Beckman
>
> On Tue, 6 Oct 2015, Anthony Orlando wrote:
>
> You are correct Peter. It's a constant struggle. For years I used a
> product from Empirix called Intelisight. It gave us the ability to
> monitor carriers (and other managed objects) with defined sets of KPI's.
> Once I saw a carrier have issues (PDD, quality, excessive 503's) I used
> to call them and tell them they had a problem. Hours or days later they
> would resolve. I got away from that practice and just routed around
> them. Funny how they notice that. Once the issue was resolved I put
> them in a penalty box and slowly added traffic. Once they realized I was
> measuring their performance and there would be financial repercussions
> it's amazing how the quality of their under lying carriers improved. My
> carrier ticket count dropped by 25-30%.
>
>
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com
> http://www.angryox.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
>
>
Oct. 7, 2015
Lack of Quality Industry-wide
by ksuriyaarachchi@alteva.com
With DIDs migrating to VoIP could ENUM registry be the solution to this issue?
As predicted if PSTN shuts down there will only peer to peer routes.
Kumudu Suriyaarachchi ksuriyaarachchi at alteva.com<mailto:ksuriyaarachchi at alteva.com>
P 484.534.4427
[Alteva-Logo-horizontal]
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Ivan Kovacevic
Sent: Tuesday, October 06, 2015 11:15 PM
To: Pete E; Peter Beckman
Cc: VoiceOps
Subject: Re: [VoiceOps] Lack of Quality Industry-wide
What would help, and what has been done in other industries (think JD Power, Gartner? ok maybe not Gartner) is to have this data aggregated and available to view as a part of an industry report.
So that you can look at Cheap-o-voip.com and say?. ?The rates sure look good, but their PDD, completion, etc are dismal, I?ll pass?? That would quickly help separate the good from the bad and hopefully drive the industry overall to improve those key metrics. I would pay for that sort of report, just to avoid wasting time on duds. Or? I would be open to sharing data, either as summary data or sanitized CDRs to help drive that sort of database.
Now? if we could only agree on what the key metrics are... it seems that everyone has a different measuring stick.
Best Regards,
Ivan Kovacevic
Vice President, Client Services
Star Telecom | www.startelecom.ca<http://www.startelecom.ca/> | SIP Based Services for Contact Centers
From: VoiceOps [mailto:voiceops-bounces at voiceops.org<mailto:voiceops-bounces at voiceops.org>] On Behalf Of Pete E
Sent: Tuesday, October 06, 2015 5:14 PM
To: Peter Beckman <beckman at angryox.com<mailto:beckman at angryox.com>>
Cc: VoiceOps <voiceops at voiceops.org<mailto:voiceops at voiceops.org>>
Subject: Re: [VoiceOps] Lack of Quality Industry-wide
Ditto. We do the same, but it doesn't get us very far. We've recently fired two carriers for performance.
On Tue, Oct 6, 2015 at 12:34 PM, Peter Beckman <beckman at angryox.com<mailto:beckman at angryox.com>> wrote:
That's a great story Anthony! It's similar to my issues. I already do this
for termination. DID and SMS issues are more difficult to manage. And the
issues you have with one carrier that drives you to mass port your DIDs
that you hope to escape start happening with your new carrier.
I wish carriers would have the same level of visibility in their service
and infrastructure as you seemed to have with Intellisight, and then fix
the problems proactively when they find them.
"What gets measured gets managed."
So true. So elusive in this business.
Beckman
On Tue, 6 Oct 2015, Anthony Orlando wrote:
You are correct Peter. It's a constant struggle. For years I used a
product from Empirix called Intelisight. It gave us the ability to
monitor carriers (and other managed objects) with defined sets of KPI's.
Once I saw a carrier have issues (PDD, quality, excessive 503's) I used
to call them and tell them they had a problem. Hours or days later they
would resolve. I got away from that practice and just routed around
them. Funny how they notice that. Once the issue was resolved I put
them in a penalty box and slowly added traffic. Once they realized I was
measuring their performance and there would be financial repercussions
it's amazing how the quality of their under lying carriers improved. My
carrier ticket count dropped by 25-30%.
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com<mailto:beckman at angryox.com> http://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org>
https://puck.nether.net/mailman/listinfo/voiceops
This communication (including any attachments) may contain privileged or confidential information of Alteva and is intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, you should notify the author and delete this communication from your system, including any attachments. Any disclosure, copying, saving or distribution of this communication, or the taking of any action based on it, is strictly prohibited. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Alteva.
Oct. 7, 2015
Lack of Quality Industry-wide
by ivan.kovacevic@startelecom.ca
What would help, and what has been done in other industries (think JD
Power, Gartner? ok maybe not Gartner) is to have this data aggregated and
available to view as a part of an industry report.
So that you can look at Cheap-o-voip.com and say?. ?The rates sure look
good, but their PDD, completion, etc are dismal, I?ll pass?? That would
quickly help separate the good from the bad and hopefully drive the
industry overall to improve those key metrics. I would pay for that sort of
report, just to avoid wasting time on duds. Or? I would be open to sharing
data, either as summary data or sanitized CDRs to help drive that sort of
database.
Now? if we could only agree on what the key metrics are... it seems that
everyone has a different measuring stick.
Best Regards,
Ivan Kovacevic
Vice President, Client Services
Star Telecom | www.startelecom.ca | SIP Based Services for Contact Centers
*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Pete
E
*Sent:* Tuesday, October 06, 2015 5:14 PM
*To:* Peter Beckman <beckman at angryox.com>
*Cc:* VoiceOps <voiceops at voiceops.org>
*Subject:* Re: [VoiceOps] Lack of Quality Industry-wide
Ditto. We do the same, but it doesn't get us very far. We've recently fired
two carriers for performance.
On Tue, Oct 6, 2015 at 12:34 PM, Peter Beckman <beckman at angryox.com> wrote:
That's a great story Anthony! It's similar to my issues. I already do this
for termination. DID and SMS issues are more difficult to manage. And the
issues you have with one carrier that drives you to mass port your DIDs
that you hope to escape start happening with your new carrier.
I wish carriers would have the same level of visibility in their service
and infrastructure as you seemed to have with Intellisight, and then fix
the problems proactively when they find them.
"What gets measured gets managed."
So true. So elusive in this business.
Beckman
On Tue, 6 Oct 2015, Anthony Orlando wrote:
You are correct Peter. It's a constant struggle. For years I used a
product from Empirix called Intelisight. It gave us the ability to
monitor carriers (and other managed objects) with defined sets of KPI's.
Once I saw a carrier have issues (PDD, quality, excessive 503's) I used
to call them and tell them they had a problem. Hours or days later they
would resolve. I got away from that practice and just routed around
them. Funny how they notice that. Once the issue was resolved I put
them in a penalty box and slowly added traffic. Once they realized I was
measuring their performance and there would be financial repercussions
it's amazing how the quality of their under lying carriers improved. My
carrier ticket count dropped by 25-30%.
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beckman at angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Oct. 7, 2015
Cisco 7941 SIP
by peeip989@gmail.com
You're preaching to the choir, Mark. As a company, for BYOD, we take a stance of, we'll supply the SIP credentials but we won't support the device. But anyone in an operations role knows what that really means -- do whatever it takes to get them working and happy.
I'll share your comments with those that believe the opposite about BYOD and scale. It will make for an interesting debate.
On Oct 6, 2015, at 22:52, Mark Lindsey <lindsey at e-c-group.com> wrote:
1. In Hosted PBX, accommodating new, non-productized devices that the customer just has to keep is the price you pay to enjoy slow growth (because the engineering effort for the customer is immense), poor reliability (because you can test much less), and an unsupportable customer deployments (because the support team isn't equipped to support this "product").
2. In Hosted PBX, the demarc is the audible voice on the speaker and the input to the microphone. Supporting random devices the customer brings you makes it impossible for you to fulfill your end of the bargain: make this voice stuff work every time for every call.
3. The best thing to do with a customer's old device is trade in credit then liquidate.
4. Cisco 79xx SIP has gone back and forth on symmetric sip signaling over the past few decades. But generally, when nat is involved, the sip phone has to do symmetric sip ports -- I.e., it must use the same port numbers for both sending sip and receiving sip. (And when carrier SBCs are involved, it needs to use the same port number for all sip transactions, not just those related to direct call control).
But I remember Cisco 79xx configs having a "nat_enable" or similar flag that actually enable the symmetric sip.
mailto:mark at ecg.co
tel:+1-229-316-0013 http://ecg.co/lindsey
> On Oct 6, 2015, at 17:10, Pete E <peeip989 at gmail.com> wrote:
>
> Greetings Voice Operators,
>
>
> We have an interesting (code word for annoying) challenge that we've never dealt with before, probably because we don't do much with Cisco phones. We have a new customer coming on who wants to keep their very old Cisco 7941 phones. They have a few offices and the phones work as expected behind an Edgemarc. However, they also have 100+ home users, and that's where the issue comes in.
>
> Apparently Cisco introduced a security "feature" where they create the session using a random high numbered port (e.g. 49123) but in the Via header, they say to respond to private IP, port 5060. So when the SBC sees the private address it assumes it is being NAT'd through a firewall and replies back to public IP, port 49123. What we're seeing is that the home router passes the response back to private IP, port 49123, which the phone doesn't accept (because it wants it on 5060) and the REGISTER fails.
>
> As you know most home routers are poor at handling ALG (and we've tested and found they are equally bad at handling this scenario). We (and the customer) don't want to troubleshoot 100+ individual home routers.
>
> We haven't found a way to turn off this really awesome "feature" so we're trying to find other solutions. Anyone been through this and have any suggestions?
>
>
> Thanks,
> Pete
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Oct. 7, 2015
Cisco 7941 SIP
by lindsey@e-c-group.com
1. In Hosted PBX, accommodating new, non-productized devices that the
customer just has to keep is the price you pay to enjoy slow growth
(because the engineering effort for the customer is immense), poor
reliability (because you can test much less), and an unsupportable customer
deployments (because the support team isn't equipped to support this
"product").
2. In Hosted PBX, the demarc is the audible voice on the speaker and the
input to the microphone. Supporting random devices the customer brings you
makes it impossible for you to fulfill your end of the bargain: make this
voice stuff work every time for every call.
3. The best thing to do with a customer's old device is trade in credit
then liquidate.
4. Cisco 79xx SIP has gone back and forth on symmetric sip signaling over
the past few decades. But generally, when nat is involved, the sip phone
has to do symmetric sip ports -- I.e., it must use the same port numbers
for both sending sip and receiving sip. (And when carrier SBCs are
involved, it needs to use the same port number for all sip transactions,
not just those related to direct call control).
But I remember Cisco 79xx configs having a "nat_enable" or similar flag
that actually enable the symmetric sip.
mailto:mark at ecg.co <mark at ecg.co>
tel:+1-229-316-0013 <+1-229-316-0013> http://ecg.co/lindsey
On Oct 6, 2015, at 17:10, Pete E <peeip989 at gmail.com> wrote:
Greetings Voice Operators,
We have an interesting (code word for annoying) challenge that we've never
dealt with before, probably because we don't do much with Cisco phones. We
have a new customer coming on who wants to keep their very old Cisco 7941
phones. They have a few offices and the phones work as expected behind an
Edgemarc. However, they also have 100+ home users, and that's where the
issue comes in.
Apparently Cisco introduced a security "feature" where they create the
session using a random high numbered port (e.g. 49123) but in the Via
header, they say to respond to *private IP, port 5060*. So when the SBC
sees the private address it assumes it is being NAT'd through a firewall
and replies back to *public IP, port 49123*. What we're seeing is that the
home router passes the response back to *private IP, port 49123*, which the
phone doesn't accept (because it wants it on 5060) and the REGISTER fails.
As you know most home routers are poor at handling ALG (and we've tested
and found they are equally bad at handling this scenario). We (and the
customer) don't want to troubleshoot 100+ individual home routers.
We haven't found a way to turn off this really awesome "feature" so we're
trying to find other solutions. Anyone been through this and have any
suggestions?
Thanks,
Pete
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
Oct. 7, 2015
Cisco 7941 SIP
by ksuriyaarachchi@alteva.com
Two things I would try
1. Point the phone to alternate port (5090) . You will need a realm configured on the HNT SBC to accept 5090
2. Downgrade the phone firmware
Kumudu Suriyaarachchi ksuriyaarachchi at alteva.com<mailto:ksuriyaarachchi at alteva.com>
P 484.534.4427
[Alteva-Logo-horizontal]
From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Pete E
Sent: Tuesday, October 06, 2015 5:10 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Cisco 7941 SIP
Greetings Voice Operators,
We have an interesting (code word for annoying) challenge that we've never dealt with before, probably because we don't do much with Cisco phones. We have a new customer coming on who wants to keep their very old Cisco 7941 phones. They have a few offices and the phones work as expected behind an Edgemarc. However, they also have 100+ home users, and that's where the issue comes in.
Apparently Cisco introduced a security "feature" where they create the session using a random high numbered port (e.g. 49123) but in the Via header, they say to respond to private IP, port 5060. So when the SBC sees the private address it assumes it is being NAT'd through a firewall and replies back to public IP, port 49123. What we're seeing is that the home router passes the response back to private IP, port 49123, which the phone doesn't accept (because it wants it on 5060) and the REGISTER fails.
As you know most home routers are poor at handling ALG (and we've tested and found they are equally bad at handling this scenario). We (and the customer) don't want to troubleshoot 100+ individual home routers.
We haven't found a way to turn off this really awesome "feature" so we're trying to find other solutions. Anyone been through this and have any suggestions?
Thanks,
Pete
This communication (including any attachments) may contain privileged or confidential information of Alteva and is intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient, you should notify the author and delete this communication from your system, including any attachments. Any disclosure, copying, saving or distribution of this communication, or the taking of any action based on it, is strictly prohibited. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Alteva.
Oct. 6, 2015
Lack of Quality Industry-wide
by peeip989@gmail.com
Ditto. We do the same, but it doesn't get us very far. We've recently fired
two carriers for performance.
On Tue, Oct 6, 2015 at 12:34 PM, Peter Beckman <beckman at angryox.com> wrote:
> That's a great story Anthony! It's similar to my issues. I already do this
> for termination. DID and SMS issues are more difficult to manage. And the
> issues you have with one carrier that drives you to mass port your DIDs
> that you hope to escape start happening with your new carrier.
>
> I wish carriers would have the same level of visibility in their service
> and infrastructure as you seemed to have with Intellisight, and then fix
> the problems proactively when they find them.
>
> "What gets measured gets managed."
>
> So true. So elusive in this business.
>
> Beckman
>
> On Tue, 6 Oct 2015, Anthony Orlando wrote:
>
> You are correct Peter. It's a constant struggle. For years I used a
>> product from Empirix called Intelisight. It gave us the ability to
>> monitor carriers (and other managed objects) with defined sets of KPI's.
>> Once I saw a carrier have issues (PDD, quality, excessive 503's) I used
>> to call them and tell them they had a problem. Hours or days later they
>> would resolve. I got away from that practice and just routed around
>> them. Funny how they notice that. Once the issue was resolved I put
>> them in a penalty box and slowly added traffic. Once they realized I was
>> measuring their performance and there would be financial repercussions
>> it's amazing how the quality of their under lying carriers improved. My
>> carrier ticket count dropped by 25-30%.
>>
>
> ---------------------------------------------------------------------------
> Peter Beckman Internet Guy
> beckman at angryox.com
> http://www.angryox.com/
> ---------------------------------------------------------------------------
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
Oct. 6, 2015
Cisco 7941 SIP
by peeip989@gmail.com
Greetings Voice Operators,
We have an interesting (code word for annoying) challenge that we've never
dealt with before, probably because we don't do much with Cisco phones. We
have a new customer coming on who wants to keep their very old Cisco 7941
phones. They have a few offices and the phones work as expected behind an
Edgemarc. However, they also have 100+ home users, and that's where the
issue comes in.
Apparently Cisco introduced a security "feature" where they create the
session using a random high numbered port (e.g. 49123) but in the Via
header, they say to respond to *private IP, port 5060*. So when the SBC
sees the private address it assumes it is being NAT'd through a firewall
and replies back to *public IP, port 49123*. What we're seeing is that the
home router passes the response back to *private IP, port 49123*, which the
phone doesn't accept (because it wants it on 5060) and the REGISTER fails.
As you know most home routers are poor at handling ALG (and we've tested
and found they are equally bad at handling this scenario). We (and the
customer) don't want to troubleshoot 100+ individual home routers.
We haven't found a way to turn off this really awesome "feature" so we're
trying to find other solutions. Anyone been through this and have any
suggestions?
Thanks,
Pete
Oct. 6, 2015