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
August 2009
- 77 participants
- 440 messages
VNXX
by abalashov@evaristesys.com
What does the FCC and/or intercarrier compensation reform crowd mean,
exactly, when they say "Virtual NXX?"
Is that some class of clever remote call forwarding schemes from a CO
where the call between it and your rate center is rated LD by the ILEC,
but which some call forwarding product manages to get around or mitigate
somehow?
Or does it refer to carriers picking up inbound calls at the LATA
supertandems by carriers from rate centers in which they don't have
direct end-office trunking and whose number blocks are not homed to the
tandems (any tandems) to which the carrier is connected? This was
rather common during the dialup boom and often skirted the
'DS1-of-consistent-usage = DEOT needed' requirement in most form ICAs,
as I understand it.
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
Aug. 9, 2009
Broadworks R14.SP9 - Unscreened Calls
by mh@markholloway.com
R14.SP9 Unscreened Calls is broken. Assign UC to Customer A trunk
group, assign static IP to Device, calls from the SIP Endpoint work.
Provision Unscreened Calls on Customer B, assign appropriate static IP
to Customer B's Device, calls from Customer B work but Customer A is
broken. Follow the same process and provision Customer C, now
Customer A and Customer B are broken...and so the pattern continues.
Latest PB is loaded. Opened a TAC case but no response yet.
Aug. 9, 2009
SMS gateway API.
by daryl@introspect.net
+1 on Clickatell. We also use them.
Their payment options really sucked at first (wouldn't use a card to
auto-add credit to an account when necessary, causing an instance or 2
of downtime because we forgot to check our available balance
frequently enough, and without a warning form them) but the seem to
have gotten better in that respect.
Technically, they have been very good.
On Aug 8, 2009, at 6:13 PM, Matt Riddell wrote:
> On 9/08/09 6:51 AM, Brandon Lehmann wrote:
>
> Yep, we use the same - occasionally they seem to take a while to
> deliver messages, but most of the time are pretty instant.
Aug. 9, 2009
SMS gateway API.
by matt@venturevoip.com
On 9/08/09 6:51 AM, Brandon Lehmann wrote:
> Alex,
>
> We've had an excellent experience developing SMS applications (inbound&
> outbound) using the APIs available from http://www.clickatell.com/. I'm not
> sure if they are the cheapest out there (as low as $0.01/msg received);
> however, we have found their API to be one of the easiest to use.
Yep, we use the same - occasionally they seem to take a while to deliver
messages, but most of the time are pretty instant.
--
Cheers,
Matt Riddell
Director
_______________________________________________
http://www.venturevoip.com/news.php (Daily Asterisk News)
http://www.venturevoip.com/st.php (SmoothTorque Predictive Dialer)
http://www.venturevoip.com/c3.php (ConduIT3 PABX Systems)
Aug. 8, 2009
SMS gateway API.
by brandon@bitradius.com
Alex,
We've had an excellent experience developing SMS applications (inbound &
outbound) using the APIs available from http://www.clickatell.com/. I'm not
sure if they are the cheapest out there (as low as $0.01/msg received);
however, we have found their API to be one of the easiest to use.
We've also developed a few applications using direct connections to a
device. The biggest problems we ran into when using a device were: finding
a phone that would charge over USB from a computer (not all do), reliable
cellular coverage while inside a cabinet and/or closet, wireless plans with
'unlimited' txt messaging plans can get 'expensive', and a device that
isn't plagued by lockups during high-volume messaging.
--
Brandon Lehmann
BitRadius, LLC
Email: brandon at bitradius.com
Web: http://www.bitradius.com
Phone: 567-255-3610x9500
Toll-Free: 888-608-7253x9500
Fax: 567-255-3611
On Fri, 7 Aug 2009 21:06:19 -0400 (EDT), "Alex Balashov"
<abalashov at evaristesys.com> wrote:
> Let me add something else here:
>
> Obviously, there are various ways to get this data off of a cell device
> that rely on use of a network rather than SMS, and can be bridged
straight
> into IP. That would be far more straightforward, cheaper and more
> sensible.
>
> However, that defeats one of the specific problems I'm trying to solve
> here, which is that the operating area has very, very spotty
> 3G/EDGE/EVDO/etc. coverage, but always has basic digital coverage.
>
>>
>> Hi everyone,
>>
>> Sorry if this is a little off-topic, but I thought I would tap the
>> enormous collective wealth of knowledge here.
>>
>> I come from the fixed-line world, so I don't know terribly much about
SMS
>> or mobile anything.
>>
>> I have a situation where I need an endpoint to receive a fairly large
>> amount of SMS messages in something close to real-time and then be able
>> to
>> automatically do something with them as part of a backoffice process,
and
>> need to set up something rather quickly.
>>
>> For example, an SMS message comes into some sort of device or service,
>> and
>> this triggers a RESTful HTTP call (or SOAP, or whatever) to some agent
>> that does something with that data.
>>
>> Speed is of the essence; this rules out most SMS-to-email gateways
>> because it usually takes at least several minutes to receive the e-mail.
>> In this case, that won't work; the delay is just too long.
>>
>> Likewise, vertically integrated SMS gateway services that provide some
>> sort of interactive online "chat" window with an interface into an SMS
>> conversation won't do. This needs to be development-friendly; I need
to
>> be able to write some code to do something with the contents of that
>> message post haste. The other thing is, vendors providing those
products
>> and services in this category charge a fair bit per text message, which
>> isn't going to fly in this case because there may be a dozen text
>> messages
>> per minute or more, occasionally. Something flat-rate would be
>> desirable,
>> even if it's expensive (say, a few hundred dollars a month).
>>
>> Lastly, I don't know if it's possible to get any kind of access circuit
>> in
>> North America over which SMS messages can be received, but even if it
>> were, that's not really an option in this case due to time constraints.
>> Likewise, setting up a GSM or CDMA receiver device registered on a cell
>> network - legitimately or otherwise - is out too, for similar reasons.
>>
>> What it really comes down to is that I need a fast SMS data relay
service
>> that handle a relatively high-volume at relatively little expense, and
>> one
>> which can provide that data via some sort of HTTP or XML-RPC or SOAP
type
>> API callback so that the data can be plumbed to an agent on my side for
>> further processing.
>>
>> I have no idea if something like this exists, or if that's tantamount to
>> a
>> request for magic. That's why I'm inquiring.
>>
>> Thanks!
>>
>> --
>> Alex Balashov
>> Evariste Systems
>> Web : http://www.evaristesys.com/
>> Tel : (+1) (678) 954-0670
>> Direct : (+1) (678) 954-0671
>> Mobile : (+1) (678) 237-1775
>>
>>
Aug. 8, 2009
[LIKELY JUNK]Re: Sylantro users
by lindsey@e-c-group.com
Elegance is nice, but converting from one system (multiple
registrations for a single AoR) to the other (using Shared Call
Appearance / Shared Line Appearance) is certainly achievable.
The first step can be done in the weeks leading to a migration. You
must get your devices under CPE Management, so that you've got your
SIP phone configurations on a server, so you can manipulate them. If
you don't already have this, there are ways to recover the
configuration from devices. The most difficult is Polycom, but
fortunately the Polycom's web interface HTML code can map nicely to
the key provisioning details of the phone.
Aastra, Linksys, and Cisco give more direct ways to retrieve the
config from the phone.
Once you've got the phone config on a CPEM server, it's
straightforward to discover which phones are registering using the
same SIP URI AoR. Then, if you're migrating to BroadWorks, you can
create new devices, and new users, and configure Shared Call
Appearance using OCI-P (BroadWorks's XML-over-TCP provisioning
interface). Then you modify the phone configs appropriately, and ask
them to re-download their configs. All of this can be automated.
It's not a trivial change, but it's certainly achievable. And it
wouldn't be the largest part of a migration from one softswitch
platform to another.
On Aug 7, 2009, at 7:20 PM, anorexicpoodle wrote:
> Supporting forked registrations was a big consideration in our
> platform
> decision as well, and once you have designed product around something
> like that, there is no elegant way to backpedal.
>
> On Fri, 2009-08-07 at 17:57 -0500, Brandon Buckner wrote:
>> Another issue I?ve seen with Broadworks is that it doesn?t allow
>> multiple registrations to a single DID. Broadsoft confirmed that. We
>> have a large amount of customers using that feature on our Sylantro
>> platform instead of one number/one phone, whichever happened to
>> register last. As we already support a Broadworks installation for a
>> big customer of ours via Taqua, we?ve got experience managing and
>> configuring the system. It was just when we started looking ourselves
>> that we didn?t want to do business like that. A big selling point on
>> the Metaswitch solution right now (and we?ve not signed anything) is
>> consolidating all the different portals for users and admins and
>> support along with troubleshooting. Especially with the Service
>> Assurance Server, there?s much less things to look at and 3rd party
>> tools to utilize for the same or better diagnostic information,
>> meaning faster resolution and better customer support.
>>
>>
>>
>> ----
>> Brandon Buckner
>> Switching Technician / VoIP Admin
>> Iowa Network Services
>> 515-830-0440 opt 1
>> brandonb at netins.com
>>
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From:voiceops-bounces at voiceops.org
>> [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia
>> Sent: Friday, August 07, 2009 4:44 PM
>> To: voiceops at voiceops.org
>> Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
>>
>>
>>
>>
>> unfortunately some of the legacy Sylantro Synergy folks will never
>> learn about the BroadWorks product if they get turned off by the
>> sales
>> folks though.
>>
>>
>>
>>
>> i completely agree that their product is solid, as a long term
>> broadworks user myself it is just a constant decision around if the
>> product is *so* good that the lack of account management isn't an
>> issue.
>>
>>
>>
>>
>>
>> I really like the feedback i've been hearing about metaswitch on this
>> list so it seems like certainly a good solution to thoroughly
>> investigate.
>>
>> On Fri, Aug 7, 2009 at 1:28 PM, Hiers, David <David_Hiers at adp.com>
>> wrote:
>>
>> Charm school dropouts are certainly not underrepresented there; but
>> their stuff works.
>>
>>
>>
>>
>>
>> David
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: voiceops-bounces at voiceops.org [voiceops-bounces at voiceops.org]
>> On
>> Behalf Of Brandon Buckner [BrandonB at netins.com]
>> Sent: Friday, August 07, 2009 9:12 AM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] Sylantro users
>>
>>
>> We are still running Sylantro. We looked into Broadsoft as we
>> manage a
>> BW installation for a customer of ours, but pretty much everyone we
>> talked to was an arrogant #^@& that acted like we owed them our
>> business and really turned us off to them. We already have a
>> Metaswitch for a PSTN gateway so we're looking heavily into their
>> offerings.
>>
>>
>>
>> ----
>>
>> Brandon Buckner
>>
>> Switching Technician / VoIP Admin
>>
>> IowaNetwork Services
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: voiceops-bounces at voiceops.org
>> [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia
>> Sent: Friday, August 07, 2009 10:50 AM
>> To: voiceops at voiceops.org
>> Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
>>
>>
>>
>>
>> Hi
>>
>> Guess since no one else responded i can rep the Synergy platform :)
>>
>> We've got the Synergy platform. Haven't moved to another platform
>> yet, still have a bunch of things to consider...
>>
>> a) we have yet to receive an EOL/EOS notice from BroadSoft. We're
>> told it will be ~2 years but waiting for something official.
>>
>> b) BroadSoft is working on an ability to migrate the base from the
>> Synergy platform to the BroadWorks platform so will need to see how
>> that works out. I think if you have SIP Trunk customers or SIP
>> Hosted
>> customers you'll be OK but anyone that might be running MGCP the
>> advance features just don't seem to be present on the BroadWorks
>> platform.
>>
>> c) There aren't a lot of other carrier grade platforms out there...
>> Metaswitch, Sonus ASX, BroadSoft Broadworks are the big ones i can
>> think of -- anyone have any other major vendors they would recommend?
>> -- We are familiar with the BroadWorks platform but we're waiting for
>> release 16 to come out with Sol10/x86 hardware support.
>>
>> On top of all that, it is extremely costly to move customers from one
>> platform to another so it will take several months to continue the
>> evaluation and if a migration is required probably a couple years
>> past
>> that.
>>
>> When you factor in ongoing M&S and licensing costs and the need to
>> reduce network costs all the time... sometimes I wonder if building
>> your own soft switch isn't the best route...
>>
>> Are you still running the Synergy platform or have you already
>> migrated to something new?
>>
>> -katia
>>
>> On Thu, Aug 6, 2009 at 1:32 AM, anorexicpoodle
>> <anorexicpoodle at gmail.com> wrote:
>>
>> I see this list has a lot of Broadsoft users, anyone left running
>> Sylantro? If you were a Sylantro shop until the buyout etc what
>> platform
>> did you move to and what steered the decision?
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> 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.
>>
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Mark R Lindsey lindsey at e-c-group.com http://e-c-group.com/~lindsey
+12293160013
Aug. 8, 2009
SMS gateway API.
by abalashov@evaristesys.com
Let me add something else here:
Obviously, there are various ways to get this data off of a cell device
that rely on use of a network rather than SMS, and can be bridged straight
into IP. That would be far more straightforward, cheaper and more
sensible.
However, that defeats one of the specific problems I'm trying to solve
here, which is that the operating area has very, very spotty
3G/EDGE/EVDO/etc. coverage, but always has basic digital coverage.
>
> Hi everyone,
>
> Sorry if this is a little off-topic, but I thought I would tap the
> enormous collective wealth of knowledge here.
>
> I come from the fixed-line world, so I don't know terribly much about SMS
> or mobile anything.
>
> I have a situation where I need an endpoint to receive a fairly large
> amount of SMS messages in something close to real-time and then be able to
> automatically do something with them as part of a backoffice process, and
> need to set up something rather quickly.
>
> For example, an SMS message comes into some sort of device or service, and
> this triggers a RESTful HTTP call (or SOAP, or whatever) to some agent
> that does something with that data.
>
> Speed is of the essence; this rules out most SMS-to-email gateways
> because it usually takes at least several minutes to receive the e-mail.
> In this case, that won't work; the delay is just too long.
>
> Likewise, vertically integrated SMS gateway services that provide some
> sort of interactive online "chat" window with an interface into an SMS
> conversation won't do. This needs to be development-friendly; I need to
> be able to write some code to do something with the contents of that
> message post haste. The other thing is, vendors providing those products
> and services in this category charge a fair bit per text message, which
> isn't going to fly in this case because there may be a dozen text messages
> per minute or more, occasionally. Something flat-rate would be desirable,
> even if it's expensive (say, a few hundred dollars a month).
>
> Lastly, I don't know if it's possible to get any kind of access circuit in
> North America over which SMS messages can be received, but even if it
> were, that's not really an option in this case due to time constraints.
> Likewise, setting up a GSM or CDMA receiver device registered on a cell
> network - legitimately or otherwise - is out too, for similar reasons.
>
> What it really comes down to is that I need a fast SMS data relay service
> that handle a relatively high-volume at relatively little expense, and one
> which can provide that data via some sort of HTTP or XML-RPC or SOAP type
> API callback so that the data can be plumbed to an agent on my side for
> further processing.
>
> I have no idea if something like this exists, or if that's tantamount to a
> request for magic. That's why I'm inquiring.
>
> Thanks!
>
> --
> Alex Balashov
> Evariste Systems
> Web : http://www.evaristesys.com/
> Tel : (+1) (678) 954-0670
> Direct : (+1) (678) 954-0671
> Mobile : (+1) (678) 237-1775
>
>
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
Aug. 8, 2009
Sylantro users
by dpeak@broadsoft.com
Alex,
I'd answer your question by delineating some of the signaling characteristics that BroadWorks can customize based on the access side device that it is talking to. These include:
Early media support/type
Number of ports/lines/simultaneous sessions supported on the device
Authentication support
e164 support or not
RFC3264 hold or not
Trusted or not, affects calling party info to the access device
Addressing scheme (proxy based or device based)
Video capable or not
Call waiting type
Route advance support/interpretation
Diversion header/referred-by header manipulation for various SIP access trunking scenarios
Remote reset support or not
Plus a handful of others that are useful in various scenarios.
Dag Peak
Senior Sales Engineer
dpeak at broadsoft.com
+1 240.364.5191
-----Original Message-----
From: Alex Balashov [mailto:abalashov at evaristesys.com]
Sent: Friday, August 07, 2009 6:35 PM
To: Dag Peak
Cc: anorexicpoodle; voiceops at voiceops.org
Subject: Re: [VoiceOps] Sylantro users
Dag,
When you talk about the differences in signaling to various devices, what
exactly are you referring to?
Are you talking about passing the device the Contact binding user part
that it registered with vs. overriding it with the incoming DNIS? Or
maybe MWI event functionality and/or something provisioning-related?
Or some other nuance that varies between devices?
Thanks,
-- Alex
> I???d clarify something about the statement below which says that
> ???BroadWorks does not allow multiple registrations to a single DID???.
> From a purely semantic perspective BroadWorks does support multiple
> registrations per DID, but there???s definitely a difference in how
> Synergy did that vs. how BroadWorks does it, with some tradeoffs on each
> side.
>
> In Synergy, their ???Call Forking??? feature allowed multiple access
> devices to register using the same AoR URI, which would result in a single
> AoR with multiple contacts. Calls to the subscriber would alert all the
> locations, and calls could be originated from any of the locations. The
> upside to this is that you could configure all those devices identically
> (with the same AoR and SIP authentication credentials), the downside to
> that strategy is that Synergy had no way to provide custom signaling to
> each device (which is not an issue if all of the user???s devices are the
> same, but is an issue if they are not, consider the case where a single
> user with has an IP phone, a cordless phone hanging off of an ATA, and a
> softclient). Synergy???s forking support was done at the protocol level.
>
> In BroadWorks a user may have many devices (again, consider the case of a
> user with three devices, the IP phone, the ATA and the softclient). The
> user will have a primary device and then up to 35 other devices, known as
> Shared Call Appearances (then name of the BroadWorks feature for this
> functionality). The difference between Synergy Call Forking and SCA is
> that with BroadWorks, each device will use a unique AoR to register.
> Another way of saying this is that a subscriber can have many devices,
> with each device having a unique AoR, and each AoR having a single contact
> address. The upside to this way of supporting multiple devices is that
> BroadWorks will know the type of device that it is signaling too, and can
> customize that signaling based on the specific requirements of the
> particular device. The way you signal to an advanced IP phone will be
> different from the way you signal to an ATA will be different from the way
> you signal to a softclient. The downside might be that your device configs
> now have to be unique per device, but with modern device configuration
> management systems (including the one built into BroadWorks), that's
> really a red herring.
>
> In addition to this way of doing things, BroadWorks allows users to have
> many phone numbers (BroadWorks is very user centric as opposed to being
> phone number or device centric). So, you could have the case where a
> single user has multiple Telephone Numbers, and any time any of those TNs
> are called, all of the user???s devices are alerted, and the user can take
> the call at any device, and the user can originate a call from any device.
> That kind of functionality is pretty straightforward and part of most
> systems, but one interesting bit we???ve added is the ability to move
> calls around between any of those locations by dialing a FAC. This
> capability is partially enabled by the SCA notion of unique AoRs per
> device.
>
> Dag Peak
> Senior Sales Engineer
> dpeak at broadsoft.com
> +1 240.364.5191
>
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
> On Behalf Of anorexicpoodle
> Sent: Friday, August 07, 2009 5:20 PM
> To: Brandon Buckner
> Cc: voiceops at voiceops.org
> Subject: Re: [VoiceOps] [LIKELY JUNK]Re: Sylantro users
>
> Supporting forked registrations was a big consideration in our platform
> decision as well, and once you have designed product around something
> like that, there is no elegant way to backpedal.
>
> On Fri, 2009-08-07 at 17:57 -0500, Brandon Buckner wrote:
>> Another issue I???ve seen with Broadworks is that it doesn???t allow
>> multiple registrations to a single DID. Broadsoft confirmed that. We
>> have a large amount of customers using that feature on our Sylantro
>> platform instead of one number/one phone, whichever happened to
>> register last. As we already support a Broadworks installation for a
>> big customer of ours via Taqua, we???ve got experience managing and
>> configuring the system. It was just when we started looking ourselves
>> that we didn???t want to do business like that. A big selling point on
>> the Metaswitch solution right now (and we???ve not signed anything) is
>> consolidating all the different portals for users and admins and
>> support along with troubleshooting. Especially with the Service
>> Assurance Server, there???s much less things to look at and 3rd party
>> tools to utilize for the same or better diagnostic information,
>> meaning faster resolution and better customer support.
>>
>>
>>
>> ----
>> Brandon Buckner
>> Switching Technician / VoIP Admin
>> Iowa Network Services
>> 515-830-0440 opt 1
>> brandonb at netins.com
>>
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From:voiceops-bounces at voiceops.org
>> [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia
>> Sent: Friday, August 07, 2009 4:44 PM
>> To: voiceops at voiceops.org
>> Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
>>
>>
>>
>>
>> unfortunately some of the legacy Sylantro Synergy folks will never
>> learn about the BroadWorks product if they get turned off by the sales
>> folks though.
>>
>>
>>
>>
>> i completely agree that their product is solid, as a long term
>> broadworks user myself it is just a constant decision around if the
>> product is *so* good that the lack of account management isn't an
>> issue.
>>
>>
>>
>>
>>
>> I really like the feedback i've been hearing about metaswitch on this
>> list so it seems like certainly a good solution to thoroughly
>> investigate.
>>
>> On Fri, Aug 7, 2009 at 1:28 PM, Hiers, David <David_Hiers at adp.com>
>> wrote:
>>
>> Charm school dropouts are certainly not underrepresented there; but
>> their stuff works.
>>
>>
>>
>>
>>
>> David
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: voiceops-bounces at voiceops.org [voiceops-bounces at voiceops.org] On
>> Behalf Of Brandon Buckner [BrandonB at netins.com]
>> Sent: Friday, August 07, 2009 9:12 AM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] Sylantro users
>>
>>
>> We are still running Sylantro. We looked into Broadsoft as we manage a
>> BW installation for a customer of ours, but pretty much everyone we
>> talked to was an arrogant #^@& that acted like we owed them our
>> business and really turned us off to them. We already have a
>> Metaswitch for a PSTN gateway so we're looking heavily into their
>> offerings.
>>
>>
>>
>> ----
>>
>> Brandon Buckner
>>
>> Switching Technician / VoIP Admin
>>
>> IowaNetwork Services
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: voiceops-bounces at voiceops.org
>> [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia
>> Sent: Friday, August 07, 2009 10:50 AM
>> To: voiceops at voiceops.org
>> Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
>>
>>
>>
>>
>> Hi
>>
>> Guess since no one else responded i can rep the Synergy platform :)
>>
>> We've got the Synergy platform. Haven't moved to another platform
>> yet, still have a bunch of things to consider...
>>
>> a) we have yet to receive an EOL/EOS notice from BroadSoft. We're
>> told it will be ~2 years but waiting for something official.
>>
>> b) BroadSoft is working on an ability to migrate the base from the
>> Synergy platform to the BroadWorks platform so will need to see how
>> that works out. I think if you have SIP Trunk customers or SIP Hosted
>> customers you'll be OK but anyone that might be running MGCP the
>> advance features just don't seem to be present on the BroadWorks
>> platform.
>>
>> c) There aren't a lot of other carrier grade platforms out there...
>> Metaswitch, Sonus ASX, BroadSoft Broadworks are the big ones i can
>> think of -- anyone have any other major vendors they would recommend?
>> -- We are familiar with the BroadWorks platform but we're waiting for
>> release 16 to come out with Sol10/x86 hardware support.
>>
>> On top of all that, it is extremely costly to move customers from one
>> platform to another so it will take several months to continue the
>> evaluation and if a migration is required probably a couple years past
>> that.
>>
>> When you factor in ongoing M&S and licensing costs and the need to
>> reduce network costs all the time... sometimes I wonder if building
>> your own soft switch isn't the best route...
>>
>> Are you still running the Synergy platform or have you already
>> migrated to something new?
>>
>> -katia
>>
>> On Thu, Aug 6, 2009 at 1:32 AM, anorexicpoodle
>> <anorexicpoodle at gmail.com> wrote:
>>
>> I see this list has a lot of Broadsoft users, anyone left running
>> Sylantro? If you were a Sylantro shop until the buyout etc what
>> platform
>> did you move to and what steered the decision?
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> 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.
>>
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
>
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
Aug. 8, 2009
SMS gateway API.
by abalashov@evaristesys.com
Hi everyone,
Sorry if this is a little off-topic, but I thought I would tap the
enormous collective wealth of knowledge here.
I come from the fixed-line world, so I don't know terribly much about SMS
or mobile anything.
I have a situation where I need an endpoint to receive a fairly large
amount of SMS messages in something close to real-time and then be able to
automatically do something with them as part of a backoffice process, and
need to set up something rather quickly.
For example, an SMS message comes into some sort of device or service, and
this triggers a RESTful HTTP call (or SOAP, or whatever) to some agent
that does something with that data.
Speed is of the essence; this rules out most SMS-to-email gateways
because it usually takes at least several minutes to receive the e-mail.
In this case, that won't work; the delay is just too long.
Likewise, vertically integrated SMS gateway services that provide some
sort of interactive online "chat" window with an interface into an SMS
conversation won't do. This needs to be development-friendly; I need to
be able to write some code to do something with the contents of that
message post haste. The other thing is, vendors providing those products
and services in this category charge a fair bit per text message, which
isn't going to fly in this case because there may be a dozen text messages
per minute or more, occasionally. Something flat-rate would be desirable,
even if it's expensive (say, a few hundred dollars a month).
Lastly, I don't know if it's possible to get any kind of access circuit in
North America over which SMS messages can be received, but even if it
were, that's not really an option in this case due to time constraints.
Likewise, setting up a GSM or CDMA receiver device registered on a cell
network - legitimately or otherwise - is out too, for similar reasons.
What it really comes down to is that I need a fast SMS data relay service
that handle a relatively high-volume at relatively little expense, and one
which can provide that data via some sort of HTTP or XML-RPC or SOAP type
API callback so that the data can be plumbed to an agent on my side for
further processing.
I have no idea if something like this exists, or if that's tantamount to a
request for magic. That's why I'm inquiring.
Thanks!
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
Aug. 8, 2009
Sylantro users
by abalashov@evaristesys.com
Dag,
When you talk about the differences in signaling to various devices, what
exactly are you referring to?
Are you talking about passing the device the Contact binding user part
that it registered with vs. overriding it with the incoming DNIS? Or
maybe MWI event functionality and/or something provisioning-related?
Or some other nuance that varies between devices?
Thanks,
-- Alex
> I???d clarify something about the statement below which says that
> ???BroadWorks does not allow multiple registrations to a single DID???.
> From a purely semantic perspective BroadWorks does support multiple
> registrations per DID, but there???s definitely a difference in how
> Synergy did that vs. how BroadWorks does it, with some tradeoffs on each
> side.
>
> In Synergy, their ???Call Forking??? feature allowed multiple access
> devices to register using the same AoR URI, which would result in a single
> AoR with multiple contacts. Calls to the subscriber would alert all the
> locations, and calls could be originated from any of the locations. The
> upside to this is that you could configure all those devices identically
> (with the same AoR and SIP authentication credentials), the downside to
> that strategy is that Synergy had no way to provide custom signaling to
> each device (which is not an issue if all of the user???s devices are the
> same, but is an issue if they are not, consider the case where a single
> user with has an IP phone, a cordless phone hanging off of an ATA, and a
> softclient). Synergy???s forking support was done at the protocol level.
>
> In BroadWorks a user may have many devices (again, consider the case of a
> user with three devices, the IP phone, the ATA and the softclient). The
> user will have a primary device and then up to 35 other devices, known as
> Shared Call Appearances (then name of the BroadWorks feature for this
> functionality). The difference between Synergy Call Forking and SCA is
> that with BroadWorks, each device will use a unique AoR to register.
> Another way of saying this is that a subscriber can have many devices,
> with each device having a unique AoR, and each AoR having a single contact
> address. The upside to this way of supporting multiple devices is that
> BroadWorks will know the type of device that it is signaling too, and can
> customize that signaling based on the specific requirements of the
> particular device. The way you signal to an advanced IP phone will be
> different from the way you signal to an ATA will be different from the way
> you signal to a softclient. The downside might be that your device configs
> now have to be unique per device, but with modern device configuration
> management systems (including the one built into BroadWorks), that's
> really a red herring.
>
> In addition to this way of doing things, BroadWorks allows users to have
> many phone numbers (BroadWorks is very user centric as opposed to being
> phone number or device centric). So, you could have the case where a
> single user has multiple Telephone Numbers, and any time any of those TNs
> are called, all of the user???s devices are alerted, and the user can take
> the call at any device, and the user can originate a call from any device.
> That kind of functionality is pretty straightforward and part of most
> systems, but one interesting bit we???ve added is the ability to move
> calls around between any of those locations by dialing a FAC. This
> capability is partially enabled by the SCA notion of unique AoRs per
> device.
>
> Dag Peak
> Senior Sales Engineer
> dpeak at broadsoft.com
> +1 240.364.5191
>
>
> -----Original Message-----
> From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
> On Behalf Of anorexicpoodle
> Sent: Friday, August 07, 2009 5:20 PM
> To: Brandon Buckner
> Cc: voiceops at voiceops.org
> Subject: Re: [VoiceOps] [LIKELY JUNK]Re: Sylantro users
>
> Supporting forked registrations was a big consideration in our platform
> decision as well, and once you have designed product around something
> like that, there is no elegant way to backpedal.
>
> On Fri, 2009-08-07 at 17:57 -0500, Brandon Buckner wrote:
>> Another issue I???ve seen with Broadworks is that it doesn???t allow
>> multiple registrations to a single DID. Broadsoft confirmed that. We
>> have a large amount of customers using that feature on our Sylantro
>> platform instead of one number/one phone, whichever happened to
>> register last. As we already support a Broadworks installation for a
>> big customer of ours via Taqua, we???ve got experience managing and
>> configuring the system. It was just when we started looking ourselves
>> that we didn???t want to do business like that. A big selling point on
>> the Metaswitch solution right now (and we???ve not signed anything) is
>> consolidating all the different portals for users and admins and
>> support along with troubleshooting. Especially with the Service
>> Assurance Server, there???s much less things to look at and 3rd party
>> tools to utilize for the same or better diagnostic information,
>> meaning faster resolution and better customer support.
>>
>>
>>
>> ----
>> Brandon Buckner
>> Switching Technician / VoIP Admin
>> Iowa Network Services
>> 515-830-0440 opt 1
>> brandonb at netins.com
>>
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From:voiceops-bounces at voiceops.org
>> [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia
>> Sent: Friday, August 07, 2009 4:44 PM
>> To: voiceops at voiceops.org
>> Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
>>
>>
>>
>>
>> unfortunately some of the legacy Sylantro Synergy folks will never
>> learn about the BroadWorks product if they get turned off by the sales
>> folks though.
>>
>>
>>
>>
>> i completely agree that their product is solid, as a long term
>> broadworks user myself it is just a constant decision around if the
>> product is *so* good that the lack of account management isn't an
>> issue.
>>
>>
>>
>>
>>
>> I really like the feedback i've been hearing about metaswitch on this
>> list so it seems like certainly a good solution to thoroughly
>> investigate.
>>
>> On Fri, Aug 7, 2009 at 1:28 PM, Hiers, David <David_Hiers at adp.com>
>> wrote:
>>
>> Charm school dropouts are certainly not underrepresented there; but
>> their stuff works.
>>
>>
>>
>>
>>
>> David
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: voiceops-bounces at voiceops.org [voiceops-bounces at voiceops.org] On
>> Behalf Of Brandon Buckner [BrandonB at netins.com]
>> Sent: Friday, August 07, 2009 9:12 AM
>> To: voiceops at voiceops.org
>> Subject: Re: [VoiceOps] Sylantro users
>>
>>
>> We are still running Sylantro. We looked into Broadsoft as we manage a
>> BW installation for a customer of ours, but pretty much everyone we
>> talked to was an arrogant #^@& that acted like we owed them our
>> business and really turned us off to them. We already have a
>> Metaswitch for a PSTN gateway so we're looking heavily into their
>> offerings.
>>
>>
>>
>> ----
>>
>> Brandon Buckner
>>
>> Switching Technician / VoIP Admin
>>
>> IowaNetwork Services
>>
>>
>>
>>
>> ______________________________________________________________________
>> From: voiceops-bounces at voiceops.org
>> [mailto:voiceops-bounces at voiceops.org] On Behalf Of katia
>> Sent: Friday, August 07, 2009 10:50 AM
>> To: voiceops at voiceops.org
>> Subject: [LIKELY JUNK]Re: [VoiceOps] Sylantro users
>>
>>
>>
>>
>> Hi
>>
>> Guess since no one else responded i can rep the Synergy platform :)
>>
>> We've got the Synergy platform. Haven't moved to another platform
>> yet, still have a bunch of things to consider...
>>
>> a) we have yet to receive an EOL/EOS notice from BroadSoft. We're
>> told it will be ~2 years but waiting for something official.
>>
>> b) BroadSoft is working on an ability to migrate the base from the
>> Synergy platform to the BroadWorks platform so will need to see how
>> that works out. I think if you have SIP Trunk customers or SIP Hosted
>> customers you'll be OK but anyone that might be running MGCP the
>> advance features just don't seem to be present on the BroadWorks
>> platform.
>>
>> c) There aren't a lot of other carrier grade platforms out there...
>> Metaswitch, Sonus ASX, BroadSoft Broadworks are the big ones i can
>> think of -- anyone have any other major vendors they would recommend?
>> -- We are familiar with the BroadWorks platform but we're waiting for
>> release 16 to come out with Sol10/x86 hardware support.
>>
>> On top of all that, it is extremely costly to move customers from one
>> platform to another so it will take several months to continue the
>> evaluation and if a migration is required probably a couple years past
>> that.
>>
>> When you factor in ongoing M&S and licensing costs and the need to
>> reduce network costs all the time... sometimes I wonder if building
>> your own soft switch isn't the best route...
>>
>> Are you still running the Synergy platform or have you already
>> migrated to something new?
>>
>> -katia
>>
>> On Thu, Aug 6, 2009 at 1:32 AM, anorexicpoodle
>> <anorexicpoodle at gmail.com> wrote:
>>
>> I see this list has a lot of Broadsoft users, anyone left running
>> Sylantro? If you were a Sylantro shop until the buyout etc what
>> platform
>> did you move to and what steered the decision?
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>>
>>
>>
>>
>> ______________________________________________________________________
>> 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.
>>
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
>
--
Alex Balashov
Evariste Systems
Web : http://www.evaristesys.com/
Tel : (+1) (678) 954-0670
Direct : (+1) (678) 954-0671
Mobile : (+1) (678) 237-1775
Aug. 8, 2009