Send cisco-voip mailing list submissions to
        [email protected]

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
        [email protected]

You can reach the person managing the list at
        [email protected]

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


Today's Topics:

   1. Re: Issue with CME/Meridian via Q.sig (Andy Carse)
   2. Re: Wall Mount (Heim, Dennis)
   3. Re: Wall Mount (Jason Aarons (AM))
   4. CUE ISM stuck in loop (Candese Perez)
   5. CAR errors in syslog (Erick Wellnitz)


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

Message: 1
Date: Tue, 9 Jul 2013 17:57:13 +0100
From: Andy Carse <[email protected]>
To: Ryan Ratliff <[email protected]>
Cc: Cisco VoIP List <[email protected]>
Subject: Re: [cisco-voip] Issue with CME/Meridian via Q.sig
Message-ID:
        <CAJS_s=8b=uLY7TRC5uoN3OyaqiPp=vpwajscearxquvthjd...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Thanks Ryan,

I'll give it a try.
 On 9 Jul 2013 14:55, "Ryan Ratliff" <[email protected]> wrote:

> Get a PCM dump of the call to see if there is any voice coming across the
> PRI.
> https://supportforums.cisco.com/docs/DOC-14060
>
> -Ryan
>
> On Jul 8, 2013, at 5:03 PM, Andy <[email protected]> wrote:
>
> Hi,
> I have a strange issue on a deployment....
> Its a q.sig deployment with an option 11
> From Cisco handsets I can dial a meridian handset and PSTN with no issue.
> From PSTN I can dial a Cisco handset and Meridian handset with no issue.
> But if I dial from a Meridian handset to Cisco handset I get no-way voice,
> the Cisco handset rings but no voice stream.
> If I web to the cisco handset I can see the transmit/recieve packets
> incrementing, and debug isdn q931 doesn't show any errors.
> The meridian guys say its configured properly.
> I've attached an amended the config of the router.
>
> Any pointers appreciated
>
> --
> Regards
>
> Andy
>
> <router config.txt>_______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130709/4b5c6b75/attachment-0001.html>

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

Message: 2
Date: Tue, 9 Jul 2013 17:38:21 -0500
From: "Heim, Dennis" <[email protected]>
To: Ryan Ratliff <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Wall Mount
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I have a 7945 I want to mount to the kitchen wall and it has wall mount with 
the knobs that most phones you can just slide it down and I am trying to avoid 
drilling into the wall.

Dennis Heim | Sr. Unified Collaboration Team Lead & Solution Architect
World Wide Technology | 314.212.1814 | 
[email protected]<mailto:[email protected]>
"Creating Impact, Ignition & Scalability"

From: Ryan Ratliff [mailto:[email protected]]
Sent: Tuesday, July 09, 2013 9:52 AM
To: Heim, Dennis
Cc: [email protected]
Subject: Re: [cisco-voip] Wall Mount

Which phone model are you asking about?  We use wall mounts extensively here in 
the TAC and the only ones we've had issue with are the 69XX and 89/99XX models.

-Ryan

On Jul 9, 2013, at 7:49 AM, "Heim, Dennis" 
<[email protected]<mailto:[email protected]>> wrote:

I know the cisco phones wall mount screw holes do not match the standard 
spacing. Does anyone know of a face plate manufacturer that makes it for the 
spacing the Cisco has choosen?

Dennis Heim | Sr. Unified Collaboration Team Lead & Solution Architect
World Wide Technology | 314.212.1814 | 
[email protected]<mailto:[email protected]>
"Creating Impact, Ignition & Scalability"

_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130709/830586ba/attachment-0001.html>

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

Message: 3
Date: Tue, 9 Jul 2013 19:56:03 -0400
From: "Jason Aarons (AM)" <[email protected]>
To: "Heim, Dennis" <[email protected]>, Ryan Ratliff
        <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Wall Mount
Message-ID:
        
<4e38db0a1959b04c8c83edcf069b53ed0d36456...@usispclexdb01.na.didata.local>
        
Content-Type: text/plain; charset="windows-1252"

7900s have never fit a standard old school single gang flush wall mount plate 
from the 70s/80s.  New installs I usually remove the plate and use drywall 
screws with a template I made myself, must customer want to buy the formal 
Cisco Wall Mount kit in the Datasheet for the 7945 phone.

CP-WALLMOUNTKIT=

http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/phones/ps379/ps8534/product_data_sheet0900aecd8069bb80.html

From: cisco-voip [mailto:[email protected]] On Behalf Of Heim, 
Dennis
Sent: Tuesday, July 09, 2013 6:38 PM
To: Ryan Ratliff
Cc: [email protected]
Subject: Re: [cisco-voip] Wall Mount


I have a 7945 I want to mount to the kitchen wall and it has wall mount with 
the knobs that most phones you can just slide it down and I am trying to avoid 
drilling into the wall.

Dennis Heim | Sr. Unified Collaboration Team Lead & Solution Architect
World Wide Technology | 314.212.1814 | 
[email protected]<mailto:[email protected]>
"Creating Impact, Ignition & Scalability"

From: Ryan Ratliff [mailto:[email protected]]
Sent: Tuesday, July 09, 2013 9:52 AM
To: Heim, Dennis
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [cisco-voip] Wall Mount

Which phone model are you asking about?  We use wall mounts extensively here in 
the TAC and the only ones we've had issue with are the 69XX and 89/99XX models.

-Ryan

On Jul 9, 2013, at 7:49 AM, "Heim, Dennis" 
<[email protected]<mailto:[email protected]>> wrote:

I know the cisco phones wall mount screw holes do not match the standard 
spacing. Does anyone know of a face plate manufacturer that makes it for the 
spacing the Cisco has choosen?

Dennis Heim | Sr. Unified Collaboration Team Lead & Solution Architect
World Wide Technology | 314.212.1814 | 
[email protected]<mailto:[email protected]>
"Creating Impact, Ignition & Scalability"

_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip



itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130709/4e067370/attachment-0001.html>

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

Message: 4
Date: Wed, 10 Jul 2013 09:29:30 -0500
From: Candese Perez <[email protected]>
To: "[email protected] VOIP" <[email protected]>
Subject: [cisco-voip] CUE ISM stuck in loop
Message-ID:
        <CAMAHmV+g=yO+uSwfagm0MqWcjWzcEf=a1dzsxf9mj9xmtz0...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Hello,
I am attempting to install CUE on a new ISM and the ISM appears to be stuck
in a loop.

I can session to the module, and I have tried using the boot helper but
then receive a
 message that the image is corrupt.

It seems that I am missing a file or something that the loader is looking
for.  I was under the assumption I could use the cue-installer.ise.version
file.

I have also tried using the install command using ftp, but I see the router
looking for a file with a .install.sre extension.

I have been going around with this module for 2 days now, and already had
one RMA'd thinking it was a hardware issue.

Anyone have a solid solution for this?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130710/55513042/attachment-0001.html>

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

Message: 5
Date: Wed, 10 Jul 2013 10:00:24 -0500
From: Erick Wellnitz <[email protected]>
To: cisco-voip <[email protected]>
Subject: [cisco-voip] CAR errors in syslog
Message-ID:
        <cak0wosc9gcdqiyum-fxywfg6bacocih__pel9yhop1g2539...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

I found the following information regarding my errors but there is a lot of
'checking' and nothing regarding what to be looking for.

My actual error is:  %UC_CAR-3-CARSchedulerJobError: %[FailureDetail=CAR
Scheduler restarted, update ALL 4 job(s) with status: '-1','-3' to status:
'-2'.][FailureCause=Update unfinished (InProgress / Scheduled) jobs from
tbl_event_log.][JobName=4 VARIOUS JOBS][ClusterID=][NodeID=chieqpscmpb01]:
CAR scheduled job failed.

Directly before this the Cisco CAR Scheduler stops and directly after it
starts again.

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/err_msgs/8_x/ccmalarms861.html


UC_CAR-3-CARSchedulerJobError : CAR scheduled job failed. Job Name [String]
Job Failure Cause [String] Job Failure Detail [String]

*Explanation* A normal CAR scheduled job failed for some reasons.

*Recommended Action* 1. Check the status of Cisco CAR Scheduler service. 2.
Check the Event Log from CAR page. 3. Check the contents in
tbl_system_preferences table. 4. Check the number of records in
tbl_billing_data, tbl_billing_error, and tbl_error_id_map tables. 5. Check
if the scheduled job configuration is correct from CAR page. 6. Collect and
check the CAR Scheduler traces for more details.



ANy guidance would be much appreciated!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130710/52764439/attachment-0001.html>

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

Subject: Digest Footer

_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip


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

End of cisco-voip Digest, Vol 117, Issue 8
******************************************

Reply via email to