date:20151028

Re: [cisco-voip] 7821 phones issue

2015-10-28 Thread Ryan Huff

Could you provide the "voice service voip" config section of HQ and a branch 
site?

Sent from my iPad

On Oct 28, 2015, at 8:08 AM, Ahmed Abd EL-Rahman 
> wrote:

I know that there is a lack of a response to the SIP invite message which is 
being sent from HQ 7821 phone to the branch 7821 phone during the call setup 
which may point to a network connectivity (or blocking) in the middle, but can 
anyone give me a reasonable answer for why the same messages are flowing 
normally when the 8831 HQ phone initiate the call to the 7821 branch phone ?? 
if something blocked it will be blocked for all.



Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ahmed 
Abd EL-Rahman
Sent: Wednesday, October 28, 2015 3:02 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] 7821 phones issue

Hi Gents,


I have a setup of CME 10.5 on 2911 ISR in the HQ, then I have a DMVPN to the 
branch site.

I have the following phone types:

- 7945 skinny based phone.

- 8831 SIP conference station.

-7821 SIP phones.

- 7861 SIP phone.

the setup is working fine in the HQ (on the same LAN) but when i took some of 
the 7821 phones and placed them in the branch site the following happens:

- They are able to register to the CME in the HQ.

- Branch phones can call all HQ phones and can also call each others’ in the 
branch normally.

- The issue is that HQ 7821 & 7861 phones cannot call 7821 branch phones (no 
ring back is heard then the call disconnects after around 1 minute), despite 
the fact that HQ 7945 and 8831 (which is also SIP based) can call Branch 7821 
phones normally with no issues ???



I have upgraded the router IOS to the latest safe harbor version 15.4(3)M4 and 
upgraded the 7821 firmware to the latest version 10.3.1 with no success.

I have enabled the debug voice ccapi inout and collected the output from 2 
calls, 1 is from HQ 8831 SIP phone to a branch 7821 phone which was successful 
and the other from HQ 7821 phone to a branch 7821 phone which was unsuccessful 
and i compared the two outputs line by line and discovered that in the 
successful call the alerting singal (ring back) is received normally, but in 
the unsuccessful one it's not received and a disconnect signal is received as 
shown below:

- successful call:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678/1F64117E85C0/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Interface=0x3E81FC6C, Progress Indication=NULL(0), Signal Indication=SIGNAL 
RINGBACK(1)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Call Entry(Responsed=TRUE, Alert Sent=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallNotify:
   Data Bitmask=0x7, Call Id=677



- unsuccessful call:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357/C9AD33DD82E1/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)

*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnected:
   Cause Value=102, Interface=0x3E81FC6C, Call Id=357
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnected:
   Call Entry(Responsed=TRUE, Cause Value=102, Retry Count=0)
*Oct 25 08:19:24.863: //356/C9AD33DD82E1/CCAPI/ccCallReleaseResources:
   release reserved xcoding resource.
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/ccCallSetAAA_Accounting:
   Accounting=0, Call Id=357
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/ccCallDisconnect:
   Cause Value=102, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect 
Cause=102)
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/ccCallDisconnect:
   Cause Value=102, Call Entry(Responsed=TRUE, Cause Value=102)
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x3E81FC6C, Tag=0x0, Call Id=357,
   Call Entry(Disconnect Cause=102, Voice Class Cause Code=0, Retry Count=0)
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event

Re: [cisco-voip] 8831 stuck on logo on keypad

2015-10-28 Thread Jeremy Bresley


On 10/28/2015 8:12 AM, Jason Aarons (AM) wrote:


sip8831.9-3-3-5 keypad shows the Cisco logo on the screen nothing else

Did a CUCM firmware upgrade to sip8831.10-3-1SR-1-NA with no luck

I can ping the phone and http to it;

Device > Phone shows Registered with Active Load sip8831.9-3-3-5

Inactive Load Failure Reason Internal Phone Error

Not seeing any ITL Errors, can't get to Menu on screen to do a factory 
reset as it just shows the Cisco logo


   [7:50:29a, 10-28-15] DeviceImageDownloadFailure 
DeviceName=SEPAC44F2147C6A IPAddress=10.68.68.168 Method=3 
FailureReason=3 Active=sip8831.9-3-3-5 Inactive=sip8831.10-3-1-16 
FailedLoadId=sip8831.10-3-1SR1-1-NA Server=10.68.68.10



Hardware version 3 phones?  We just ran into this last week, probably a 
little sticker on the bottom of the keypad that says it requires 10.3.1 
firmware.  Symptoms are EXACTLY what we were seeing.  Phone shows 
registered, but keypad was stuck on one of the logos (remote site, so we 
were going by what the remote hands were telling us was on the screen, 
remote control tool was showing everything was fine).


Very disappointed there isn't a field notice about this like there was 
for the 7900 V13/V14 phones that required 9.4.2 firmware to have the 
display work.  Would have kept us from wasting a couple hours 
troubleshooting the problem.


Jeremy "TheBrez" Bresley
b...@brezworks.com
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] 8831 stuck on logo on keypad

2015-10-28 Thread Jason Aarons (AM)

sip8831.9-3-3-5 keypad shows the Cisco logo on the screen nothing else
Did a CUCM firmware upgrade to sip8831.10-3-1SR-1-NA with no luck

I can ping the phone and http to it;
Device > Phone shows Registered with Active Load sip8831.9-3-3-5
Inactive Load Failure ReasonInternal Phone Error

Not seeing any ITL Errors, can't get to Menu on screen to do a factory reset as 
it just shows the Cisco logo

   [7:50:29a, 10-28-15] DeviceImageDownloadFailure 
DeviceName=SEPAC44F2147C6A IPAddress=10.68.68.168 Method=3 FailureReason=3 
Active=sip8831.9-3-3-5 Inactive=sip8831.10-3-1-16 
FailedLoadId=sip8831.10-3-1SR1-1-NA Server=10.68.68.10



___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCCX Upgrade - minor

2015-10-28 Thread Matthew Loraditch

You do not need it.

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jose 
Colon II
Sent: Wednesday, October 28, 2015 1:47 AM
To: Cisco VOIP 
Subject: [cisco-voip] UCCX Upgrade - minor

Just to verify. Do I need to use the refresh upgrade cop file to upgrade from 
10.5.1.1-24 to 10.5.1.11001-49.

Thanks in advance. I believe I do not need it.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] 7821 phones issue

2015-10-28 Thread Ahmed Abd EL-Rahman

Hi Gents,


I have a setup of CME 10.5 on 2911 ISR in the HQ, then I have a DMVPN to the 
branch site.

I have the following phone types:

- 7945 skinny based phone.

- 8831 SIP conference station.

-7821 SIP phones.

- 7861 SIP phone.

the setup is working fine in the HQ (on the same LAN) but when i took some of 
the 7821 phones and placed them in the branch site the following happens:

- They are able to register to the CME in the HQ.

- Branch phones can call all HQ phones and can also call each others' in the 
branch normally.

- The issue is that HQ 7821 & 7861 phones cannot call 7821 branch phones (no 
ring back is heard then the call disconnects after around 1 minute), despite 
the fact that HQ 7945 and 8831 (which is also SIP based) can call Branch 7821 
phones normally with no issues ???



I have upgraded the router IOS to the latest safe harbor version 15.4(3)M4 and 
upgraded the 7821 firmware to the latest version 10.3.1 with no success.

I have enabled the debug voice ccapi inout and collected the output from 2 
calls, 1 is from HQ 8831 SIP phone to a branch 7821 phone which was successful 
and the other from HQ 7821 phone to a branch 7821 phone which was unsuccessful 
and i compared the two outputs line by line and discovered that in the 
successful call the alerting singal (ring back) is received normally, but in 
the unsuccessful one it's not received and a disconnect signal is received as 
shown below:

- successful call:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678/1F64117E85C0/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Interface=0x3E81FC6C, Progress Indication=NULL(0), Signal Indication=SIGNAL 
RINGBACK(1)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Call Entry(Responsed=TRUE, Alert Sent=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallNotify:
   Data Bitmask=0x7, Call Id=677



- unsuccessful call:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357/C9AD33DD82E1/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)

*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnected:
   Cause Value=102, Interface=0x3E81FC6C, Call Id=357
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnected:
   Call Entry(Responsed=TRUE, Cause Value=102, Retry Count=0)
*Oct 25 08:19:24.863: //356/C9AD33DD82E1/CCAPI/ccCallReleaseResources:
   release reserved xcoding resource.
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/ccCallSetAAA_Accounting:
   Accounting=0, Call Id=357
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/ccCallDisconnect:
   Cause Value=102, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect 
Cause=102)
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/ccCallDisconnect:
   Cause Value=102, Call Entry(Responsed=TRUE, Cause Value=102)
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x3E81FC6C, Tag=0x0, Call Id=357,
   Call Entry(Disconnect Cause=102, Voice Class Cause Code=0, Retry Count=0)
*Oct 25 08:19:24.863: //357/C9AD33DD82E1/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
*Oct 25 08:19:24.863: //-1//CCAPI/cc_free_feature_vsa:

*Oct 25 08:19:24.863: :cc_free_feature_vsa freeing 24DE2870
*Oct 25 08:19:24.863: //-1//CCAPI/cc_free_feature_vsa:

*Oct 25 08:19:24.863:  vsacount in free is 1
*Oct 25 08:19:24.863: //356/C9AD33DD82E1/CCAPI/ccCallDisconnect:
   Cause Value=102, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect 
Cause=0)
*Oct 25 08:19:24.863: //356/C9AD33DD82E1/CCAPI/ccCallDisconnect:
   Cause Value=102, Call Entry(Responsed=TRUE, Cause Value=102)
*Oct 25 08:19:24.871: //356/C9AD33DD82E1/CCAPI/cc_api_call_disconnect_done:
   Disposition=0, Interface=0x3E81FC6C, Tag=0x0, Call Id=356,
   Call Entry(Disconnect Cause=102, Voice Class Cause Code=0, Retry Count=0)
*Oct 25 08:19:24.871: //356/C9AD33DD82E1/CCAPI/cc_api_call_disconnect_done:
   Call Disconnect Event Sent
*Oct 25 08:19:24.871: //-1//CCAPI/cc_free_feature_vsa:

*Oct 25 08:19:24.871: :cc_free_feature_vsa freeing

Re: [cisco-voip] 8831 stuck on logo on keypad

2015-10-28 Thread Brokenshire, Steve

Yes you need to use the Interim firmware release sip8831.9-3-3-TO-10-3-1-v2,
Upgrade the system using the install/upgrade after downloading the cop file 
from the cisco support site

https://software.cisco.com/download/release.html?mdfid=284738433=282074288=10.3(1)SR1=AVAILABLE==latest

you will need to log in using your CCO

then select sip V 10 then 10.3(1)
then cmterm-8831-sip.9-3-3-TO-10-3-1-v2.k3.cop.sgn
then import this using update/upgrade option in OS

then go back to call manager and change the default file to the one for this, 
then issue a reset to the phone type and it will update them
Steve Brokenshire
Civic Offices
Knoll Street
Cleethorpes
DN35 8LN
Tel: 01472323968
Email: steve.brokensh...@nelincs.gov.uk

[facebook]  [twitter] 
   [linked in] 
   [youtube] 
   [instagram] 
 [armed_forces] 


From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jason 
Aarons (AM)
Sent: 28 October 2015 13:12
To: cisco-voip (cisco-voip@puck.nether.net)
Subject: [cisco-voip] 8831 stuck on logo on keypad

sip8831.9-3-3-5 keypad shows the Cisco logo on the screen nothing else
Did a CUCM firmware upgrade to sip8831.10-3-1SR-1-NA with no luck

I can ping the phone and http to it;
Device > Phone shows Registered with Active Load sip8831.9-3-3-5
Inactive Load Failure ReasonInternal Phone Error

Not seeing any ITL Errors, can't get to Menu on screen to do a factory reset as 
it just shows the Cisco logo

   [7:50:29a, 10-28-15] DeviceImageDownloadFailure 
DeviceName=SEPAC44F2147C6A IPAddress=10.68.68.168 Method=3 FailureReason=3 
Active=sip8831.9-3-3-5 Inactive=sip8831.10-3-1-16 
FailedLoadId=sip8831.10-3-1SR1-1-NA Server=10.68.68.10







P Reduce your environmental footprint, please do not print this
email unless you really need to. 


This electronic 
message contains information from North East Lincolnshire Council
which may be privileged or confidential. The information is intended to be for
the use of the individual(s) or entity named above. If you are not the intended
recipient be aware that any disclosure, copying, distribution or use of the
contents of this information is prohibited. If you have received this
electronic message in error, please telephone or email the number(s) or address
above immediately. Activity and use of the North East Lincolnshire email system
is monitored to secure its effective operation and for other lawful business
purposes. Communications using this system will also be monitored and may be
recorded to secure effective operation and for other lawful business purposes.
Scanned by Anti Virus Software


___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] 7821 phones issue

2015-10-28 Thread Ahmed Abd EL-Rahman

Hi Ryan:

Please note that the branch is nothing, just a small 887 router configured for 
DMVPN with the HQ to provide IP connectivity, so no voice configs on the branch 
router at all.

For the HQ router, here is the voice service voip section configs:

voice service voip
ip address trusted list
  ipv4 10.10.3.2
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
redirect ip2ip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
h323
 sip
  bind control source-interface GigabitEthernet0/2.3
  bind media source-interface GigabitEthernet0/2.3
  registrar server expires max 1200 min 300





Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA

From: Ryan Huff [mailto:ryanh...@outlook.com]
Sent: Wednesday, October 28, 2015 3:21 PM
To: Ahmed Abd EL-Rahman 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] 7821 phones issue

Could you provide the "voice service voip" config section of HQ and a branch 
site?

Sent from my iPad

On Oct 28, 2015, at 8:08 AM, Ahmed Abd EL-Rahman 
> wrote:
I know that there is a lack of a response to the SIP invite message which is 
being sent from HQ 7821 phone to the branch 7821 phone during the call setup 
which may point to a network connectivity (or blocking) in the middle, but can 
anyone give me a reasonable answer for why the same messages are flowing 
normally when the 8831 HQ phone initiate the call to the 7821 branch phone ?? 
if something blocked it will be blocked for all.



Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ahmed 
Abd EL-Rahman
Sent: Wednesday, October 28, 2015 3:02 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] 7821 phones issue

Hi Gents,


I have a setup of CME 10.5 on 2911 ISR in the HQ, then I have a DMVPN to the 
branch site.

I have the following phone types:

- 7945 skinny based phone.

- 8831 SIP conference station.

-7821 SIP phones.

- 7861 SIP phone.

the setup is working fine in the HQ (on the same LAN) but when i took some of 
the 7821 phones and placed them in the branch site the following happens:

- They are able to register to the CME in the HQ.

- Branch phones can call all HQ phones and can also call each others' in the 
branch normally.

- The issue is that HQ 7821 & 7861 phones cannot call 7821 branch phones (no 
ring back is heard then the call disconnects after around 1 minute), despite 
the fact that HQ 7945 and 8831 (which is also SIP based) can call Branch 7821 
phones normally with no issues ???



I have upgraded the router IOS to the latest safe harbor version 15.4(3)M4 and 
upgraded the 7821 firmware to the latest version 10.3.1 with no success.

I have enabled the debug voice ccapi inout and collected the output from 2 
calls, 1 is from HQ 8831 SIP phone to a branch 7821 phone which was successful 
and the other from HQ 7821 phone to a branch 7821 phone which was unsuccessful 
and i compared the two outputs line by line and discovered that in the 
successful call the alerting singal (ring back) is received normally, but in 
the unsuccessful one it's not received and a disconnect signal is received as 
shown below:

- successful call:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678/1F64117E85C0/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Interface=0x3E81FC6C, Progress Indication=NULL(0), Signal Indication=SIGNAL 
RINGBACK(1)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Call Entry(Responsed=TRUE, Alert Sent=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallNotify:
   Data Bitmask=0x7, Call Id=677



- unsuccessful call:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357/C9AD33DD82E1/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)

*Oct 25 08:19:24.863:

Re: [cisco-voip] 7821 phones issue

2015-10-28 Thread Brian Meade

I'm guessing there's a device with SIP inspection in the middle that
doesn't like the Authorization header and is dropping the packets.  You
could either go through the full path and fix that issue or somehow strip
out that Authorization header.

What do you have configured under sip-ua?

On Wed, Oct 28, 2015 at 11:49 AM, Ahmed Abd EL-Rahman <
ahmed.rah...@bmbgroup.com> wrote:

> Hi Brian,
>
>
>
> If this is the case, so how this can be fixed ?
>
>
>
> Also if this is what makes the call fail, how these calls are working
> between the 7821 phones on the same LAN (both HQ and Branch)? Also it’s
> working from branch 7821 to HQ 7821, it just not working from HQ 7821 to
> branch 7821.
>
>
>
>
>
>
>
> Best Regards
>
>
>
> Ahmed Abd EL-Rahman
>
> Senior Network Engineer - KSA
>
>
>
>
>
> *From:* bmead...@gmail.com [mailto:bmead...@gmail.com] *On Behalf Of *Brian
> Meade
> *Sent:* Wednesday, October 28, 2015 6:43 PM
> *To:* Ahmed Abd EL-Rahman 
> *Cc:* cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] 7821 phones issue
>
>
>
> In the non-working Invite, CME is sending an Authorization header that
> doesn't exist in the working case:
>
> Authorization: Digest username="204",realm="all",uri="sip:201@10.10.3.2
> ;user=phone",response="13d0e80e52a41bc8642290d5744ca66d",nonce="9D2BD5F30012BAFA",cnonce="570b883d",qop=auth,nc=0003,algorithm=MD5
>
>
>
> This is forwarded from the incoming Invite from the 7821.  I'm guessing
> you have some sort of header-passthrough configured here resulting in the
> problem occurring.
>
>
>
>
>
>
>
>
>
> On Wed, Oct 28, 2015 at 8:07 AM, Ahmed Abd EL-Rahman <
> ahmed.rah...@bmbgroup.com> wrote:
>
> I know that there is a lack of a response to the SIP invite message which
> is being sent from HQ 7821 phone to the branch 7821 phone during the call
> setup which may point to a network connectivity (or blocking) in the
> middle, but can anyone give me a reasonable answer for why the same
> messages are flowing normally when the 8831 HQ phone initiate the call to
> the 7821 branch phone ?? if something blocked it will be blocked for all.
>
>
>
>
>
>
>
> Best Regards
>
>
>
> Ahmed Abd EL-Rahman
>
> Senior Network Engineer - KSA
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Ahmed Abd EL-Rahman
> *Sent:* Wednesday, October 28, 2015 3:02 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] 7821 phones issue
>
>
>
> Hi Gents,
>
>
>
> I have a setup of CME 10.5 on 2911 ISR in the HQ, then I have a DMVPN to
> the branch site.
>
> I have the following phone types:
>
> - 7945 skinny based phone.
>
> - 8831 SIP conference station.
>
> -7821 SIP phones.
>
> - 7861 SIP phone.
>
> the setup is working fine in the HQ (on the same LAN) but when i took some
> of the 7821 phones and placed them in the branch site the following happens:
>
> - They are able to register to the CME in the HQ.
>
> - Branch phones can call all HQ phones and can also call each others’ in
> the branch normally.
>
> - The issue is that *HQ* 7821 & 7861 phones *cannot* call 7821 *branch* phones
> (no ring back is heard then the call disconnects after around 1 minute),
> despite the fact that *HQ* 7945 and 8831 (which is also SIP based) can
> call *Branch* 7821 phones normally with no issues ???
>
>
>
> I have upgraded the router IOS to the latest safe harbor version 15.4(3)M4
> and upgraded the 7821 firmware to the latest version 10.3.1 with no success.
>
> I have enabled the debug voice ccapi inout and collected the output from 2
> calls, 1 is from HQ 8831 SIP phone to a branch 7821 phone which was
> successful and the other from HQ 7821 phone to a branch 7821 phone which
> was unsuccessful and i compared the two outputs line by line and discovered
> that in the successful call the alerting singal (ring back) is received
> normally, but in the unsuccessful one it's not received and a disconnect
> signal is received as shown below:
>
> *- successful call:*
>
> *Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
> *Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:
>
> *Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
> *Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:
>
> *Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
> *Oct 25 10:43:55.258: //678/1F64117E85C0/CCAPI/cc_api_call_proceeding:
>Interface=0x3E81FC6C, Progress Indication=NULL(0)
> **Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:*
> *Interface=0x3E81FC6C, Progress Indication=NULL(0), Signal
> Indication=SIGNAL RINGBACK(1)*
> *Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
>Call Entry(Retry Count=0, Responsed=TRUE)
> *Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
>Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
> *Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
>Call Entry(Responsed=TRUE, Alert Sent=TRUE)
> *Oct 25 10:43:55.470:

Re: [cisco-voip] 7821 phones issue

2015-10-28 Thread Ahmed Abd EL-Rahman

Hi Brian,

If this is the case, so how this can be fixed ?

Also if this is what makes the call fail, how these calls are working between 
the 7821 phones on the same LAN (both HQ and Branch)? Also it’s working from 
branch 7821 to HQ 7821, it just not working from HQ 7821 to branch 7821.



Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA


From: bmead...@gmail.com [mailto:bmead...@gmail.com] On Behalf Of Brian Meade
Sent: Wednesday, October 28, 2015 6:43 PM
To: Ahmed Abd EL-Rahman 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] 7821 phones issue

In the non-working Invite, CME is sending an Authorization header that doesn't 
exist in the working case:
Authorization: Digest 
username="204",realm="all",uri="sip:201@10.10.3.2;user=phone",response="13d0e80e52a41bc8642290d5744ca66d",nonce="9D2BD5F30012BAFA",cnonce="570b883d",qop=auth,nc=0003,algorithm=MD5

This is forwarded from the incoming Invite from the 7821.  I'm guessing you 
have some sort of header-passthrough configured here resulting in the problem 
occurring.




On Wed, Oct 28, 2015 at 8:07 AM, Ahmed Abd EL-Rahman 
> wrote:
I know that there is a lack of a response to the SIP invite message which is 
being sent from HQ 7821 phone to the branch 7821 phone during the call setup 
which may point to a network connectivity (or blocking) in the middle, but can 
anyone give me a reasonable answer for why the same messages are flowing 
normally when the 8831 HQ phone initiate the call to the 7821 branch phone ?? 
if something blocked it will be blocked for all.



Best Regards

Ahmed Abd EL-Rahman
Senior Network Engineer - KSA

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of Ahmed Abd EL-Rahman
Sent: Wednesday, October 28, 2015 3:02 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] 7821 phones issue

Hi Gents,


I have a setup of CME 10.5 on 2911 ISR in the HQ, then I have a DMVPN to the 
branch site.

I have the following phone types:

- 7945 skinny based phone.

- 8831 SIP conference station.

-7821 SIP phones.

- 7861 SIP phone.

the setup is working fine in the HQ (on the same LAN) but when i took some of 
the 7821 phones and placed them in the branch site the following happens:

- They are able to register to the CME in the HQ.

- Branch phones can call all HQ phones and can also call each others’ in the 
branch normally.

- The issue is that HQ 7821 & 7861 phones cannot call 7821 branch phones (no 
ring back is heard then the call disconnects after around 1 minute), despite 
the fact that HQ 7945 and 8831 (which is also SIP based) can call Branch 7821 
phones normally with no issues ???



I have upgraded the router IOS to the latest safe harbor version 15.4(3)M4 and 
upgraded the 7821 firmware to the latest version 10.3.1 with no success.

I have enabled the debug voice ccapi inout and collected the output from 2 
calls, 1 is from HQ 8831 SIP phone to a branch 7821 phone which was successful 
and the other from HQ 7821 phone to a branch 7821 phone which was unsuccessful 
and i compared the two outputs line by line and discovered that in the 
successful call the alerting singal (ring back) is received normally, but in 
the unsuccessful one it's not received and a disconnect signal is received as 
shown below:

- successful call:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678//CCAPI/cc_api_get_xcode_stream:

*Oct 25 10:43:55.258: cc_api_get_xcode_stream : 4982
*Oct 25 10:43:55.258: //678/1F64117E85C0/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Interface=0x3E81FC6C, Progress Indication=NULL(0), Signal Indication=SIGNAL 
RINGBACK(1)
*Oct 25 10:43:55.466: //678/1F64117E85C0/CCAPI/cc_api_call_alert:
   Call Entry(Retry Count=0, Responsed=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Progress Indication=NULL(0), Signal Indication=SIGNAL RINGBACK(1)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallAlert:
   Call Entry(Responsed=TRUE, Alert Sent=TRUE)
*Oct 25 10:43:55.470: //677/1F64117E85C0/CCAPI/ccCallNotify:
   Data Bitmask=0x7, Call Id=677



- unsuccessful call:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357//CCAPI/cc_api_get_xcode_stream:

*Oct 25 08:18:21.359: cc_api_get_xcode_stream : 4982
*Oct 25 08:18:21.359: //357/C9AD33DD82E1/CCAPI/cc_api_call_proceeding:
   Interface=0x3E81FC6C, Progress Indication=NULL(0)

*Oct 25

[cisco-voip] be6kS

2015-10-28 Thread Erick Wellnitz

All,

I seem to remember hearing something about a plugin or a tool to configure
the BE6KS but I can't seem to find such a thing.

I thought it was a Firefox plugin.  Was I imagining things?

Thanks!
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

2015-10-28 Thread Ryan Huff

UCOS does not support Windows time services. Cisco IOS based devices or Linux 
servers are recommended.

Sent from my iPad

On Oct 28, 2015, at 1:33 PM, Thomas LeMay 
> wrote:

Hi,

Questions: What is the best business practice for the type of NTP server to use 
as the source: windows or some other operating system?

Thank you,

Tom

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Aaron 
Banks
Sent: Wednesday, October 28, 2015 12:39 AM
To: Ryan Huff; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Thank you for all of that.  You know what it was - NTP.  I shut down the HA.  
NTP was doing weird things on the primary node and I asked the customer if the 
NTP server address he gave me was a windows server.  Bingo.  I changed the NTP 
source, rebooted the primary, called voicemail and then powered on the HA.

Lesson learned.

From: ryanh...@outlook.com
To: amichaelba...@hotmail.com; 
cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
Date: Tue, 27 Oct 2015 17:25:47 +
1.) Shut down the HA node.

2.) Reboot the primary node

3.) Once the primary node is up, place a call into voicemail

4.) Power the HA node back on

5.) Once HA is up, verify HA status.



Sent from my T-Mobile 4G LTE Device


 Original message 
From: Aaron Banks
Date:10/27/2015 12:35 PM (GMT-05:00)
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery


Has anyone seen/resolved a split brain recovery in Unity Connection 10.5.2?  
The primary and secondary keep swapping back and forth every few minutes.  I 
can ping and trace to each server.  I restarted the primary but that did not 
resolve the issue.  In the RTMT system logs, the secondary sends an NTP query 
to the primary the response is the primary is inaccessible or down.  I'm 
stumped.
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] 8831 stuck on logo on keypad

2015-10-28 Thread Ryan Ratliff (rratliff)

Steve is correct, you MUST go through the ‘9-3-3-TO-10-3-1’ load between 
9-3-3-5 and 10-3-1.  If you have LSCs installed on 9-3-3-5 make sure you use 
the v2 interim load.

As for an FN on this issue hold tight...

-Ryan

On Oct 28, 2015, at 10:11 AM, Brokenshire, Steve 
> 
wrote:

Yes you need to use the Interim firmware release sip8831.9-3-3-TO-10-3-1-v2,
Upgrade the system using the install/upgrade after downloading the cop file 
from the cisco support site

https://software.cisco.com/download/release.html?mdfid=284738433=282074288=10.3(1)SR1=AVAILABLE==latest

you will need to log in using your CCO

then select sip V 10 then 10.3(1)
then cmterm-8831-sip.9-3-3-TO-10-3-1-v2.k3.cop.sgn
then import this using update/upgrade option in OS

then go back to call manager and change the default file to the one for this, 
then issue a reset to the phone type and it will update them
Steve Brokenshire
Civic Offices
Knoll Street
Cleethorpes
DN35 8LN
Tel: 01472323968
Email: steve.brokensh...@nelincs.gov.uk

  
  

    


From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jason 
Aarons (AM)
Sent: 28 October 2015 13:12
To: cisco-voip (cisco-voip@puck.nether.net)
Subject: [cisco-voip] 8831 stuck on logo on keypad

sip8831.9-3-3-5 keypad shows the Cisco logo on the screen nothing else
Did a CUCM firmware upgrade to sip8831.10-3-1SR-1-NA with no luck

I can ping the phone and http to it;
Device > Phone shows Registered with Active Load sip8831.9-3-3-5
Inactive Load Failure ReasonInternal Phone Error

Not seeing any ITL Errors, can't get to Menu on screen to do a factory reset as 
it just shows the Cisco logo

   [7:50:29a, 10-28-15] DeviceImageDownloadFailure 
DeviceName=SEPAC44F2147C6A IPAddress=10.68.68.168 Method=3 FailureReason=3 
Active=sip8831.9-3-3-5 Inactive=sip8831.10-3-1-16 
FailedLoadId=sip8831.10-3-1SR1-1-NA Server=10.68.68.10











P Reduce your environmental footprint, please do not print this
email unless you really need to.

This electronic message contains information from North East Lincolnshire 
Council
which may be privileged or confidential. The information is intended to be for
the use of the individual(s) or entity named above. If you are not the intended
recipient be aware that any disclosure, copying, distribution or use of the
contents of this information is prohibited. If you have received this
electronic message in error, please telephone or email the number(s) or address
above immediately. Activity and use of the North East Lincolnshire email system
is monitored to secure its effective operation and for other lawful business
purposes. Communications using this system will also be monitored and may be
recorded to secure effective operation and for other lawful business purposes.
Scanned by Anti Virus Software




___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

2015-10-28 Thread Matthew Loraditch

So here’s a question then if Windows isn’t supported, how do you make sure ADFS 
works? I had plenty of timing problems with ADFS being out of sync, until I 
started using my primary DC as the UCM/UCXN NTP as I saw that recommended 
somewhere to fix..

What are folks doing here?

Matthew G. Loraditch – CCNP-Voice, CCNA-R, CCDA
Network Engineer
Direct Voice: 443.541.1518

Facebook | 
Twitter | 
LinkedIn 
| G+

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Erick 
Wellnitz
Sent: Wednesday, October 28, 2015 1:41 PM
To: Charles Goldsmith 
Cc: voip puck ; Aaron Banks 

Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

I like both IOS and Linux ntpd

I synch those with time.nist.gov

Remember that you need a stratum 6 or better to sync UC apps like connection or 
CUCM.

On Wed, Oct 28, 2015 at 11:35 AM, Charles Goldsmith 
> wrote:
I personally prefer an IOS based device, a core switch or router.

On Wed, Oct 28, 2015 at 12:33 PM, Thomas LeMay 
> wrote:
Hi,

Questions: What is the best business practice for the type of NTP server to use 
as the source: windows or some other operating system?

Thank you,

Tom

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of Aaron Banks
Sent: Wednesday, October 28, 2015 12:39 AM
To: Ryan Huff; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Thank you for all of that.  You know what it was - NTP.  I shut down the HA.  
NTP was doing weird things on the primary node and I asked the customer if the 
NTP server address he gave me was a windows server.  Bingo.  I changed the NTP 
source, rebooted the primary, called voicemail and then powered on the HA.

Lesson learned.

From: ryanh...@outlook.com
To: amichaelba...@hotmail.com; 
cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
Date: Tue, 27 Oct 2015 17:25:47 +
1.) Shut down the HA node.

2.) Reboot the primary node

3.) Once the primary node is up, place a call into voicemail

4.) Power the HA node back on

5.) Once HA is up, verify HA status.

Sent from my T-Mobile 4G LTE Device

 Original message 
From: Aaron Banks
Date:10/27/2015 12:35 PM (GMT-05:00)
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Has anyone seen/resolved a split brain recovery in Unity Connection 10.5.2?  
The primary and secondary keep swapping back and forth every few minutes.  I 
can ping and trace to each server.  I restarted the primary but that did not 
resolve the issue.  In the RTMT system logs, the secondary sends an NTP query 
to the primary the response is the primary is inaccessible or down.  I'm 
stumped.

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

2015-10-28 Thread Jason Aarons (AM)

Older versions of Windows Server ie 2003/2008 did SNTP natively not NTP.  You 
can’t point to a NTP client to SNTP server. SNTP is not precise enough, but 
good enough for Kerberos/Windows.

Windows Server 2012 can serve up NTP
http://www.sysadminlab.net/windows/configuring-ntp-on-windows-server-2012

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Matthew Loraditch
Sent: Wednesday, October 28, 2015 2:07 PM
To: Erick Wellnitz ; Charles Goldsmith 

Cc: voip puck ; Aaron Banks 

Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

So here’s a question then if Windows isn’t supported, how do you make sure ADFS 
works? I had plenty of timing problems with ADFS being out of sync, until I 
started using my primary DC as the UCM/UCXN NTP as I saw that recommended 
somewhere to fix..

What are folks doing here?

Matthew G. Loraditch – CCNP-Voice, CCNA-R, CCDA
Network Engineer
Direct Voice: 443.541.1518
Facebook | 
Twitter | 
LinkedIn 
| G+

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Erick 
Wellnitz
Sent: Wednesday, October 28, 2015 1:41 PM
To: Charles Goldsmith >
Cc: voip puck >; 
Aaron Banks >
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

I like both IOS and Linux ntpd

I synch those with time.nist.gov

Remember that you need a stratum 6 or better to sync UC apps like connection or 
CUCM.

On Wed, Oct 28, 2015 at 11:35 AM, Charles Goldsmith 
> wrote:
I personally prefer an IOS based device, a core switch or router.

On Wed, Oct 28, 2015 at 12:33 PM, Thomas LeMay 
> wrote:
Hi,

Questions: What is the best business practice for the type of NTP server to use 
as the source: windows or some other operating system?

Thank you,

Tom

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of Aaron Banks
Sent: Wednesday, October 28, 2015 12:39 AM
To: Ryan Huff; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Thank you for all of that.  You know what it was - NTP.  I shut down the HA.  
NTP was doing weird things on the primary node and I asked the customer if the 
NTP server address he gave me was a windows server.  Bingo.  I changed the NTP 
source, rebooted the primary, called voicemail and then powered on the HA.

Lesson learned.

From: ryanh...@outlook.com
To: amichaelba...@hotmail.com; 
cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
Date: Tue, 27 Oct 2015 17:25:47 +
1.) Shut down the HA node.

2.) Reboot the primary node

3.) Once the primary node is up, place a call into voicemail

4.) Power the HA node back on

5.) Once HA is up, verify HA status.

Sent from my T-Mobile 4G LTE Device

 Original message 
From: Aaron Banks
Date:10/27/2015 12:35 PM (GMT-05:00)
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Has anyone seen/resolved a split brain recovery in Unity Connection 10.5.2?  
The primary and secondary keep swapping back and forth every few minutes.  I 
can ping and trace to each server.  I restarted the primary but that did not 
resolve the issue.  In the RTMT system logs, the secondary sends an NTP query 
to the primary the response is the primary is inaccessible or down.  I'm 
stumped.

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

itevomcid
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

2015-10-28 Thread Erick Wellnitz

I like both IOS and Linux ntpd

I synch those with time.nist.gov

Remember that you need a stratum 6 or better to sync UC apps like
connection or CUCM.

On Wed, Oct 28, 2015 at 11:35 AM, Charles Goldsmith 
wrote:

> I personally prefer an IOS based device, a core switch or router.
>
> On Wed, Oct 28, 2015 at 12:33 PM, Thomas LeMay 
> wrote:
>
>> Hi,
>>
>>
>>
>> Questions: What is the best business practice for the type of NTP server
>> to use as the source: windows or some other operating system?
>>
>>
>>
>> Thank you,
>>
>>
>>
>> Tom
>>
>>
>>
>> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On
>> Behalf Of *Aaron Banks
>> *Sent:* Wednesday, October 28, 2015 12:39 AM
>> *To:* Ryan Huff; cisco-voip@puck.nether.net
>> *Subject:* Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>>
>>
>>
>> Thank you for all of that.  You know what it was - NTP.  I shut down the
>> HA.  NTP was doing weird things on the primary node and I asked the
>> customer if the NTP server address he gave me was a windows server.
>> Bingo.  I changed the NTP source, rebooted the primary, called voicemail
>> and then powered on the HA.
>>
>> Lesson learned.
>> --
>>
>> From: ryanh...@outlook.com
>> To: amichaelba...@hotmail.com; cisco-voip@puck.nether.net
>> Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>> Date: Tue, 27 Oct 2015 17:25:47 +
>>
>> 1.) Shut down the HA node.
>>
>>
>>
>> 2.) Reboot the primary node
>>
>>
>>
>> 3.) Once the primary node is up, place a call into voicemail
>>
>>
>>
>> 4.) Power the HA node back on
>>
>>
>>
>> 5.) Once HA is up, verify HA status.
>>
>>
>>
>>
>>
>>
>>
>> Sent from my T-Mobile 4G LTE Device
>>
>>
>>
>>  Original message 
>> From: Aaron Banks
>> Date:10/27/2015 12:35 PM (GMT-05:00)
>> To: cisco-voip@puck.nether.net
>> Subject: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>>
>>
>>
>> Has anyone seen/resolved a split brain recovery in Unity Connection
>> 10.5.2?  The primary and secondary keep swapping back and forth every few
>> minutes.  I can ping and trace to each server.  I restarted the primary but
>> that did not resolve the issue.  In the RTMT system logs, the secondary
>> sends an NTP query to the primary the response is the primary is
>> inaccessible or down.  I'm stumped.
>>
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

2015-10-28 Thread Charles Goldsmith

I personally prefer an IOS based device, a core switch or router.

On Wed, Oct 28, 2015 at 12:33 PM, Thomas LeMay 
wrote:

> Hi,
>
>
>
> Questions: What is the best business practice for the type of NTP server
> to use as the source: windows or some other operating system?
>
>
>
> Thank you,
>
>
>
> Tom
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Aaron Banks
> *Sent:* Wednesday, October 28, 2015 12:39 AM
> *To:* Ryan Huff; cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>
>
>
> Thank you for all of that.  You know what it was - NTP.  I shut down the
> HA.  NTP was doing weird things on the primary node and I asked the
> customer if the NTP server address he gave me was a windows server.
> Bingo.  I changed the NTP source, rebooted the primary, called voicemail
> and then powered on the HA.
>
> Lesson learned.
> --
>
> From: ryanh...@outlook.com
> To: amichaelba...@hotmail.com; cisco-voip@puck.nether.net
> Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
> Date: Tue, 27 Oct 2015 17:25:47 +
>
> 1.) Shut down the HA node.
>
>
>
> 2.) Reboot the primary node
>
>
>
> 3.) Once the primary node is up, place a call into voicemail
>
>
>
> 4.) Power the HA node back on
>
>
>
> 5.) Once HA is up, verify HA status.
>
>
>
>
>
>
>
> Sent from my T-Mobile 4G LTE Device
>
>
>
>  Original message 
> From: Aaron Banks
> Date:10/27/2015 12:35 PM (GMT-05:00)
> To: cisco-voip@puck.nether.net
> Subject: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>
>
>
> Has anyone seen/resolved a split brain recovery in Unity Connection
> 10.5.2?  The primary and secondary keep swapping back and forth every few
> minutes.  I can ping and trace to each server.  I restarted the primary but
> that did not resolve the issue.  In the RTMT system logs, the secondary
> sends an NTP query to the primary the response is the primary is
> inaccessible or down.  I'm stumped.
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] UCCX Upgrade - minor

2015-10-28 Thread Jose Colon II

Thanks you
On Oct 28, 2015 6:33 AM, "Matthew Loraditch" <
mloradi...@heliontechnologies.com> wrote:

> You do not need it.
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Jose Colon II
> *Sent:* Wednesday, October 28, 2015 1:47 AM
> *To:* Cisco VOIP 
> *Subject:* [cisco-voip] UCCX Upgrade - minor
>
>
>
> Just to verify. Do I need to use the refresh upgrade cop file to upgrade
> from 10.5.1.1-24 to 10.5.1.11001-49.
>
>
>
> Thanks in advance. I believe I do not need it.
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] CM 8.6 to 10.5 common Partition

2015-10-28 Thread Scott Voll

OK so we had CM 8.6 running on MCS servers with 146 gb mirrored drives.

Now I'm on VM CM 10.5 and the OVA came with a 80 gig drive.

Now I'm bouncing at my 90% used common partition.

is this normal?  is this a bug?  is it that i'm using a 80 gig drive.

Before I open a TAC case... What is the underlining issue?

TIA

Scott
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

2015-10-28 Thread Erick Wellnitz

The error I get on CUC publishers is that it must be stratum 6 or better.
10.5.2 SU1 and better versions building in a dead network for hardware
migration.

I would agree that the closer to 1 you can get, the better.

Worst case, since DNS is no longer taboo, is to sync directly with a
stratum 1 time server in the wild.

On Wed, Oct 28, 2015 at 12:09 PM, Daniel Pagan  wrote:

> Just a heads up, Cisco recommendation for CUCM is that NTP stratum should
> be 3 or better to avoid DB replication issues.
>
>
>
>
> http://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/118718-technote-cucm-00.html
>
>
>
> “Stratum level should be less than 4 on publisher for optimal performance”
>
>
>
> CUC documentation isn’t very clear on this specifically - CUC 10x docs
> mention stratum 9 or better but that sounds wrong IMO.
>
>
>
> I would follow the same recommendation documented for CUCM (stratum 3 or
> better) on CUC.
>
>
>
> HTH
>
>
>
> - Dan
>
>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Erick Wellnitz
> *Sent:* Wednesday, October 28, 2015 1:41 PM
> *To:* Charles Goldsmith 
> *Cc:* voip puck ; Aaron Banks <
> amichaelba...@hotmail.com>
> *Subject:* Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>
>
>
> I like both IOS and Linux ntpd
>
>
>
> I synch those with time.nist.gov
>
>
>
> Remember that you need a stratum 6 or better to sync UC apps like
> connection or CUCM.
>
>
>
> On Wed, Oct 28, 2015 at 11:35 AM, Charles Goldsmith 
> wrote:
>
> I personally prefer an IOS based device, a core switch or router.
>
>
>
> On Wed, Oct 28, 2015 at 12:33 PM, Thomas LeMay 
> wrote:
>
> Hi,
>
>
>
> Questions: What is the best business practice for the type of NTP server
> to use as the source: windows or some other operating system?
>
>
>
> Thank you,
>
>
>
> Tom
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Aaron Banks
> *Sent:* Wednesday, October 28, 2015 12:39 AM
> *To:* Ryan Huff; cisco-voip@puck.nether.net
> *Subject:* Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>
>
>
> Thank you for all of that.  You know what it was - NTP.  I shut down the
> HA.  NTP was doing weird things on the primary node and I asked the
> customer if the NTP server address he gave me was a windows server.
> Bingo.  I changed the NTP source, rebooted the primary, called voicemail
> and then powered on the HA.
>
> Lesson learned.
> --
>
> From: ryanh...@outlook.com
> To: amichaelba...@hotmail.com; cisco-voip@puck.nether.net
> Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
> Date: Tue, 27 Oct 2015 17:25:47 +
>
> 1.) Shut down the HA node.
>
>
>
> 2.) Reboot the primary node
>
>
>
> 3.) Once the primary node is up, place a call into voicemail
>
>
>
> 4.) Power the HA node back on
>
>
>
> 5.) Once HA is up, verify HA status.
>
>
>
>
>
>
>
> Sent from my T-Mobile 4G LTE Device
>
>
>
>  Original message 
> From: Aaron Banks
> Date:10/27/2015 12:35 PM (GMT-05:00)
> To: cisco-voip@puck.nether.net
> Subject: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
>
>
>
> Has anyone seen/resolved a split brain recovery in Unity Connection
> 10.5.2?  The primary and secondary keep swapping back and forth every few
> minutes.  I can ping and trace to each server.  I restarted the primary but
> that did not resolve the issue.  In the RTMT system logs, the secondary
> sends an NTP query to the primary the response is the primary is
> inaccessible or down.  I'm stumped.
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

2015-10-28 Thread Norton, Mike

Even though it is true that newer Windows versions have moved to NTP from SNTP, 
Microsoft still does not intend for you to use it as an “NTP server” per se. It 
is intended for AD’s own internal time-syncing needs and that’s it.

--
Support boundary to configure the Windows Time service for high-accuracy 
environments: https://support.microsoft.com/en-us/kb/939322

“We do not guarantee and we do not support the accuracy of the W32Time service 
between nodes on a network. The W32Time service is not a full-featured NTP 
solution that meets time-sensitive application needs.”
--

If you’re having problems with ADFS due to time, I’d have to wonder if maybe 
your AD domain is synced from an unreliable source, or perhaps not synced from 
anywhere. (VMs with virtual clock set to follow physical host clock can wreak 
havoc as well.) As long as your AD domain is synced from the same real NTP 
source as your Cisco stuff, times should be more than close enough. You do sync 
your AD domain to a real NTP source, right?

-mn

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jason 
Aarons (AM)
Sent: October-28-15 12:13 PM
To: Matthew Loraditch; Erick Wellnitz; Charles Goldsmith
Cc: voip puck; Aaron Banks
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Older versions of Windows Server ie 2003/2008 did SNTP natively not NTP.  You 
can’t point to a NTP client to SNTP server. SNTP is not precise enough, but 
good enough for Kerberos/Windows.

Windows Server 2012 can serve up NTP
http://www.sysadminlab.net/windows/configuring-ntp-on-windows-server-2012

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Matthew Loraditch
Sent: Wednesday, October 28, 2015 2:07 PM
To: Erick Wellnitz >; 
Charles Goldsmith >
Cc: voip puck >; 
Aaron Banks >
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

So here’s a question then if Windows isn’t supported, how do you make sure ADFS 
works? I had plenty of timing problems with ADFS being out of sync, until I 
started using my primary DC as the UCM/UCXN NTP as I saw that recommended 
somewhere to fix..

What are folks doing here?

Matthew G. Loraditch – CCNP-Voice, CCNA-R, CCDA
Network Engineer
Direct Voice: 443.541.1518
Facebook | 
Twitter | 
LinkedIn 
| G+

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Erick 
Wellnitz
Sent: Wednesday, October 28, 2015 1:41 PM
To: Charles Goldsmith >
Cc: voip puck >; 
Aaron Banks >
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

I like both IOS and Linux ntpd

I synch those with time.nist.gov

Remember that you need a stratum 6 or better to sync UC apps like connection or 
CUCM.

On Wed, Oct 28, 2015 at 11:35 AM, Charles Goldsmith 
> wrote:
I personally prefer an IOS based device, a core switch or router.

On Wed, Oct 28, 2015 at 12:33 PM, Thomas LeMay 
> wrote:
Hi,

Questions: What is the best business practice for the type of NTP server to use 
as the source: windows or some other operating system?

Thank you,

Tom

From: cisco-voip 
[mailto:cisco-voip-boun...@puck.nether.net]
 On Behalf Of Aaron Banks
Sent: Wednesday, October 28, 2015 12:39 AM
To: Ryan Huff; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Thank you for all of that.  You know what it was - NTP.  I shut down the HA.  
NTP was doing weird things on the primary node and I asked the customer if the 
NTP server address he gave me was a windows server.  Bingo.  I changed the NTP 
source, rebooted the primary, called voicemail and then powered on the HA.

Lesson learned.

From: ryanh...@outlook.com
To: amichaelba...@hotmail.com; 
cisco-voip@puck.nether.net
Subject: RE: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery
Date: Tue, 27 Oct 2015 17:25:47 +
1.) Shut down the HA node.

2.) Reboot the primary node

3.) Once the primary node is up, place a call into voicemail

4.) Power the HA node back on

5.) Once HA is up, verify HA status.

Sent from my T-Mobile 4G LTE Device

Re: [cisco-voip] 7821 phones issue

2015-10-28 Thread Brian Meade

You could try a sip-profile under voice service voip to strip it out.

voice class sip-profiles 100
 request Invite sip-header Authorization remove

voice service voip
 sip
  sip-profiles 100

I've never tried this for CME messaging though.  It's normally a CUBE
feature.  It may still work though.

You should be able to remove the username/password under the SIP ephone
configuration for the calling phone if it's on the same subnet as CME which
may also help but doesn't help if you have those 78XX phones registering
over the WAN.


On Wed, Oct 28, 2015 at 3:41 PM, Ahmed Abd EL-Rahman <
ahmed.rah...@bmbgroup.com> wrote:

> Nothing configured under the sip-ua.
>
> How can I strip out the authorization header please?
>
>
>
>
>
> Best Regards
>
> Ahmed Abd EL-Rahman
> Senior Network Engineer - BMB KSA
>
> On Oct 28, 2015, at 7:29 PM, Brian Meade > wrote:
>
> I'm guessing there's a device with SIP inspection in the middle that
> doesn't like the Authorization header and is dropping the packets.  You
> could either go through the full path and fix that issue or somehow strip
> out that Authorization header.
>
> What do you have configured under sip-ua?
>
> On Wed, Oct 28, 2015 at 11:49 AM, Ahmed Abd EL-Rahman <
> ahmed.rah...@bmbgroup.com> wrote:
> Hi Brian,
>
> If this is the case, so how this can be fixed ?
>
> Also if this is what makes the call fail, how these calls are working
> between the 7821 phones on the same LAN (both HQ and Branch)? Also it’s
> working from branch 7821 to HQ 7821, it just not working from HQ 7821 to
> branch 7821.
>
>
>
> Best Regards
>
> Ahmed Abd EL-Rahman
> Senior Network Engineer - KSA
>
>
> From: bmead...@gmail.com [mailto:
> bmead...@gmail.com] On Behalf Of Brian Meade
> Sent: Wednesday, October 28, 2015 6:43 PM
> To: Ahmed Abd EL-Rahman >
> Cc: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] 7821 phones issue
>
> In the non-working Invite, CME is sending an Authorization header that
> doesn't exist in the working case:
> Authorization: Digest username="204",realm="all",uri="sip:201@10.10.3.2
>  >;user=phone",response="13d0e80e52a41bc8642290d5744ca66d",nonce="9D2BD5F30012BAFA",cnonce="570b883d",qop=auth,nc=0003,algorithm=MD5
>
> This is forwarded from the incoming Invite from the 7821.  I'm guessing
> you have some sort of header-passthrough configured here resulting in the
> problem occurring.
>
>
>
>
> On Wed, Oct 28, 2015 at 8:07 AM, Ahmed Abd EL-Rahman <
> ahmed.rah...@bmbgroup.com> wrote:
> I know that there is a lack of a response to the SIP invite message which
> is being sent from HQ 7821 phone to the branch 7821 phone during the call
> setup which may point to a network connectivity (or blocking) in the
> middle, but can anyone give me a reasonable answer for why the same
> messages are flowing normally when the 8831 HQ phone initiate the call to
> the 7821 branch phone ?? if something blocked it will be blocked for all.
>
>
>
> Best Regards
>
> Ahmed Abd EL-Rahman
> Senior Network Engineer - KSA
>
> From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net cisco-voip-boun...@puck.nether.net>] On Behalf Of Ahmed Abd EL-Rahman
> Sent: Wednesday, October 28, 2015 3:02 PM
> To: cisco-voip@puck.nether.net
> Subject: [cisco-voip] 7821 phones issue
>
> Hi Gents,
>
>
> I have a setup of CME 10.5 on 2911 ISR in the HQ, then I have a DMVPN to
> the branch site.
>
> I have the following phone types:
>
> - 7945 skinny based phone.
>
> - 8831 SIP conference station.
>
> -7821 SIP phones.
>
> - 7861 SIP phone.
>
> the setup is working fine in the HQ (on the same LAN) but when i took some
> of the 7821 phones and placed them in the branch site the following happens:
>
> - They are able to register to the CME in the HQ.
>
> - Branch phones can call all HQ phones and can also call each others’ in
> the branch normally.
>
> - The issue is that HQ 7821 & 7861 phones cannot call 7821 branch phones
> (no ring back is heard then the call disconnects after around 1 minute),
> despite the fact that HQ 7945 and 8831 (which is also SIP based) can call
> Branch 7821 phones normally with no issues ???
>
>
>
> I have upgraded the router IOS to the latest safe harbor version 15.4(3)M4
> and upgraded the 7821 firmware to the latest version 10.3.1 with no success.
>
> I have enabled the debug voice ccapi inout and collected the output from 2
> calls, 1 is from HQ 8831 SIP phone to a branch 7821 phone which was
> successful and the other from HQ 7821 phone to a branch 7821 phone which
> was unsuccessful and i compared the two outputs line by line and discovered
> that in the successful call the alerting singal (ring back) is received
> normally, but in the unsuccessful one it's not

Re: [cisco-voip] CM 8.6 to 10.5 common Partition

2015-10-28 Thread Anthony Holloway

The common partition will float between 90% and 95% capacity by design, and
by default.  You can adjust this if you want to via RTMT Low and High Water
Marks for the Common Partition.

The way the Low and High marks work is like this:  If the system is at 0%
utilzed, then starts to increase to exceed the Low water mark, nothing
happens.  Then when it continues to rise, and exceed the High water mark,
the system will start to purge old log files until the utilization drops
below the Low water mark.  Then the disk will start to fill again, and
repeat this process over and over.  Hence the floating between the 90% and
95%.

When you do an upgrade, it's recommended to move these values from 90/95 to
30/40 to free up space for the upgrade.

Source:

Default High and Low settings
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/service/10_0_1/rtmt/CUCM_BK_CA30A928_00_cisco-unified-rtmt-administration-100/CUCM_BK_CA30A928_00_cisco-unified-rtmt-administration-100_appendix_01001.html#CUCM_RF_L8915889_00

High and Low water mark changes for upgrades, see step 4 (note the
descrepency between the normal values here and the above values)
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/10_0_1/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100/CUCM_BK_U4214F9D_00_upgrade-guide-cucm-100_chapter_011.html#CUCM_TK_PEC312F1_00

On Wed, Oct 28, 2015 at 2:58 PM, Scott Voll  wrote:

> OK so we had CM 8.6 running on MCS servers with 146 gb mirrored drives.
>
> Now I'm on VM CM 10.5 and the OVA came with a 80 gig drive.
>
> Now I'm bouncing at my 90% used common partition.
>
> is this normal?  is this a bug?  is it that i'm using a 80 gig drive.
>
> Before I open a TAC case... What is the underlining issue?
>
> TIA
>
> Scott
>
>
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] Cisco IP Phone upgrades

2015-10-28 Thread Stephen Welsh

I’m sure there will be a few people on this list that will be in a situation 
where they (or their clients) are planning to replace the older Cisco IP Phone 
models with some of the nice new handsets that are now available.

Although there is the built-in Phone Migration feature in CUCM, it required a 
lot of effort and co-ordination to use, and the native CUCM migration feature 
does not handle phone button templates unfortunately.

Well Cisco and UnifiedFX have been working together to eliminate all of the 
pain points for upgrading Cisco phones, now it’s just a case of physically 
swapping the phone, our new product ‘MigrationFX’ dynamically migrates the 
phone configuration (including phone button templates) and automagically 
identifies the old phone to migrate.

The part where Cisco come-in is the price, MigrationFX is free to anyone 
submitting a Technology Migration for 100 or more Cisco phones and includes the 
MigrationFX promo code 'L-CP-MGFX-PROMO=‘

We have also provided a Free ‘Lab Edition’ of MigrationFX for anyone to install 
and test in the meantime, rather than having to wait for the GPL order to 
complete before getting started

I suggest you visit this page to find out more, including a demo of MigrationFX 
in action:

http://www.unifiedfx.com/get-migrationfx-for-free

Kind Regards.

Stephen Welsh
CTO
UnifiedFX
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] 7821 phones issue

Re: [cisco-voip] 8831 stuck on logo on keypad

[cisco-voip] 8831 stuck on logo on keypad

Re: [cisco-voip] UCCX Upgrade - minor

[cisco-voip] 7821 phones issue

Re: [cisco-voip] 8831 stuck on logo on keypad

Re: [cisco-voip] 7821 phones issue

Re: [cisco-voip] 7821 phones issue

Re: [cisco-voip] 7821 phones issue

[cisco-voip] be6kS

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Re: [cisco-voip] 8831 stuck on logo on keypad

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Re: [cisco-voip] UCCX Upgrade - minor

[cisco-voip] CM 8.6 to 10.5 common Partition

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Re: [cisco-voip] Unity Connection 10.5.2 Split Brain Recovery

Re: [cisco-voip] 7821 phones issue

Re: [cisco-voip] CM 8.6 to 10.5 common Partition

[cisco-voip] Cisco IP Phone upgrades

23 matches

Site Navigation

Mail list logo

Footer information