[cisco-voip] Place to get SIP services?

Joseph A. Budz JBudz at hahnlaw.com
Tue Mar 11 13:04:34 EDT 2008


Drew,
I'm using a local provider called Fidelity. Same as you want - NO CONTRACT. If you are in or near the Ohio / Cleveland area then let me know and I'll give you there contact information. Otherwise, I understand AT&T can now offer SIP.

Thank You,

Joe A. Budz
Network Operations Manager
Hahn Loeser + Parks LLP
Phone: (216) 274-2338
Fax: (216) 274-2507
E-mail: joe at hahnlaw.com


-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of cisco-voip-request at puck.nether.net
Sent: Tuesday, March 11, 2008 11:07 AM
To: cisco-voip at puck.nether.net
Subject: cisco-voip Digest, Vol 53, Issue 89

Send cisco-voip mailing list submissions to
	cisco-voip at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
	cisco-voip-request at puck.nether.net

You can reach the person managing the list at
	cisco-voip-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."


Today's Topics:

   1. Place to get SIP services? (Drew Weaver)
   2. Re: Radio caused reboot of IP phones (Scott Voll)
   3. Re: CUCM 6.X Attendant Console (Dustin S. Fowler)


----------------------------------------------------------------------

Message: 1
Date: Tue, 11 Mar 2008 11:03:35 -0400
From: Drew Weaver <drew.weaver at thenap.com>
Subject: [cisco-voip] Place to get SIP services?
To: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
Message-ID:
	<B7152C470C9BF3448ED33F16A75D81C14D2CB1A3CD at exchanga.thenap.com>
Content-Type: text/plain; charset="us-ascii"

Howdy,

This is sort of related to Cisco, we are planning on purchasing a new telephony system and we have decided we are going to go with Cisco, but we're having a hard time getting our vendors to sell us VoIP incoming/outgoing SIP, does anyone know of a good place we can use while we are testing (not a long contract, etc)?

Sorry this is slightly off-topic.

-Drew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080311/a59d48f6/attachment-0001.html 

------------------------------

Message: 2
Date: Tue, 11 Mar 2008 07:05:21 -0800
From: "Scott Voll" <svoll.voip at gmail.com>
Subject: Re: [cisco-voip] Radio caused reboot of IP phones
To: "Brad Rogers" <BRogers at pasadenaisd.org>
Cc: cisco-voip at puck.nether.net
Message-ID:
	<f84a38d30803110805he7e48e5td34c950f4c3f936 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

UPDATE.  I believe your correct.  there are only a couple phones that this
actually does reboot.  Looking at the Hardware version makes me think your
correct.

Thanks to everyone for your help and insight.

Scott

On Tue, Mar 11, 2008 at 5:49 AM, Brad Rogers <BRogers at pasadenaisd.org>
wrote:

>  From what I understand, this is specific to a certain manufacturing run
> of 7940's and 7960's.    When they were manufactured they left out the RF
> shield.  When this happened to us we replaced some phones with new ones and
> it fixed the problem.
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *JASON BURWELL
> *Sent:* Monday, March 10, 2008 9:59 PM
> *To:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Radio caused reboot of IP phones
>
>
>
> It seems to me the more urgent concern in this situation might be the
> radio's user being exposed to that level of RF radiation on a daily basis.
> If it is sending out enough TX wattage to make a 7941 reset, that can't be
> good for the body.
>
>
>
> Jason
>
>
>  ------------------------------
>
> *From:* cisco-voip-bounces at puck.nether.net on behalf of Wes Sisk
> *Sent:* Mon 3/10/2008 4:53 PM
> *To:* Scott Voll
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Radio caused reboot of IP phones
>
> Known issue and not much we can do about it.  Phone has to be susceptible
> to RF interference by FCC rqmt.  Some phone models are more/less susceptible
> by housing insulation, but all do reset with enough RF close enough.
>
> /Wes
>
> Scott Voll wrote:
>
> Has anyone seen this before.
>
>
>
> one of our sites uses Kenwood ProTalk radios.  if you key the radio the IP
> phone (794x) phone reboots.  Totally reproducable.  Key the button reboot.
>
>
>
> Is this a know bug?  anyway to fix it?  in the event of an emergency when
> both phone an radio are needed, this could be really bad news!
>
>
>
> TIA
>
>
>
> Scott
>
> ------------------------------
>
>
>
> _______________________________________________
>
> cisco-voip mailing list
>
> cisco-voip at puck.nether.net
>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080311/d6e2e36f/attachment-0001.html 

------------------------------

Message: 3
Date: Tue, 11 Mar 2008 11:06:33 -0400
From: "Dustin S. Fowler" <dustin.s.fowler at gmail.com>
Subject: Re: [cisco-voip] CUCM 6.X Attendant Console
To: "'Ryan Ratliff'" <rratliff at cisco.com>
Cc: cisco-voip at puck.nether.net
Message-ID: <47d6a024.2586460a.0265.0d98 at mx.google.com>
Content-Type: text/plain; charset="us-ascii"

Gents,

 

I see where to change the Usernames in the service parameters but not the
passwords. Is it on a different page?

 

Dustin

 

From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Tuesday, March 11, 2008 10:24 AM
To: Dustin S. Fowler
Cc: 'Wes Sisk'; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 6.X Attendant Console

 

Remember you set both the username and password in the AC service parameters
too.  They can be whatever you wish as long as they match the application
user configured.

  

-Ryan

 

On Mar 11, 2008, at 9:09 AM, Dustin S. Fowler wrote:

 

Wes,

 

We are only LDAP. 

 

Is there another way to verify the password. I reset it manually to 12345. I
also deleted and recreated the application users altogether. 

 

Thanks

 

Dustin

 

From: Wes Sisk [mailto:wsisk at cisco.com] 
Sent: Monday, March 10, 2008 3:57 PM
To: Dustin S. Fowler
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CUCM 6.X Attendant Console

 

"Failed to do provider Login"

the password configured for the AC user under user->global directory does
not match the password configured for the AC user in the service. 
set the password under AC Server service parameters. then reset the password
for the user in ldap.

are you AD/LDAP integrated?

/Wes

Dustin S. Fowler wrote: 

All,

 

Below is an error log while trying to use the Attendant Console. I have
restarted the service. I have verified the ac and ACDeviceAuthenticationUser
users, their passwords are set to 12345. They have the following rights:

 

Standard CTI Enabled

Standard CTI Allow Control of all Devices

Standard CTI Allow Call Park Monitoring

 

 

Any ideas are welcome.

 

Dustin S Fowler

 

 

1[main]03/10 10:16:03.968 DEBUG main >>> New trace level: DEBUG

    2[main]03/10 10:16:03.968  INFO main >>> 

    3[main]03/10 10:16:03.968  INFO main >>>
**************************************

    4[main]03/10 10:16:03.968  INFO main >>> ****** Attendant Console Client
******

    5[main]03/10 10:16:03.968  INFO main >>> * Version  : 6.0(1)

    6[main]03/10 10:16:03.968  INFO main >>> * Built on : Tue May  8
02:50:11 PDT 2007

    7[main]03/10 10:16:03.968  INFO main >>>
**************************************

    8[main]03/10 10:16:03.968  INFO main >>> 

    9[main]03/10 10:16:03.968 DEBUG main >>> Command Argument 0: C:\Program
Files\Cisco\Unified Communications Manager Attendant
Console\bin\ACClient.exe

   10[main]03/10 10:16:03.984  INFO main >>> toolTip Delay = 150

   11[main]03/10 10:16:04.203 DEBUG main >>> New trace level: WARN

   12[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_File_Online in resource bundle: GlobalUI

   13[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Speeddial_Add in resource bundle: GlobalUI

   14[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Speeddial_Delete in resource bundle: GlobalUI

   15[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Speeddial_Edit in resource bundle: GlobalUI

   16[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Speeddial_NewGroup in resource bundle: GlobalUI

   17[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Speeddial_DeleteGroup in resource bundle: GlobalUI

   18[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Edit_Settings in resource bundle: GlobalUI

   19[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_TextSize_Largest in resource bundle: GlobalUI

   20[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_TextSize_Larger in resource bundle: GlobalUI

   21[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_TextSize_Medium in resource bundle: GlobalUI

   22[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_TextSize_Smaller in resource bundle: GlobalUI

   23[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_TextSize_Smallest in resource bundle: GlobalUI

   24[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Help_Help in resource bundle: GlobalUI

   25[main]03/10 10:17:44.062  WARN main >>> Cannot find key:
Menu_Accelerator_Help_About in resource bundle: GlobalUI

   26[main]03/10 10:17:44.375  WARN main >>> Cannot find key:
LineString_Unknown in resource bundle: GlobalUI

   27[main]03/10 10:17:44.375  WARN main >>> Cannot find key:
LineString_Unknown in resource bundle: GlobalUI

   28[main]03/10 10:17:44.609  WARN main >>> Cannot find key:
Menu_Accelerator_Speeddial_EditGroup in resource bundle: GlobalUI

   29[main]03/10 10:17:44.609  WARN main >>> Cannot find key:
Menu_Accelerator_Speeddial_EditGroup in resource bundle: GlobalUI

   30[main]03/10 10:17:44.687  WARN main >>> Cannot find key:
Dialog_QueuedCall_Label_String in resource bundle: Dialog

   31[Thread-13]03/10 10:17:45.437  WARN Thread-13 >>> Inside
loadUserList(): Enter

   32[Thread-12]03/10 10:20:09.484 ERROR Thread-12 >>>
ACClientTelephonyMgr.init(): Failed to do provider Login.
com.cisco.ac.common.ACException: Unable to create provider -- null

   33[Thread-12]03/10 10:20:09.484 ERROR Thread-12 >>> Exception:
com.cisco.ac.common.ACException: Failed_Telephony_Init

 

 

 

 



  _____  



 
 
 
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
  

_______________________________________________

cisco-voip mailing list

cisco-voip at puck.nether.net

https://puck.nether.net/mailman/listinfo/cisco-voip

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080311/900ae95c/attachment.html 

------------------------------

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


End of cisco-voip Digest, Vol 53, Issue 89
******************************************



More information about the cisco-voip mailing list