Discussion:
voip.ms impression
Mark Wood
2012-11-20 00:25:35 UTC
Permalink
We have been using voip.ms for 6-8 months so far and I want to get some feedback from users that have been at it for longer.

Specifically we (main and subaccounts) experience times where our outbound calls just hang after dialing and sometimes abruptly connect, or sometimes not at all. When a subaccount calls to report problems to us and we check our home page it will show all of our accounts as 'not registered', and then slowly one by one they will show as 'registered'. We had an incident over the weekend with a security office that couldn't receive any inbound calls. We logged in to the voip.ms site to check the registrations and initiate a support ticket and the site again said 'not registered'. The instructions had us do and 'echo test' procedure and the results were the same as when they were routed to the subaccount. The support response 12 hours later was 'works for us' and then 'check your routers and firewalls'.

Comments? Who are other good candidates for reselling VoIP like this model?

Thanks,
Mark W. Wood
office: (760)202-0224 X2010
Direct: (760)459-1981
[cid:***@01CDC66F.2447FEE0]
www.redphonetech.com
Tony Graziano
2012-11-20 00:51:07 UTC
Permalink
We use voip.ms for small occasional use and its very good for testing. Our
production systems use Appia (we are a reseller) who can also provide t.38
service which we have found to work well in a production environment.

At the same time, most of our sip servers sit behind application aware
firewalls and ensure connections using SIP the protocol are in now way
impaired by other applications on the network. These application aware
devices also have IDS and are completely cloud managed and monitored.

I would agree voip.ms works but not always that well at every POP and they
do seem to have occasional problems with call quality and completion
depending on the number you call. Whether this is ISP routing, edge or
internal issues at their POP is sometimes a little unclear, but they are
good enough to use for failover, backup or testing but not particulary in
large production environments (IMO).
Post by Mark Wood
We have been using voip.ms for 6-8 months so far and I want to get some
feedback from users that have been at it for longer. ****
** **
Specifically we (main and subaccounts) experience times where our outbound
calls just hang after dialing and sometimes abruptly connect, or sometimes
not at all. When a subaccount calls to report problems to us and we check
our home page it will show all of our accounts as ‘not registered’, and
then slowly one by one they will show as ‘registered’. We had an incident
over the weekend with a security office that couldn’t receive any inbound
calls. We logged in to the voip.ms site to check the registrations and
initiate a support ticket and the site again said ‘not registered’. The
instructions had us do and ‘echo test’ procedure and the results were the
same as when they were routed to the subaccount. The support response 12
hours later was ‘works for us’ and then ‘check your routers and firewalls’.
****
** **
Comments? Who are other good candidates for reselling VoIP like this model?
****
** **
*Thanks,*
*Mark W. Wood*
*office:* (760)202-0224 X2010****
*Direct: *(760)459-1981****
*[image: New Image.BMP]*
www.redphonetech.com****
** **
** **
* *
** **
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Nicholas Drayer
2012-11-20 04:23:57 UTC
Permalink
We use voip.ms for three smaller not-for-profit clients. We found in the past that all our problems were due to firewalls: due to the way SIP works, firewall problems can be intermittent and vexing. Without those specific (expensive but rubbish) firewalls the problems do not occur.

On the first site have had no problems for a year now, using 15 softphones and pfSense (with HAVP and Snort) as a firewall using voip.ms' PBX features.
On a second site we have no problems over the last 3 months using 4 Polycom SoundPoint ip 335's connecting to voip.ms' PBX features.

On a third site setup a month ago, we are experiencing no problems with sipXecs 4.6 on AWS EC2 connected to voip.ms through sipXecs' built-in iptables (and the AWS security group setup properly). On this sipXecs 4.6 instance we have a backup trunk to Toronto that is registered, and we use IP authentication on the primary trunk to New York (with an inbound DID redirected using an URI to port 5080). No problems at all to date. Fingers crossed... knocking on wood, etc. We have a sipXecs alarm set on the secondary registered connection, and it did registered a drop once for a couple of minutes two weeks ago.

I would say that voip.ms' support isn't geared towards people having problems with their firewalls... I'm guessing they are usually right that it's the end-user's device, not voip.ms' servers. It must be a very frustrating job! They have always been polite and reasonably helpful to me. But don't expect emergency support within the hour, unless it really is their systems down.
Indeed, voip.ms documents somewhere on their website that they not support T.38.
As always, YMMV, in other words, it might not work for you even though it works great for me!

Nicholas Drayer
Managing Director
Dyrand Systems
T. 604.408.4415 Ext. 319
www.dyrand.com


From: sipx-users-***@list.sipfoundry.org [mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: November-19-12 4:51 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] voip.ms impression

We use voip.ms<http://voip.ms> for small occasional use and its very good for testing. Our production systems use Appia (we are a reseller) who can also provide t.38 service which we have found to work well in a production environment.

At the same time, most of our sip servers sit behind application aware firewalls and ensure connections using SIP the protocol are in now way impaired by other applications on the network. These application aware devices also have IDS and are completely cloud managed and monitored.

I would agree voip.ms<http://voip.ms> works but not always that well at every POP and they do seem to have occasional problems with call quality and completion depending on the number you call. Whether this is ISP routing, edge or internal issues at their POP is sometimes a little unclear, but they are good enough to use for failover, backup or testing but not particulary in large production environments (IMO).
On Mon, Nov 19, 2012 at 7:25 PM, Mark Wood <***@redphonetech.com<mailto:***@redphonetech.com>> wrote:
We have been using voip.ms<http://voip.ms> for 6-8 months so far and I want to get some feedback from users that have been at it for longer.

Specifically we (main and subaccounts) experience times where our outbound calls just hang after dialing and sometimes abruptly connect, or sometimes not at all. When a subaccount calls to report problems to us and we check our home page it will show all of our accounts as 'not registered', and then slowly one by one they will show as 'registered'. We had an incident over the weekend with a security office that couldn't receive any inbound calls. We logged in to the voip.ms<http://voip.ms> site to check the registrations and initiate a support ticket and the site again said 'not registered'. The instructions had us do and 'echo test' procedure and the results were the same as when they were routed to the subaccount. The support response 12 hours later was 'works for us' and then 'check your routers and firewalls'.

Comments? Who are other good candidates for reselling VoIP like this model?

Thanks,
Mark W. Wood
office: (760)202-0224 X2010
Direct: (760)459-1981
[New Image.BMP]
www.redphonetech.com<http://www.redphonetech.com>





_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org<mailto:sipx-***@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-users/



--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net<mailto:***@voice.myitdepartment.net>
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!
[http://www.ezuce.com/image/image_gallery?uuid=61c95dd3-a26d-4363-95b1-131231e1edf0&groupId=284283&t=1340112036507%22+style=%22width:+310px;+height:+310px;]<http://sipxcolab2013.eventbrite.com/?discount=tony2013>


LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net<mailto:***@voice.myitdepartment.net>

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Todd Hodgen
2012-11-20 08:06:34 UTC
Permalink
Specifically, we do not use VOIP.ms as primary service for customers. We
find they are not reliable enough. They are great for testing, quick
temporary service, occasional usage such as conference bridge, international
dialing, etc.



I don't believe their issues are related to routers in most cases. As an
example, I have three sites that have sub-accounts setup from my own
personal account with VOIP.ms. They all register to the same server at
VOIP.ms. I received error messages from all three sites that they cannot
connect to the ITSP for service, at the same time. Later, from the same
three sites, I get a message that they are now reconnected.



Each site uses a different ITSP, each site is separate and not working with
the other sites in any way. The only common thread is the service itself.
I've spoken to VOIP.ms, they claim it is not them, check the routers. 1
pfsence router, 1 watchguard, and 1 Sonicwall - go figure.



I say use VOIP.ms, it's a great service. But, don't put many eggs in that
basket.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Nicholas Drayer
Sent: Monday, November 19, 2012 8:24 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] voip.ms impression



We use voip.ms for three smaller not-for-profit clients. We found in the
past that all our problems were due to firewalls: due to the way SIP works,
firewall problems can be intermittent and vexing. Without those specific
(expensive but rubbish) firewalls the problems do not occur.



On the first site have had no problems for a year now, using 15 softphones
and pfSense (with HAVP and Snort) as a firewall using voip.ms' PBX features.

On a second site we have no problems over the last 3 months using 4 Polycom
SoundPoint ip 335's connecting to voip.ms' PBX features.



On a third site setup a month ago, we are experiencing no problems with
sipXecs 4.6 on AWS EC2 connected to voip.ms through sipXecs' built-in
iptables (and the AWS security group setup properly). On this sipXecs 4.6
instance we have a backup trunk to Toronto that is registered, and we use IP
authentication on the primary trunk to New York (with an inbound DID
redirected using an URI to port 5080). No problems at all to date. Fingers
crossed. knocking on wood, etc. We have a sipXecs alarm set on the secondary
registered connection, and it did registered a drop once for a couple of
minutes two weeks ago.



I would say that voip.ms' support isn't geared towards people having
problems with their firewalls. I'm guessing they are usually right that it's
the end-user's device, not voip.ms' servers. It must be a very frustrating
job! They have always been polite and reasonably helpful to me. But don't
expect emergency support within the hour, unless it really is their systems
down.

Indeed, voip.ms documents somewhere on their website that they not support
T.38.

As always, YMMV, in other words, it might not work for you even though it
works great for me!



Nicholas Drayer

Managing Director

Dyrand Systems

T. 604.408.4415 Ext. 319

www.dyrand.com





From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: November-19-12 4:51 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] voip.ms impression



We use voip.ms for small occasional use and its very good for testing. Our
production systems use Appia (we are a reseller) who can also provide t.38
service which we have found to work well in a production environment.



At the same time, most of our sip servers sit behind application aware
firewalls and ensure connections using SIP the protocol are in now way
impaired by other applications on the network. These application aware
devices also have IDS and are completely cloud managed and monitored.



I would agree voip.ms works but not always that well at every POP and they
do seem to have occasional problems with call quality and completion
depending on the number you call. Whether this is ISP routing, edge or
internal issues at their POP is sometimes a little unclear, but they are
good enough to use for failover, backup or testing but not particulary in
large production environments (IMO).

On Mon, Nov 19, 2012 at 7:25 PM, Mark Wood <***@redphonetech.com>
wrote:

We have been using voip.ms for 6-8 months so far and I want to get some
feedback from users that have been at it for longer.



Specifically we (main and subaccounts) experience times where our outbound
calls just hang after dialing and sometimes abruptly connect, or sometimes
not at all. When a subaccount calls to report problems to us and we check
our home page it will show all of our accounts as 'not registered', and then
slowly one by one they will show as 'registered'. We had an incident over
the weekend with a security office that couldn't receive any inbound calls.
We logged in to the voip.ms site to check the registrations and initiate a
support ticket and the site again said 'not registered'. The instructions
had us do and 'echo test' procedure and the results were the same as when
they were routed to the subaccount. The support response 12 hours later was
'works for us' and then 'check your routers and firewalls'.



Comments? Who are other good candidates for reselling VoIP like this model?



Thanks,

Mark W. Wood

office: (760)202-0224 X2010

Direct: (760)459-1981

New Image.BMP

www.redphonetech.com










_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~



Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013>






LAN/Telephony/Security and Control Systems Helpdesk:

Telephone: 434.984.8426

sip: ***@voice.myitdepartment.net



Helpdesk Customers: http://myhelp.myitdepartment.net

Blog: http://blog.myitdepartment.net
Gerald Drouillard
2012-11-20 13:04:23 UTC
Permalink
Post by Mark Wood
We have been using voip.ms for 6-8 months so far and I want to get
some feedback from users that have been at it for longer.
Specifically we (main and subaccounts) experience times where our
outbound calls just hang after dialing and sometimes abruptly connect,
or sometimes not at all. When a subaccount calls to report problems to
us and we check our home page it will show all of our accounts as 'not
registered', and then slowly one by one they will show as
'registered'. We had an incident over the weekend with a security
office that couldn't receive any inbound calls. We logged in to the
voip.ms site to check the registrations and initiate a support ticket
and the site again said 'not registered'. The instructions had us do
and 'echo test' procedure and the results were the same as when they
were routed to the subaccount. The support response 12 hours later was
'works for us' and then 'check your routers and firewalls'.
Comments? Who are other good candidates for reselling VoIP like this model?
Voip.ms is a great service if you don't need t.38. The only "problem"
is that there is something fish going on if you use registration
authentication. Time to time, you will loose registration. Fortunately
you can configure your account to be IP authentication.
http://www.drouillard.biz/blog/ip-authentication-with-sipxecs-and-voip-ms/

Their tech support has been fine with exception to the authentication
issue which I believe is a capacity issue on their side.

Other ITSP players you should check are http://www.voipinnovations.com/
and Appia if you have a lot of patience.
--
Regards
--------------------------------------
Gerald Drouillard
Technology Architect
Drouillard & Associates, Inc.
http://www.Drouillard.biz
Gerry Hull
2012-11-20 14:26:11 UTC
Permalink
Hi Mark,

I've been a voip.ms customer for 3 years. I'd say they are in the middle
of the pack. I do use a LOT of providers, though. Probably #1 in
reliability for me is flowroute.com. Less features, but rock-solid
performance. Just behind them is Anveo.com... Very good, good response
times, Top notch SOAP API, Very open to suggestions. Vitelity.com is
another provider I've used for a long time -- voip.ms resells a bunch of
their product. Vitelity has great support. Pricing for all these
provides is very competitive.

YMMV

Gerry
Post by Mark Wood
We have been using voip.ms for 6-8 months so far and I want to get some
feedback from users that have been at it for longer. ****
** **
Specifically we (main and subaccounts) experience times where our outbound
calls just hang after dialing and sometimes abruptly connect, or sometimes
not at all. When a subaccount calls to report problems to us and we check
our home page it will show all of our accounts as ‘not registered’, and
then slowly one by one they will show as ‘registered’. We had an incident
over the weekend with a security office that couldn’t receive any inbound
calls. We logged in to the voip.ms site to check the registrations and
initiate a support ticket and the site again said ‘not registered’. The
instructions had us do and ‘echo test’ procedure and the results were the
same as when they were routed to the subaccount. The support response 12
hours later was ‘works for us’ and then ‘check your routers and firewalls’.
****
** **
Comments? Who are other good candidates for reselling VoIP like this model?
****
** **
*Thanks,*
*Mark W. Wood*
*office:* (760)202-0224 X2010****
*Direct: *(760)459-1981****
*[image: New Image.BMP]*
www.redphonetech.com****
** **
** **
* *
** **
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Burleigh, Matt
2012-11-20 18:22:11 UTC
Permalink
I've recently(2 months) started using voip.ms and my support experience
has been similar. Ever since Hurricane Sandy I've had numerous issues. I
can usually restart SIP trunking to restore service and I don't always
get an alarm from sipx. I've had some recent complaints of busy signals
as well...



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Mark Wood
Sent: Monday, November 19, 2012 19:26
To: 'sipx-***@list.sipfoundry.org'
Subject: [sipx-users] voip.ms impression



We have been using voip.ms for 6-8 months so far and I want to get some
feedback from users that have been at it for longer.



Specifically we (main and subaccounts) experience times where our
outbound calls just hang after dialing and sometimes abruptly connect,
or sometimes not at all. When a subaccount calls to report problems to
us and we check our home page it will show all of our accounts as 'not
registered', and then slowly one by one they will show as 'registered'.
We had an incident over the weekend with a security office that couldn't
receive any inbound calls. We logged in to the voip.ms site to check the
registrations and initiate a support ticket and the site again said 'not
registered'. The instructions had us do and 'echo test' procedure and
the results were the same as when they were routed to the subaccount.
The support response 12 hours later was 'works for us' and then 'check
your routers and firewalls'.



Comments? Who are other good candidates for reselling VoIP like this
model?



Thanks,

Mark W. Wood

office: (760)202-0224 X2010

Direct: (760)459-1981



www.redphonetech.com
Gerald Drouillard
2012-11-20 18:45:46 UTC
Permalink
Post by Burleigh, Matt
I've recently(2 months) started using voip.ms and my support
experience has been similar. Ever since Hurricane Sandy I've had
numerous issues. I can usually restart SIP trunking to restore service
and I don't always get an alarm from sipx. I've had some recent
complaints of busy signals as well...
That should go away if you can use IP auth.
--
Regards
--------------------------------------
Gerald Drouillard
Technology Architect
Drouillard & Associates, Inc.
http://www.Drouillard.biz
Tony Graziano
2012-11-20 18:56:45 UTC
Permalink
Today alone I had two sites with a authentication issue. In one instance I
had two registrations that sipx said were authenticated. voip.ms says none
were. Restrating the gateways said they were authenticated, voip.ms still
says no. Incoming still worked even though it was not registered, which is
"wrong" but outbound would not work until we moved from seattle.

Moving one registration from seattle to NY and restart gateways... now
voip.ms agreed.

Same thing in Dallas, sipx says YES voip.ms says NO. Restart gateway, no.
Move to NY and restart, now voip.ms says yes.

I'm not particularly fond of their tech support. "It must be you". The
one constant in all this is voip.ms...

On Tue, Nov 20, 2012 at 1:22 PM, Burleigh, Matt <
I’ve recently(2 months) started using voip.ms and my support experience
has been similar. Ever since Hurricane Sandy I’ve had numerous issues. I
can usually restart SIP trunking to restore service and I don’t always get
an alarm from sipx. I’ve had some recent complaints of busy signals as
well... ****
** **
*Sent:* Monday, November 19, 2012 19:26
*Subject:* [sipx-users] voip.ms impression****
** **
We have been using voip.ms for 6-8 months so far and I want to get some
feedback from users that have been at it for longer. ****
** **
Specifically we (main and subaccounts) experience times where our outbound
calls just hang after dialing and sometimes abruptly connect, or sometimes
not at all. When a subaccount calls to report problems to us and we check
our home page it will show all of our accounts as ‘not registered’, and
then slowly one by one they will show as ‘registered’. We had an incident
over the weekend with a security office that couldn’t receive any inbound
calls. We logged in to the voip.ms site to check the registrations and
initiate a support ticket and the site again said ‘not registered’. The
instructions had us do and ‘echo test’ procedure and the results were the
same as when they were routed to the subaccount. The support response 12
hours later was ‘works for us’ and then ‘check your routers and firewalls’.
****
** **
Comments? Who are other good candidates for reselling VoIP like this model?
****
** **
*Thanks,*
*Mark W. Wood*
*office:* (760)202-0224 X2010****
*Direct: *(760)459-1981****
*[image: New Image.BMP]*
www.redphonetech.com****
** **
** **
* *
** **
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>
--
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: ***@voice.myitdepartment.net

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
Todd Hodgen
2012-11-21 03:02:59 UTC
Permalink
Yes, the Seattle switch is horrible, and I don't recommend it. They say
that Seattle and Chicago are their two newest and most up to date switches,
as well as least busy. But I can't use Seattle any longer.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: Tuesday, November 20, 2012 10:57 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] voip.ms impression



Today alone I had two sites with a authentication issue. In one instance I
had two registrations that sipx said were authenticated. voip.ms says none
were. Restrating the gateways said they were authenticated, voip.ms still
says no. Incoming still worked even though it was not registered, which is
"wrong" but outbound would not work until we moved from seattle.



Moving one registration from seattle to NY and restart gateways... now
voip.ms agreed.



Same thing in Dallas, sipx says YES voip.ms says NO. Restart gateway, no.
Move to NY and restart, now voip.ms says yes.



I'm not particularly fond of their tech support. "It must be you". The one
constant in all this is voip.ms...

On Tue, Nov 20, 2012 at 1:22 PM, Burleigh, Matt
<***@eiisolutions.net> wrote:

I've recently(2 months) started using voip.ms and my support experience has
been similar. Ever since Hurricane Sandy I've had numerous issues. I can
usually restart SIP trunking to restore service and I don't always get an
alarm from sipx. I've had some recent complaints of busy signals as well...




From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Mark Wood
Sent: Monday, November 19, 2012 19:26
To: 'sipx-***@list.sipfoundry.org'
Subject: [sipx-users] voip.ms impression



We have been using voip.ms for 6-8 months so far and I want to get some
feedback from users that have been at it for longer.



Specifically we (main and subaccounts) experience times where our outbound
calls just hang after dialing and sometimes abruptly connect, or sometimes
not at all. When a subaccount calls to report problems to us and we check
our home page it will show all of our accounts as 'not registered', and then
slowly one by one they will show as 'registered'. We had an incident over
the weekend with a security office that couldn't receive any inbound calls.
We logged in to the voip.ms site to check the registrations and initiate a
support ticket and the site again said 'not registered'. The instructions
had us do and 'echo test' procedure and the results were the same as when
they were routed to the subaccount. The support response 12 hours later was
'works for us' and then 'check your routers and firewalls'.



Comments? Who are other good candidates for reselling VoIP like this model?



Thanks,

Mark W. Wood

office: (760)202-0224 X2010

Direct: (760)459-1981

New Image.BMP

www.redphonetech.com










_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: ***@voice.myitdepartment.net
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~



Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013>






LAN/Telephony/Security and Control Systems Helpdesk:

Telephone: 434.984.8426

sip: ***@voice.myitdepartment.net



Helpdesk Customers: http://myhelp.myitdepartment.net

Blog: http://blog.myitdepartment.net
Loading...