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. patch time (for some of you) (Paul)
   2. Re: uccx menu will not time out (Anthony Holloway)
   3. SIP to PRI failover on local route groups (Louis Koekemoer (ZA))
   4. Cisco Voice Implementation Checklist (Rittenhouse, Robert (LACA))
   5. E.164 without PSTN access code (Heim, Dennis)
   6. Re: SIP to PRI failover on local route groups
      (Ryan Ratliff (rratliff))
   7. Re: E.164 without PSTN access code (Nate VanMaren)
   8. Re: E.164 without PSTN access code (Jason Aarons (AM))
   9. Re: E.164 without PSTN access code (Heim, Dennis)


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

Message: 1
Date: Wed, 3 Oct 2012 10:32:34 -0700 (PDT)
From: Paul <[email protected]>
To: Cisco Vo IP Group <[email protected]>
Subject: [cisco-voip] patch time (for some of you)
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_sep12.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121003/e0c91191/attachment-0001.html>

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

Message: 2
Date: Wed, 3 Oct 2012 13:56:01 -0500
From: Anthony Holloway <[email protected]>
To: "Leetun, Rob" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] uccx menu will not time out
Message-ID:
        <cacrcjoihzatx+tuaajcp1dx0ponzxo1ve8hogdym-mjtal_...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I have not seen this and I am running 8.5(1)SU2.

A couple of things:


   - Your wav file in Caller2VM could have a lot of silence on the end,
   making it appear as though the timeout is not working.  Could you attach it?
   - I cannot see which option you have mapped to the 2VM Connection. Could
   you highlight it, then post that screenshot?
   - You didn't explain what the script is doing.  Does it repeat the
   message?  Does it go to unsuccessful?  What happens?
   - For these single option choices such as this, sometime using the
   Implicit Confirmation step is best.  It works like this:  you play a prompt
   to the caller, and if they press anykey, they "abort" the default action.
   E.g., "Press 1 for voice mail, otherwise stay on the line"  The otherwise
   part is the default action.  So if they press a key, you can catch that,
   and then Redirect to voice mail.  It's personal preference really, and thus
   up to you, but I wanted to point that out to you in case you didn't know
   what that step was for.

I look forward to your reply.

Anthony Holloway

On Tue, Oct 2, 2012 at 11:00 AM, Leetun, Rob <[email protected]>wrote:

>  Hi,****
>
> ** **
>
> Has anyone ran into this error, which the menu in uccx 8.5 will not time
> out.****
>
> ** **
>
> ****
>
> ** **
>
> ****
>
> ** **
>
> ****
>
> ** **
>
> ****
>
> ** **
>
> ****
>
> ** **
>
> Thanks.****
>
> ** **
>
> ****
>
> Rob****
>
> ** **
>
> Robert E. Leetun, CCNA, CCNA+Voice****
>
> Network Engineer****
>
> Boulder County Information Services****
>
> 2025 14th Street****
>
> Boulder, Colorado 80302****
>
> 303-441-3866 (W)****
>
> 303-441-3983 (F)****
>
> ** **
>
> _______________________________________________
> 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/20121003/bffd6df6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 35145 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121003/bffd6df6/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 19341 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121003/bffd6df6/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 40003 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121003/bffd6df6/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 36135 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121003/bffd6df6/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 37628 bytes
Desc: not available
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121003/bffd6df6/attachment-0009.png>

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

Message: 3
Date: Thu, 4 Oct 2012 09:02:40 +0000
From: "Louis Koekemoer (ZA)" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] SIP to PRI failover on local route groups
Message-ID:
        <3bd7d37efe87f747a899371ddeadf48e084a0...@zabrysvexmb02.af.didata.local>
        
Content-Type: text/plain; charset="windows-1252"

   I'm making use of local route groups. I have 4 PRI's with MGCP configuration 
to the PSTN. We also have a LCR via a SIP trunk to the CUCM. As I'm using local 
route groups, My route group contain Tom down the Sip trunk and then the 4 
PRI's. When the Sip trunk fails, I get a SIP response 503 "Service 
Unavailable." This logically sounds good, but my calls do not failover to the 
PRI's.

I'm guessing that the CUCM is expecting a different reponse. Any suggestions?


Regards

Louis Koekemoer
Principal Systems Engineer: Converged Communications
Dimension Data
Tel: +27 (11) 575 6560
Mobile: +27 (71) 680 8790
Fax: +27 (11) 576 6560
[email protected]<mailto:[email protected]>
Planned Travel -
Planned Leave - 01/12/2012 - 06/01/2013
For more information about Dimension Data, please go to  
www.dimensiondata.com<http://www.dimensiondata.com/>
P Please consider the environment before printing this email

This email and all contents are subject to the following disclaimer:

"http://www.dimensiondata.com/emaildisclaimer";
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121004/cb05aef1/attachment-0001.html>

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

Message: 4
Date: Thu, 4 Oct 2012 12:56:16 +0000
From: "Rittenhouse, Robert (LACA)" <[email protected]>
To: "cisco-voip ([email protected])"
        <[email protected]>
Subject: [cisco-voip] Cisco Voice Implementation Checklist
Message-ID:
        <c99d0bf675e0c347bbeafa21f49421bc11c30...@exch2010mbx.ourgang.laca.org>
        
Content-Type: text/plain; charset="us-ascii"

I'm starting to make an ordered checklist that can be followed for a basic 
Cisco voice implementation. Now, before I go and possibly re-create the wheel, 
does Cisco (or someone else) already provide such a checklist? I've searched 
the Internet over and I haven't found anything too promising. I am at the point 
where I am probably going to just develop one for my purposes and release it.

I also had the thought of making a web form that would first step you through 
asking the basic questions for an implementation. Then it could allow you to 
fill out all of the gory details for each building in the entire project and 
then build a PDF of the entire implementation as a TODO check-list. Would 
releasing something like this even be useful for others I wonder? I'm rather 
new to the Cisco voice implementation scene and that might be part of my want 
to over-prepare but I think that it could be a useful guide.

Thanks,

Robert Rittenhouse
Network Coordinator
Licking Area Computer Association (LACA)
(740) 345-3400 ext. 220
[email protected]<mailto:[email protected]>
________________________________
PLEASE NOTE: This message and any response to it may constitute a public 
record, and therefore may be available upon request in accordance with Ohio 
public records law. (ORC 149.43)

This e-mail message, including any attachments, is for the sole use of the 
intended recipient(s) and may contain private, confidential, and/or privileged 
information. Any unauthorized review, use, disclosure, or distribution is 
prohibited. If you are not the intended recipient, employee, or agent 
responsible for delivering this message, please contact the sender by reply 
e-mail and destroy all copies of the original e-mail message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121004/41121c7b/attachment-0001.html>

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

Message: 5
Date: Thu, 4 Oct 2012 08:28:48 -0500
From: "Heim, Dennis" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] E.164 without PSTN access code
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I am thinking of doing E.164 dialing and allowing dialing without a trunk code. 
My question is how to handle dialing 0 for an operator and the usual 
international dialing pattern of 011. I know I could do 0#, but that would be a 
change for users. What have others done regarding this?

Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: [email protected]<mailto:[email protected]>
www.wwt.com<http://www.wwt.com/>

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

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

Message: 6
Date: Thu, 4 Oct 2012 14:17:23 +0000
From: "Ryan Ratliff (rratliff)" <[email protected]>
To: "Louis Koekemoer (ZA)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SIP to PRI failover on local route groups
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"

You'll want to look at ccm traces and determine what q.850 cause cucm converts 
that 503 to and set up the "stop hunting on...? service parameter 
appropriately. I'm not sure offhand what that one will be.

"Louis Koekemoer (ZA)" <[email protected]> wrote:




I?m making use of local route groups. I have 4 PRI?s with MGCP configuration to 
the PSTN. We also have a LCR via a SIP trunk to the CUCM. As I?m using local 
route groups, My route group contain Tom down the Sip trunk and then the 4 
PRI?s. When the Sip trunk fails, I get a SIP response 503 "Service 
Unavailable." This logically sounds good, but my calls do not failover to the 
PRI?s.

I?m guessing that the CUCM is expecting a different reponse. Any suggestions?


Regards

Louis Koekemoer
Principal Systems Engineer: Converged Communications
Dimension Data
Tel: +27 (11) 575 6560
Mobile: +27 (71) 680 8790
Fax: +27 (11) 576 6560
[email protected]<mailto:[email protected]>
Planned Travel ?
Planned Leave - 01/12/2012 ? 06/01/2013
For more information about Dimension Data, please go to  
www.dimensiondata.com<http://www.dimensiondata.com/>
P Please consider the environment before printing this email



This email and all contents are subject to the following disclaimer:
"http://www.dimensiondata.com/emaildisclaimer";<http://www.dimensiondata.com/emaildisclaimer>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121004/304cc582/attachment-0001.html>

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

Message: 7
Date: Thu, 4 Oct 2012 14:24:02 +0000
From: Nate VanMaren <[email protected]>
To: "Heim, Dennis" <[email protected]>, "[email protected]"
        <[email protected]>
Subject: Re: [cisco-voip] E.164 without PSTN access code
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

How does the PSTN handle it?

I have to assume inter digit timeout.

From: [email protected] 
[mailto:[email protected]] On Behalf Of Heim, Dennis
Sent: Thursday, October 04, 2012 7:29 AM
To: [email protected]
Subject: [cisco-voip] E.164 without PSTN access code

I am thinking of doing E.164 dialing and allowing dialing without a trunk code. 
My question is how to handle dialing 0 for an operator and the usual 
international dialing pattern of 011. I know I could do 0#, but that would be a 
change for users. What have others done regarding this?

Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: [email protected]<mailto:[email protected]>
www.wwt.com<http://www.wwt.com/>

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

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

Message: 8
Date: Thu, 4 Oct 2012 11:49:43 -0400
From: "Jason Aarons (AM)" <[email protected]>
To: Nate VanMaren <[email protected]>, "Heim, Dennis"
        <[email protected]>, "[email protected]"
        <[email protected]>
Subject: Re: [cisco-voip] E.164 without PSTN access code
Message-ID:
        
<4e38db0a1959b04c8c83edcf069b53ed0d2a174...@usispclexdb01.na.didata.local>
        
Content-Type: text/plain; charset="windows-1252"

At the gateway you convert to how carrier wants to see it -jason

The newer loads you can press * for 2 seconds and a plus sign appears on phone 
display.

From: [email protected] 
[mailto:[email protected]] On Behalf Of Nate VanMaren
Sent: Thursday, October 04, 2012 10:24 AM
To: Heim, Dennis; [email protected]
Subject: Re: [cisco-voip] E.164 without PSTN access code


How does the PSTN handle it?

I have to assume inter digit timeout.

From: [email protected] 
[mailto:[email protected]] On Behalf Of Heim, Dennis
Sent: Thursday, October 04, 2012 7:29 AM
To: [email protected]
Subject: [cisco-voip] E.164 without PSTN access code

I am thinking of doing E.164 dialing and allowing dialing without a trunk code. 
My question is how to handle dialing 0 for an operator and the usual 
international dialing pattern of 011. I know I could do 0#, but that would be a 
change for users. What have others done regarding this?

Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: [email protected]<mailto:[email protected]>
www.wwt.com<http://www.wwt.com/>



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

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

Message: 9
Date: Thu, 4 Oct 2012 10:54:08 -0500
From: "Heim, Dennis" <[email protected]>
To: "Jason Aarons (AM)" <[email protected]>, Nate
        VanMaren <[email protected]>, "[email protected]"
        <[email protected]>
Subject: Re: [cisco-voip] E.164 without PSTN access code
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I just found that out, which I think is fantastic.

Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: [email protected]<mailto:[email protected]>
www.wwt.com<http://www.wwt.com/>

From: Jason Aarons (AM) [mailto:[email protected]]
Sent: Thursday, October 04, 2012 11:50 AM
To: Nate VanMaren; Heim, Dennis; [email protected]
Subject: RE: E.164 without PSTN access code

At the gateway you convert to how carrier wants to see it -jason

The newer loads you can press * for 2 seconds and a plus sign appears on phone 
display.

From: 
[email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of Nate VanMaren
Sent: Thursday, October 04, 2012 10:24 AM
To: Heim, Dennis; [email protected]<mailto:[email protected]>
Subject: Re: [cisco-voip] E.164 without PSTN access code


How does the PSTN handle it?

I have to assume inter digit timeout.

From: 
[email protected]<mailto:[email protected]> 
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
 On Behalf Of Heim, Dennis
Sent: Thursday, October 04, 2012 7:29 AM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] E.164 without PSTN access code

I am thinking of doing E.164 dialing and allowing dialing without a trunk code. 
My question is how to handle dialing 0 for an operator and the usual 
international dialing pattern of 011. I know I could do 0#, but that would be a 
change for users. What have others done regarding this?

Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: [email protected]<mailto:[email protected]>
www.wwt.com<http://www.wwt.com/>



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

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

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


End of cisco-voip Digest, Vol 108, Issue 4
******************************************

Reply via email to