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: SX20 Telepresence software upgrade (James Dust)
2. Hardware limitation of the EX90 (John Snow)
3. Re: SX20 Telepresence software upgrade (Chris Ward (chrward))
4. Re: Problem with 2921 and t.38 (Amit Kumar)
5. Re: CER not seeing CUCM (Pawlowski, Adam)
6. Re: CER not seeing CUCM (Jason Burns)
7. Re: SX20 Telepresence software upgrade (Ryan Ratliff (rratliff))
8. Call Stays in Queue When All Agents Log Out - UCCE, ICM
(Ryan Burtch)
9. Re: CER not seeing CUCM (Erick Wellnitz)
10. VPN Question (Ryan Burtch)
11. Re: VPN Question (Garrett Skjelstad)
12. Forced Authorization Code wait always 15sec before route call
(Alice Borgo)
13. Re: Call Stays in Queue When All Agents Log Out - UCCE, ICM
(Beck, Christopher)
14. Prefix for Missed Calls (Lisa Notarianni)
15. Re: Prefix for Missed Calls (Haas, Neal)
16. Re: Prefix for Missed Calls (Heim, Dennis)
17. Re: Prefix for Missed Calls (Mike )
18. Re: Prefix for Missed Calls (Brian Meade (brmeade))
----------------------------------------------------------------------
Message: 1
Date: Wed, 11 Sep 2013 16:04:19 +0000
From: James Dust <[email protected]>
To: "Chris Ward (chrward)" <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SX20 Telepresence software upgrade
Message-ID:
<b5861604ffbff545ba7bdd7763e6c3fc543c5...@csexmbox04.charles-stanley.co.uk>
Content-Type: text/plain; charset="us-ascii"
Afternoon Chris,
Yes I have restarted the TFTP service on all nodes, and it was a cop file I
used to upload the firmware.
The device defaults page has been updated and no specific phone load is
specified on the devices themselves.
Thanks for sanity checking this for me, I may need to log a support case now
then.
Kind Regards
James
From: Chris Ward (chrward) [mailto:[email protected]]
Sent: 11 September 2013 16:54
To: James Dust; [email protected]
Subject: RE: SX20 Telepresence software upgrade
Hi James,
Have you started TFTP on the TFTP server? That would be required after a cop
file install or manual file upload to the TFTP directory.
Also, check the device defaults for the SX20 and see if there is a version
specified, if not, specify one. A COP file installation should have done this
for you, but a manual upload would not. Also, make sure that a firmware load is
NOT defined on the device's page itself (ccmadmin) as this will override the
device default page.
That is my normal list of things to check/do for phones that aren't upgrading
as expected.
+Chris
TME - Unity Connection and MediaSense
From: cisco-voip
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
On Behalf Of James Dust
Sent: Wednesday, September 11, 2013 11:06 AM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] SX20 Telepresence software upgrade
Afternoon all,
I am trying to upgrade some SX20 devices on our 8.6.2 cucm cluster from version
TC5.1.5 to TC6.1.1 but am encountering difficulties. I have installed the new
software on all cucm nodes and hard reset/factory reset the SX20's to try and
get them to upgrade but they don't pick up the new default software image.
Has anyone else encountered this problem? And if so what do you need to do?
On a side note I realise you need to update the release key for the device when
you upgrade and have this covered.
Kind regards
James
Consider the environment - Think before you print
The contents of this email are confidential to the intended recipient and may
not be disclosed. Although it is believed that this email and any attachments
are virus free, it is the responsibility of the recipient to confirm this.
You are advised that urgent, time-sensitive communications should not be sent
by email. We hereby give you notice that a delivery receipt does not constitute
acknowledgement or receipt by the intended recipient(s).
Details of Charles Stanley group companies and their regulators (where
applicable), can be found at this URL
http://www.charles-stanley.co.uk/contact-us/disclosure/
Consider the environment - Think before you print
The contents of this email are confidential to the intended recipient and may
not be disclosed. Although it is believed that this email and any attachments
are virus free, it is the responsibility of the recipient to confirm this.
You are advised that urgent, time-sensitive communications should not be sent
by email. We hereby give you notice that a delivery receipt does not constitute
acknowledgement or receipt by the intended recipient(s).
Details of Charles Stanley group companies and their regulators (where
applicable), can be found at this URL
http://www.charles-stanley.co.uk/contact-us/disclosure/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130911/878816df/attachment-0001.html>
------------------------------
Message: 2
Date: Wed, 11 Sep 2013 16:06:08 +0000
From: John Snow <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Hardware limitation of the EX90
Message-ID:
<7b3fb7d232fc5e46a5ecd865ec67b274192ef...@lvscgyex03.longviewsystems.com>
Content-Type: text/plain; charset="us-ascii"
I just deployed a couple EX90's local to CUCM 9.1, but I notice there is
limitation on the DN of max 4 calls. It seems odd that I can have up to 200
calls theoretically on the DN for any SCCP 79XX phone but only 4 on this
device. If I bridge this to an MCU does that remove the limitation? I don't
see a specific number defined in any of the documentation.
Can someone from Cisco confirm this or anyone else know the answer?
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130911/9cedb7b0/attachment-0001.html>
------------------------------
Message: 3
Date: Wed, 11 Sep 2013 16:21:44 +0000
From: "Chris Ward (chrward)" <[email protected]>
To: James Dust <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [cisco-voip] SX20 Telepresence software upgrade
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
James,
It's also possible that the load they running while CUCM compatible weren't yet
capable of downloading firmware from CUCM. I am not sure in the history of TC
code where that capability was added.
+Chris
TME - Unity Connection and MediaSense
From: James Dust [mailto:[email protected]]
Sent: Wednesday, September 11, 2013 12:04 PM
To: Chris Ward (chrward); [email protected]
Subject: RE: SX20 Telepresence software upgrade
Afternoon Chris,
Yes I have restarted the TFTP service on all nodes, and it was a cop file I
used to upload the firmware.
The device defaults page has been updated and no specific phone load is
specified on the devices themselves.
Thanks for sanity checking this for me, I may need to log a support case now
then.
Kind Regards
James
From: Chris Ward (chrward) [mailto:[email protected]]
Sent: 11 September 2013 16:54
To: James Dust; [email protected]<mailto:[email protected]>
Subject: RE: SX20 Telepresence software upgrade
Hi James,
Have you started TFTP on the TFTP server? That would be required after a cop
file install or manual file upload to the TFTP directory.
Also, check the device defaults for the SX20 and see if there is a version
specified, if not, specify one. A COP file installation should have done this
for you, but a manual upload would not. Also, make sure that a firmware load is
NOT defined on the device's page itself (ccmadmin) as this will override the
device default page.
That is my normal list of things to check/do for phones that aren't upgrading
as expected.
+Chris
TME - Unity Connection and MediaSense
From: cisco-voip
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
On Behalf Of James Dust
Sent: Wednesday, September 11, 2013 11:06 AM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] SX20 Telepresence software upgrade
Afternoon all,
I am trying to upgrade some SX20 devices on our 8.6.2 cucm cluster from version
TC5.1.5 to TC6.1.1 but am encountering difficulties. I have installed the new
software on all cucm nodes and hard reset/factory reset the SX20's to try and
get them to upgrade but they don't pick up the new default software image.
Has anyone else encountered this problem? And if so what do you need to do?
On a side note I realise you need to update the release key for the device when
you upgrade and have this covered.
Kind regards
James
Consider the environment - Think before you print
The contents of this email are confidential to the intended recipient and may
not be disclosed. Although it is believed that this email and any attachments
are virus free, it is the responsibility of the recipient to confirm this.
You are advised that urgent, time-sensitive communications should not be sent
by email. We hereby give you notice that a delivery receipt does not constitute
acknowledgement or receipt by the intended recipient(s).
Details of Charles Stanley group companies and their regulators (where
applicable), can be found at this URL
http://www.charles-stanley.co.uk/contact-us/disclosure/
Consider the environment - Think before you print
The contents of this email are confidential to the intended recipient and may
not be disclosed. Although it is believed that this email and any attachments
are virus free, it is the responsibility of the recipient to confirm this.
You are advised that urgent, time-sensitive communications should not be sent
by email. We hereby give you notice that a delivery receipt does not constitute
acknowledgement or receipt by the intended recipient(s).
Details of Charles Stanley group companies and their regulators (where
applicable), can be found at this URL
http://www.charles-stanley.co.uk/contact-us/disclosure/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130911/70014131/attachment-0001.html>
------------------------------
Message: 4
Date: Wed, 11 Sep 2013 21:32:22 +0530
From: Amit Kumar <[email protected]>
To: Reto Gassmann <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Problem with 2921 and t.38
Message-ID:
<cahasel5dfxuwevp8mhhnw12cs4fcxhuzmk6vutnf7z2zn5y...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Here are some points , we should be looking at.
Does fax transmission fails for same fax numbers, all the time or its
random. ?
In which stage fax fails, during switchover or it's not doing switchover at
all ?
Are we using NSE based, switch over or protocol ?
Faxes are connected with FXS port of same router ?
MGCP & Skinny or H.323 ?
Thanks,
Amit
On Tue, Sep 10, 2013 at 1:27 AM, Reto Gassmann <[email protected]> wrote:
> Hello Group
>
>
> we have to renew our gateways and have now new 2921 router with pri
> interfaces.
>
>
> now we have Problems sending and receving faxes with t.38. Most of the
> faxes can be sent and received without any problem. However some are not
> transmitted at all. Has anyone a similar situation and can give me some
> hints on how to configure the gateways and waht IOS we could load in order
> to get all the faxes to be sent and received.
>
>
> thank you for any hints
>
> Regrds Reto
>
>
> GW#sh ver
>
> Cisco IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version
> 15.3(2)T, RELEASE SOFTWARE (fc3)
>
> Technical Support: http://www.cisco.com/techsupport
>
> Copyright (c) 1986-2013 by Cisco Systems, Inc.
>
> Compiled Thu 28-Mar-13 11:05 by prod_rel_team
>
>
>
> ROM: System Bootstrap, Version 15.0(1r)M16, RELEASE SOFTWARE (fc1)
>
>
>
> GW uptime is 14 weeks, 4 days, 2 hours, 23 minutes
>
> System returned to ROM by power-on
>
> System restarted at 11:53:45 MEZ Thu May 30 2013
>
> System image file is "flash:c2900-universalk9-mz.SPA.153-2.T.bin"
>
> Last reload type: Normal Reload
>
> Last reload reason: power-on
>
>
> Cisco CISCO2921/K9 (revision 1.0) with 479232K/45056K bytes of memory.
>
> Processor board ID xxx
>
> 3 Gigabit Ethernet interfaces
>
> 124 Serial interfaces
>
> 1 terminal line
>
> 4 Channelized E1/PRI ports
>
> DRAM configuration is 64 bits wide with parity enabled.
>
> 255K bytes of non-volatile configuration memory.
>
> 250880K bytes of ATA System CompactFlash 0 (Read/Write)
>
>
>
>
>
> License Info:
>
>
>
> License UDI:
>
>
>
> -------------------------------------------------
>
> Device# PID SN
>
> -------------------------------------------------
>
> *0 CISCO xxx
>
>
>
> Technology Package License Information for Module:'c2900'
>
>
>
> -----------------------------------------------------------------
>
> Technology Technology-package Technology-package
>
> Current Type Next reboot
>
> ------------------------------------------------------------------
>
> ipbase ipbasek9 Permanent ipbasek9
>
> security None None None
>
> uc uck9 Permanent uck9
>
> data None None None
>
>
>
> Configuration register is 0x2102
>
> _______________________________________________
> 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/20130911/f6ca41fe/attachment-0001.html>
------------------------------
Message: 5
Date: Wed, 11 Sep 2013 13:41:33 -0400
From: "Pawlowski, Adam" <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] CER not seeing CUCM
Message-ID:
<1361b9676b9a41448eb672b89aa7731f19eff25...@mbccr5.itorg.ad.buffalo.edu>
Content-Type: text/plain; charset="us-ascii"
I had this problem myself when moving things around - it needs SNMP
reachability, using the same or one of the community strings defined in CER
(that wasn't clear to me in the documentation). If you've changed the UCM
nodes around though I found I had to delete the call manager and re-add it for
it to work. This also meant waiting ages for phone tracking to fail out before
it could be done.
Adam P
SUNYAB
--
Message: 1
Date: Tue, 10 Sep 2013 13:31:08 -0500
From: Erick Wellnitz <[email protected]>
To: cisco-voip <[email protected]>
Subject: [cisco-voip] CER not seeing CUCM
Message-ID:
<CAK0wOsBbeBGyLySxET8Ms9946Ywa__z6JoA6Y4NowPVt4LS=y...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I had this issue before and I can't find my notes on it.
In CER when I click on Cisco Unified Communications Managers
List<https://10.2.146.60:8443/ceradmin/servlet/CERAdminServlet#> I see no
results. I thought I followed the install and config document exactly.
Any help is much appreciated!
------------------------------
Message: 6
Date: Wed, 11 Sep 2013 14:02:21 -0400
From: Jason Burns <[email protected]>
To: "Pawlowski, Adam" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] CER not seeing CUCM
Message-ID:
<cagmgrw8usrjfrqurgy0stf3epsbadtg1py4+o4twphszdvj...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
I second Joe's recommendation to make sure CER is pointed to a server
running CallManager AND that all servers are configured for SNMP.
This has caused me problems TWICE before where I pointed CER to a publisher
that wasn't running CCM and I had the same symptoms. There should be some
note / defect about this.
On Wed, Sep 11, 2013 at 1:41 PM, Pawlowski, Adam <[email protected]> wrote:
> I had this problem myself when moving things around - it needs SNMP
> reachability, using the same or one of the community strings defined in CER
> (that wasn't clear to me in the documentation). If you've changed the UCM
> nodes around though I found I had to delete the call manager and re-add it
> for it to work. This also meant waiting ages for phone tracking to fail out
> before it could be done.
>
> Adam P
> SUNYAB
>
> --
>
> Message: 1
> Date: Tue, 10 Sep 2013 13:31:08 -0500
> From: Erick Wellnitz <[email protected]>
> To: cisco-voip <[email protected]>
> Subject: [cisco-voip] CER not seeing CUCM
> Message-ID:
> <CAK0wOsBbeBGyLySxET8Ms9946Ywa__z6JoA6Y4NowPVt4LS=
> [email protected]>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I had this issue before and I can't find my notes on it.
>
> In CER when I click on Cisco Unified Communications Managers List<
> https://10.2.146.60:8443/ceradmin/servlet/CERAdminServlet#> I see no
> results. I thought I followed the install and config document exactly.
>
> Any help is much appreciated!
>
> _______________________________________________
> 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/20130911/c5672446/attachment-0001.html>
------------------------------
Message: 7
Date: Wed, 11 Sep 2013 18:52:10 +0000
From: "Ryan Ratliff (rratliff)" <[email protected]>
To: James Dust <[email protected]>
Cc: cisco-voip voyp list <[email protected]>
Subject: Re: [cisco-voip] SX20 Telepresence software upgrade
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="windows-1252"
Do you have the CUCM set as the provisioning server?
-Ryan
On Sep 11, 2013, at 12:21 PM, Chris Ward (chrward)
<[email protected]<mailto:[email protected]>> wrote:
James,
It?s also possible that the load they running while CUCM compatible weren?t yet
capable of downloading firmware from CUCM. I am not sure in the history of TC
code where that capability was added.
+Chris
TME - Unity Connection and MediaSense
From: James Dust
[mailto:[email protected]<http://charles-stanley.co.uk>]
Sent: Wednesday, September 11, 2013 12:04 PM
To: Chris Ward (chrward);
[email protected]<mailto:[email protected]>
Subject: RE: SX20 Telepresence software upgrade
Afternoon Chris,
Yes I have restarted the TFTP service on all nodes, and it was a cop file I
used to upload the firmware.
The device defaults page has been updated and no specific phone load is
specified on the devices themselves.
Thanks for sanity checking this for me, I may need to log a support case now
then.
Kind Regards
James
From: Chris Ward (chrward) [mailto:[email protected]]
Sent: 11 September 2013 16:54
To: James Dust; [email protected]<mailto:[email protected]>
Subject: RE: SX20 Telepresence software upgrade
Hi James,
Have you started TFTP on the TFTP server? That would be required after a cop
file install or manual file upload to the TFTP directory.
Also, check the device defaults for the SX20 and see if there is a version
specified, if not, specify one. A COP file installation should have done this
for you, but a manual upload would not. Also, make sure that a firmware load is
NOT defined on the device?s page itself (ccmadmin) as this will override the
device default page.
That is my normal list of things to check/do for phones that aren?t upgrading
as expected.
+Chris
TME - Unity Connection and MediaSense
From: cisco-voip
[mailto:[email protected]]<mailto:[mailto:[email protected]]>
On Behalf Of James Dust
Sent: Wednesday, September 11, 2013 11:06 AM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] SX20 Telepresence software upgrade
Afternoon all,
I am trying to upgrade some SX20 devices on our 8.6.2 cucm cluster from version
TC5.1.5 to TC6.1.1 but am encountering difficulties. I have installed the new
software on all cucm nodes and hard reset/factory reset the SX20?s to try and
get them to upgrade but they don?t pick up the new default software image.
Has anyone else encountered this problem? And if so what do you need to do?
On a side note I realise you need to update the release key for the device when
you upgrade and have this covered.
Kind regards
James
Consider the environment - Think before you print
The contents of this email are confidential to the intended recipient and may
not be disclosed. Although it is believed that this email and any attachments
are virus free, it is the responsibility of the recipient to confirm this.
You are advised that urgent, time-sensitive communications should not be sent
by email. We hereby give you notice that a delivery receipt does not constitute
acknowledgement or receipt by the intended recipient(s).
Details of Charles Stanley group companies and their regulators (where
applicable), can be found at this URL
http://www.charles-stanley.co.uk/contact-us/disclosure/
Consider the environment - Think before you print
The contents of this email are confidential to the intended recipient and may
not be disclosed. Although it is believed that this email and any attachments
are virus free, it is the responsibility of the recipient to confirm this.
You are advised that urgent, time-sensitive communications should not be sent
by email. We hereby give you notice that a delivery receipt does not constitute
acknowledgement or receipt by the intended recipient(s).
Details of Charles Stanley group companies and their regulators (where
applicable), can be found at this URL
http://www.charles-stanley.co.uk/contact-us/disclosure/
_______________________________________________
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/20130911/a20fe9df/attachment-0001.html>
------------------------------
Message: 8
Date: Wed, 11 Sep 2013 16:29:11 -0400
From: Ryan Burtch <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Call Stays in Queue When All Agents Log Out -
UCCE, ICM
Message-ID:
<cak+shf4kvcg0xv2-iuy9z_huex6ejtmsdoabmjzyx02hrrz...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
All:
I have an issue with an ICM script that is not tearing down a queued call
when all agents log out. I know this isn't a typical issue, but has anyone
figured out how to deal with this scenario. Call is being queued in ICM
via the queue to skill group node.
Sincerely,
Ryan Burtch
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130911/cb2b13f4/attachment-0001.html>
------------------------------
Message: 9
Date: Wed, 11 Sep 2013 15:30:26 -0500
From: Erick Wellnitz <[email protected]>
To: Jason Burns <[email protected]>
Cc: "[email protected]" <[email protected]>,
"Pawlowski, Adam" <[email protected]>
Subject: Re: [cisco-voip] CER not seeing CUCM
Message-ID:
<CAK0wOsAQ7sekGeKC_b8CNQN8h9OCye6NG=gcdk_42h0fd0c...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
That is exactly what the issue was. My publisher doesn't run the
CallManager service.
On Wed, Sep 11, 2013 at 1:02 PM, Jason Burns <[email protected]> wrote:
> I second Joe's recommendation to make sure CER is pointed to a server
> running CallManager AND that all servers are configured for SNMP.
>
> This has caused me problems TWICE before where I pointed CER to a
> publisher that wasn't running CCM and I had the same symptoms. There should
> be some note / defect about this.
>
>
> On Wed, Sep 11, 2013 at 1:41 PM, Pawlowski, Adam <[email protected]>wrote:
>
>> I had this problem myself when moving things around - it needs SNMP
>> reachability, using the same or one of the community strings defined in CER
>> (that wasn't clear to me in the documentation). If you've changed the UCM
>> nodes around though I found I had to delete the call manager and re-add it
>> for it to work. This also meant waiting ages for phone tracking to fail out
>> before it could be done.
>>
>> Adam P
>> SUNYAB
>>
>> --
>>
>> Message: 1
>> Date: Tue, 10 Sep 2013 13:31:08 -0500
>> From: Erick Wellnitz <[email protected]>
>> To: cisco-voip <[email protected]>
>> Subject: [cisco-voip] CER not seeing CUCM
>> Message-ID:
>> <CAK0wOsBbeBGyLySxET8Ms9946Ywa__z6JoA6Y4NowPVt4LS=
>> [email protected]>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> I had this issue before and I can't find my notes on it.
>>
>> In CER when I click on Cisco Unified Communications Managers List<
>> https://10.2.146.60:8443/ceradmin/servlet/CERAdminServlet#> I see no
>> results. I thought I followed the install and config document exactly.
>>
>> Any help is much appreciated!
>>
>> _______________________________________________
>> cisco-voip mailing list
>> [email protected]
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
>
> _______________________________________________
> 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/20130911/b7e96d99/attachment-0001.html>
------------------------------
Message: 10
Date: Thu, 12 Sep 2013 00:26:11 -0400
From: Ryan Burtch <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] VPN Question
Message-ID:
<cak+shf6dezd66wffjkxmkyahs26cvjsomzzsuwo1uc6eqeg...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
All:
I know this isn't a networking list, but I'm trying to setup my computer to
connect to 2 VPNs at the same time. Both have been configured to allow
split tunneling, but whenever they are both connected, I am unable to
access too the necessary Internal resources for each VPN. Does anyone know
how to get this to work?
Sincerely,
Ryan Burtch
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/13b00bd6/attachment-0001.html>
------------------------------
Message: 11
Date: Wed, 11 Sep 2013 22:25:49 -0700
From: Garrett Skjelstad <[email protected]>
To: Ryan Burtch <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] VPN Question
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
Windows doesn't support two IPSec VPN clients on the same PC.
I am not sure about Mac or Linux.
Sent from my (old) iPhone5
On Sep 11, 2013, at 21:26, Ryan Burtch <[email protected]> wrote:
> All:
>
> I know this isn't a networking list, but I'm trying to setup my computer to
> connect to 2 VPNs at the same time. Both have been configured to allow split
> tunneling, but whenever they are both connected, I am unable to access too
> the necessary Internal resources for each VPN. Does anyone know how to get
> this to work?
>
>
>
> Sincerely,
>
> Ryan Burtch
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
Message: 12
Date: Thu, 12 Sep 2013 09:51:19 +0200
From: "Alice Borgo" <[email protected]>
To: <[email protected]>
Subject: [cisco-voip] Forced Authorization Code wait always 15sec
before route call
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"
Hello Guys,
I've this problem.
CUCM 9.1.1 - Phone Firmware 9.3.3.2
FAC implemented for External call.
Phone request to insert code when needed, insert code and after press # key
to route immediately the Call, but system ignore it. Alway wait 15 seconds
before route the call.
Modified T302 Timer to 5 second, nothing!!!
Any Idea?
Thank you!
Regards
Alessandro Bertacco
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/882fb9a9/attachment-0001.html>
------------------------------
Message: 13
Date: Thu, 12 Sep 2013 08:24:40 -0500
From: "Beck, Christopher" <[email protected]>
To: Ryan Burtch <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [cisco-voip] Call Stays in Queue When All Agents Log Out
- UCCE, ICM
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
I run a check in the script section that executes while the call is in queue to
see if all agents have logged out. If so, I cancel queuing and process
accordingly.
From: cisco-voip [mailto:[email protected]] On Behalf Of Ryan
Burtch
Sent: Wednesday, September 11, 2013 3:29 PM
To: [email protected]
Subject: [cisco-voip] Call Stays in Queue When All Agents Log Out - UCCE, ICM
All:
I have an issue with an ICM script that is not tearing down a queued call when
all agents log out. I know this isn't a typical issue, but has anyone figured
out how to deal with this scenario. Call is being queued in ICM via the queue
to skill group node.
Sincerely,
Ryan Burtch
Confidentiality Notice: This email is intended for the sole use of the intended
recipient(s) and may contain confidential, proprietary or privileged
information.
If you are not the intended recipient, you are notified that any use, review,
dissemination, copying or action taken based on this message or its
attachments,
if any, is prohibited. If you are not the intended recipient, please contact
the
sender by reply email and destroy or delete all copies of the original message
and any attachments. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/ec2ae721/attachment-0001.html>
------------------------------
Message: 14
Date: Thu, 12 Sep 2013 14:30:52 +0000
From: Lisa Notarianni <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Prefix for Missed Calls
Message-ID:
<b1d1594f698e684db83c15828d282dd874642...@sn2prd0310mb359.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
(Call Manager 8.6.6)
Has anyone ever successfully utilized translation patterns to prefix 91 so that
when Dial is pressed in Missed or Received Calls, it will automatically
populate the 91 for calls that were missed or received from outside of network
callers?
We had done some testing but it caused an overlap in route patterns which
therefore caused a timeout delay for internal calling.
Here is what we built:
{2-9]xx xxx xxxx would automatically add 91 prefix
[2-9]xxx Is for internal calling
If an internal call was made for example to 4357, Call Manager would wait to
see if the caller was done dialing and after about 15 seconds it would time out
and then the call would go through. The system was comparing the 2 route
patterns above and was not sure which was being used which caused the delay.
I know there are other suggested ways of accomplishing this but if there is a
workaround to Cisco?s preferred way of showing 91 prefix on each incoming call
we would rather that.
Thank you in advance.
Lisa
[LisaNotarianniSignature]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/9ef9e2dd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 10828 bytes
Desc: image001.gif
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/9ef9e2dd/attachment-0001.gif>
------------------------------
Message: 15
Date: Thu, 12 Sep 2013 14:37:49 +0000
From: "Haas, Neal" <[email protected]>
To: Lisa Notarianni <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Prefix for Missed Calls
Message-ID:
<3bfada3c46e5a4428c76dc87fcf5fade4a65a...@cofmail03.intra.co.fresno.ca.us>
Content-Type: text/plain; charset="utf-8"
No, I tried to work on this same area for several months but never did anything
except for create overlapping dial plans.
I was told the easiest thing to do was to create a phone service that would
take care of this for you. I have never had time to look into this.
Neal Haas
From: cisco-voip [mailto:[email protected]] On Behalf Of Lisa
Notarianni
Sent: Thursday, September 12, 2013 7:31 AM
To: [email protected]
Subject: [cisco-voip] Prefix for Missed Calls
(Call Manager 8.6.6)
Has anyone ever successfully utilized translation patterns to prefix 91 so that
when Dial is pressed in Missed or Received Calls, it will automatically
populate the 91 for calls that were missed or received from outside of network
callers?
We had done some testing but it caused an overlap in route patterns which
therefore caused a timeout delay for internal calling.
Here is what we built:
{2-9]xx xxx xxxx would automatically add 91 prefix
[2-9]xxx Is for internal calling
If an internal call was made for example to 4357, Call Manager would wait to
see if the caller was done dialing and after about 15 seconds it would time out
and then the call would go through. The system was comparing the 2 route
patterns above and was not sure which was being used which caused the delay.
I know there are other suggested ways of accomplishing this but if there is a
workaround to Cisco?s preferred way of showing 91 prefix on each incoming call
we would rather that.
Thank you in advance.
Lisa
[LisaNotarianniSignature]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/e2af9624/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 10828 bytes
Desc: image001.gif
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/e2af9624/attachment-0001.gif>
------------------------------
Message: 16
Date: Thu, 12 Sep 2013 09:42:59 -0500
From: "Heim, Dennis" <[email protected]>
To: "Haas, Neal" <[email protected]>, Lisa Notarianni
<[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [cisco-voip] Prefix for Missed Calls
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
If you have transformation patterns, you should use them.
At the ingress gateway you append the necessary digits, a 9 or 91, based on the
CSS. On the phone you use the calling party transformation, to have a css that
contains a partition that has a transformation pattern that will strip off the
necessary digits, like 9, 91, from the display of the phone.
If you need more details let me know. This will make it so when the call comes
in you see the 10 digits, and when you hit the missed calls directory the 9 or
91 or already populated.
Dennis Heim | Solution Architect (Collaboration)
World Wide Technology, Inc. | 314-212-1814
PS Engineering: Innovate & Ignite.
From: cisco-voip [mailto:[email protected]] On Behalf Of Haas,
Neal
Sent: Thursday, September 12, 2013 7:38 AM
To: Lisa Notarianni; [email protected]
Subject: Re: [cisco-voip] Prefix for Missed Calls
No, I tried to work on this same area for several months but never did anything
except for create overlapping dial plans.
I was told the easiest thing to do was to create a phone service that would
take care of this for you. I have never had time to look into this.
Neal Haas
From: cisco-voip [mailto:[email protected]] On Behalf Of Lisa
Notarianni
Sent: Thursday, September 12, 2013 7:31 AM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] Prefix for Missed Calls
(Call Manager 8.6.6)
Has anyone ever successfully utilized translation patterns to prefix 91 so that
when Dial is pressed in Missed or Received Calls, it will automatically
populate the 91 for calls that were missed or received from outside of network
callers?
We had done some testing but it caused an overlap in route patterns which
therefore caused a timeout delay for internal calling.
Here is what we built:
{2-9]xx xxx xxxx would automatically add 91 prefix
[2-9]xxx Is for internal calling
If an internal call was made for example to 4357, Call Manager would wait to
see if the caller was done dialing and after about 15 seconds it would time out
and then the call would go through. The system was comparing the 2 route
patterns above and was not sure which was being used which caused the delay.
I know there are other suggested ways of accomplishing this but if there is a
workaround to Cisco?s preferred way of showing 91 prefix on each incoming call
we would rather that.
Thank you in advance.
Lisa
[cid:[email protected]]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/453039e2/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 10828 bytes
Desc: image001.gif
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/453039e2/attachment-0001.gif>
------------------------------
Message: 17
Date: Thu, 12 Sep 2013 10:43:30 -0400
From: "Mike " <[email protected]>
To: "'Lisa Notarianni'" <[email protected]>,
<[email protected]>
Subject: Re: [cisco-voip] Prefix for Missed Calls
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
This is done by using transformation patterns.
Start with this link and read all 3 parts.
http://blog.internetworkexpert.com/2009/12/07/building-global-dial-plans-in-cucm7-part-i-globalization/
If you need help let me know.
From: cisco-voip [mailto:[email protected]] On Behalf Of Lisa
Notarianni
Sent: Thursday, September 12, 2013 10:31 AM
To: [email protected]
Subject: [cisco-voip] Prefix for Missed Calls
(Call Manager 8.6.6)
Has anyone ever successfully utilized translation patterns to prefix 91 so that
when Dial is pressed in Missed or Received Calls, it will automatically
populate the 91 for calls that were missed or received from outside of network
callers?
We had done some testing but it caused an overlap in route patterns which
therefore caused a timeout delay for internal calling.
Here is what we built:
{2-9]xx xxx xxxx would automatically add 91 prefix
[2-9]xxx Is for internal calling
If an internal call was made for example to 4357, Call Manager would wait to
see if the caller was done dialing and after about 15 seconds it would time out
and then the call would go through. The system was comparing the 2 route
patterns above and was not sure which was being used which caused the delay.
I know there are other suggested ways of accomplishing this but if there is a
workaround to Cisco?s preferred way of showing 91 prefix on each incoming call
we would rather that.
Thank you in advance.
Lisa
LisaNotarianniSignature
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/f8df6911/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 10828 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/f8df6911/attachment-0001.gif>
------------------------------
Message: 18
Date: Thu, 12 Sep 2013 14:45:23 +0000
From: "Brian Meade (brmeade)" <[email protected]>
To: Lisa Notarianni <[email protected]>,
"[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Prefix for Missed Calls
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
The easiest way is going to be to prefix the 91 on the gateway configuration or
prefix +1 which is more ideal. You can then use a calling party
transformations to normalize the calling number on the phones during the
incoming call but the missed calls will show the number with the +1 or 91
depending on which method you choose. If you go with the E164 method, you?ll
need to create some additional translation patterns to translate the E164
number back to something that matches your route patterns.
From: cisco-voip [mailto:[email protected]] On Behalf Of Lisa
Notarianni
Sent: Thursday, September 12, 2013 10:31 AM
To: [email protected]
Subject: [cisco-voip] Prefix for Missed Calls
(Call Manager 8.6.6)
Has anyone ever successfully utilized translation patterns to prefix 91 so that
when Dial is pressed in Missed or Received Calls, it will automatically
populate the 91 for calls that were missed or received from outside of network
callers?
We had done some testing but it caused an overlap in route patterns which
therefore caused a timeout delay for internal calling.
Here is what we built:
{2-9]xx xxx xxxx would automatically add 91 prefix
[2-9]xxx Is for internal calling
If an internal call was made for example to 4357, Call Manager would wait to
see if the caller was done dialing and after about 15 seconds it would time out
and then the call would go through. The system was comparing the 2 route
patterns above and was not sure which was being used which caused the delay.
I know there are other suggested ways of accomplishing this but if there is a
workaround to Cisco?s preferred way of showing 91 prefix on each incoming call
we would rather that.
Thank you in advance.
Lisa
[LisaNotarianniSignature]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/48f373bd/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 10828 bytes
Desc: image001.gif
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20130912/48f373bd/attachment-0001.gif>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 119, Issue 11
*******************************************
