Re: [cisco-voip] moving voicemail integration from exchange 2003 to 2010

[Sreekanth Narayanan]

According to this document, the CUC cannot detect automatic move of the
mailboxes from Exchange 2003 to 2010.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcucumgx/9xcucumg030.html

So I believe you'd need to follow the steps in Replacing Unity Connection
Unified Messaging Accounts After Moving Exchange Mailboxes.

On 24 September 2015 at 18:41, Jorge L. Rodriguez Aguila <
jorge.rodrig...@netxar.com> wrote:

> they are already running unity connection 9.0, and unified messaging on
> exchange 2003 but will be migrating to exchange 2010 shortly
>
>
> Jorge Rodriguez, CCNP, CCNP-V
> Senior Voice/Data Network Consultant
> Netxar Technologies, a Digicel Company
> Cel 7876888530
> Office 7877650058
> jorge.rodrig...@netxar.com
>
>
>
>
> On Sep 24, 2015, at 9:08 AM, Sreekanth Narayanan 
> wrote:
>
> I'm guessing you're using Unity?
>
>
> www.cisco.com/c/en/us/td/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.pdf
>
>
>
> On 24 September 2015 at 18:33, Jorge L. Rodriguez Aguila <
> jorge.rodrig...@netxar.com> wrote:
>
>> Is this basically breaking whats done and starting over or is there some
>> documented path to move the integration from 2003 to 2010?
>>
>>
>> Jorge Rodriguez, CCNP, CCNP-V
>> Senior Voice/Data Network Consultant
>> Netxar Technologies, a Digicel Company
>> Cel 7876888530
>> Office 7877650058
>> jorge.rodrig...@netxar.com
>>
>>
>>
>>
>>
>> ___
>> 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] moving voicemail integration from exchange 2003 to 2010

[Jorge L. Rodriguez Aguila]

Thanks will do then



Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com




On Sep 24, 2015, at 9:27 AM, Sreekanth Narayanan 
> wrote:

According to this document, the CUC cannot detect automatic move of the 
mailboxes from Exchange 2003 to 2010.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcucumgx/9xcucumg030.html

So I believe you'd need to follow the steps in Replacing Unity Connection 
Unified Messaging Accounts After Moving Exchange Mailboxes.

On 24 September 2015 at 18:41, Jorge L. Rodriguez Aguila 
> wrote:
they are already running unity connection 9.0, and unified messaging on 
exchange 2003 but will be migrating to exchange 2010 shortly


Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com




On Sep 24, 2015, at 9:08 AM, Sreekanth Narayanan 
> wrote:

I'm guessing you're using Unity?

www.cisco.com/c/en/us/td/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.pdf



On 24 September 2015 at 18:33, Jorge L. Rodriguez Aguila 
> wrote:
Is this basically breaking whats done and starting over or is there some 
documented path to move the integration from 2003 to 2010?


Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com





___
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] moving voicemail integration from exchange 2003 to 2010

[Jorge L. Rodriguez Aguila]

Is this basically breaking whats done and starting over or is there some 
documented path to move the integration from 2003 to 2010?


Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com




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

Re: [cisco-voip] moving voicemail integration from exchange 2003 to 2010

[Sreekanth Narayanan]

I'm guessing you're using Unity?

www.cisco.com/c/en/us/td/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.pdf



On 24 September 2015 at 18:33, Jorge L. Rodriguez Aguila <
jorge.rodrig...@netxar.com> wrote:

> Is this basically breaking whats done and starting over or is there some
> documented path to move the integration from 2003 to 2010?
>
>
> Jorge Rodriguez, CCNP, CCNP-V
> Senior Voice/Data Network Consultant
> Netxar Technologies, a Digicel Company
> Cel 7876888530
> Office 7877650058
> jorge.rodrig...@netxar.com
>
>
>
>
>
> ___
> 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] moving voicemail integration from exchange 2003 to 2010

[Jorge L. Rodriguez Aguila]

they are already running unity connection 9.0, and unified messaging on 
exchange 2003 but will be migrating to exchange 2010 shortly


Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com




On Sep 24, 2015, at 9:08 AM, Sreekanth Narayanan 
> wrote:

I'm guessing you're using Unity?

www.cisco.com/c/en/us/td/docs/voice_ip_comm/unity/7x/using_exch2010/usingex2010withcu7x5x.pdf



On 24 September 2015 at 18:33, Jorge L. Rodriguez Aguila 
> wrote:
Is this basically breaking whats done and starting over or is there some 
documented path to move the integration from 2003 to 2010?


Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com





___
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] moving voicemail integration from exchange 2003 to 2010

[Chris Ward (chrward)]

I assume this is Unity Connection Single Inbox integration?

If so, then just add the new integration to Unity Connection (it can host 
multiple Exchange integrations at once), and as you move mailboxes, you change 
their Exchange integration on Connection to the new instance. Should be quick 
and painless.

+Chris
TME - MediaSense

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jorge 
L. Rodriguez Aguila
Sent: Thursday, September 24, 2015 9:03 AM
To: Cisco-Voip 
Subject: [cisco-voip] moving voicemail integration from exchange 2003 to 2010

Is this basically breaking whats done and starting over or is there some 
documented path to move the integration from 2003 to 2010?

Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com



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

Re: [cisco-voip] moving voicemail integration from exchange 2003 to 2010

[Jorge L. Rodriguez Aguila]

That looks like the way yo go, thanks guys for the info


Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com




On Sep 24, 2015, at 9:46 AM, Chris Ward (chrward) 
> wrote:

I assume this is Unity Connection Single Inbox integration?

If so, then just add the new integration to Unity Connection (it can host 
multiple Exchange integrations at once), and as you move mailboxes, you change 
their Exchange integration on Connection to the new instance. Should be quick 
and painless.

+Chris
TME - MediaSense

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Jorge 
L. Rodriguez Aguila
Sent: Thursday, September 24, 2015 9:03 AM
To: Cisco-Voip >
Subject: [cisco-voip] moving voicemail integration from exchange 2003 to 2010

Is this basically breaking whats done and starting over or is there some 
documented path to move the integration from 2003 to 2010?

Jorge Rodriguez, CCNP, CCNP-V
Senior Voice/Data Network Consultant
Netxar Technologies, a Digicel Company
Cel 7876888530
Office 7877650058
jorge.rodrig...@netxar.com

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

[cisco-voip] LDAP error on CUC

[Jonathan Charles]

We are integrated CUC/CUCM with AD (version 10.5)...

We can import users from AD (Users - Import Users - from LDAP) successfully.

The same user cannot be converted from local to AD (checking box Integrate
with LDAP Directory on the CUC User page)...

The error returned is "This user cannot be associated with the LDAP
Directory."

Google returns no results...

Any ideas?




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

Re: [cisco-voip] LDAP error on CUC

[Chris Ward (chrward)]

Did a quick search inside our knowledge base here, looks like this will need a 
TAC case. In some cases a reboot fixes it and in other cases, the DB needs some 
touching to resolve. If you are up for it, it would be good to try and figure 
out root cause, so please open a TAC case and let them do some troubleshooting.

If you are in a crunch, you can try a reboot of the CUC node/cluster.

+Chris
TME - MediaSense

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Jonathan Charles
Sent: Thursday, September 24, 2015 11:45 AM
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] LDAP error on CUC

Please note that this is for ALL users...

On Thu, Sep 24, 2015 at 10:44 AM, Jonathan Charles 
> wrote:
We are integrated CUC/CUCM with AD (version 10.5)...

We can import users from AD (Users - Import Users - from LDAP) successfully.

The same user cannot be converted from local to AD (checking box Integrate with 
LDAP Directory on the CUC User page)...

The error returned is "This user cannot be associated with the LDAP Directory."

Google returns no results...

Any ideas?




Jonathan

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

Re: [cisco-voip] LDAP error on CUC

[Ryan Huff]

I'm assuming that you have performed a directory synchronization in Unity 
Connections first, then attempted the import (and the local Unity Connections 
account name matches the AD account name).
 
Thanks,
 
Ryan
 
Date: Thu, 24 Sep 2015 10:45:25 -0500
From: jonv...@gmail.com
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] LDAP error on CUC

Please note that this is for ALL users... 
On Thu, Sep 24, 2015 at 10:44 AM, Jonathan Charles  wrote:
We are integrated CUC/CUCM with AD (version 10.5)...
We can import users from AD (Users - Import Users - from LDAP) successfully.
The same user cannot be converted from local to AD (checking box Integrate with 
LDAP Directory on the CUC User page)...
The error returned is "This user cannot be associated with the LDAP Directory."
Google returns no results...
Any ideas?



Jonathan



___
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] Comcast PRI in US and calls to international missing US country code +1

[Jason Aarons (AM)]

Customer has a Comcast Business PRI.

I am sending the Calling Party Number as 10 Digits and Type/National with 
Plan/ISDN for calls to Austria.

Problem is Austria is not seeing the +1 country code for calls coming in.

Comcast Support is taking a long time to tell me what the Type/Plan is they 
want to see on outgoing International calls.  If I send a 1 with Type 
International they give a switch error.   Anyone worked with Comcast Business 
PRIs before?

Sep 23 12:42:48.830: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8  callref = 0x00E4
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Display i = 'DiData TEST'
Calling Party Number i = 0x2181, '2484135692'
Plan:ISDN, Type:National
Called Party Number i = 0x80, '01143577336616'
Plan:Unknown, Type:Unknown
*Sep 23 12:42:48.846: ISDN Se0/1/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 
0x80E4
Channel ID i = 0xA98

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

Re: [cisco-voip] LDAP error on CUC

[Jonathan Charles]

Please note that this is for ALL users...

On Thu, Sep 24, 2015 at 10:44 AM, Jonathan Charles 
wrote:

> We are integrated CUC/CUCM with AD (version 10.5)...
>
> We can import users from AD (Users - Import Users - from LDAP)
> successfully.
>
> The same user cannot be converted from local to AD (checking box Integrate
> with LDAP Directory on the CUC User page)...
>
> The error returned is "This user cannot be associated with the LDAP
> Directory."
>
> Google returns no results...
>
> Any ideas?
>
>
>
>
> Jonathan
>
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] LDAP error on CUC

[Jonathan Charles]

OK, I think I have this figured out... these users were initially
configured as synched from CUCM; they were then deleted and were bulked in
via BAT... now, they are trying to be set up to sync with AD...

If you delete a user (we are pre-production) and then import them from AD,
it says it fails with a reason of 'null' but the user imports anyway and
claims to be integrated to AD...



Jonathan

On Thu, Sep 24, 2015 at 11:01 AM, Ryan Huff  wrote:

> I'm assuming that you have performed a directory synchronization in Unity
> Connections first, then attempted the import (and the local Unity
> Connections account name matches the AD account name).
>
> Thanks,
>
> Ryan
>
> --
> Date: Thu, 24 Sep 2015 10:45:25 -0500
> From: jonv...@gmail.com
> To: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] LDAP error on CUC
>
> Please note that this is for ALL users...
>
> On Thu, Sep 24, 2015 at 10:44 AM, Jonathan Charles 
> wrote:
>
> We are integrated CUC/CUCM with AD (version 10.5)...
>
> We can import users from AD (Users - Import Users - from LDAP)
> successfully.
>
> The same user cannot be converted from local to AD (checking box Integrate
> with LDAP Directory on the CUC User page)...
>
> The error returned is "This user cannot be associated with the LDAP
> Directory."
>
> Google returns no results...
>
> Any ideas?
>
>
>
>
> Jonathan
>
>
>
> ___ 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] LDAP error on CUC

[Ryan Huff]

To convert local accounts to AD synced you should perform the directory sync, 
then use the checkbox in the account to integrate with ldap (or use the bat 
tool). After you import an account from AD, the account is no longer in Unity's 
cached ad account list for Unity to match the local account with.

Thanks,

Ryan

Sent from my T-Mobile 4G LTE Device

 Original message 
From: Ryan Huff  
Date:09/24/2015  12:01 PM  (GMT-05:00) 
To: Jonathan Charles ,cisco-voip@puck.nether.net 
Subject: Re: [cisco-voip] LDAP error on CUC 

I'm assuming that you have performed a directory synchronization in Unity 
Connections first, then attempted the import (and the local Unity Connections 
account name matches the AD account name).
 
Thanks,
 
Ryan
 
Date: Thu, 24 Sep 2015 10:45:25 -0500
From: jonv...@gmail.com
To: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] LDAP error on CUC

Please note that this is for ALL users... 

On Thu, Sep 24, 2015 at 10:44 AM, Jonathan Charles  wrote:
We are integrated CUC/CUCM with AD (version 10.5)...

We can import users from AD (Users - Import Users - from LDAP) successfully.

The same user cannot be converted from local to AD (checking box Integrate with 
LDAP Directory on the CUC User page)...

The error returned is "This user cannot be associated with the LDAP Directory."

Google returns no results...

Any ideas?




Jonathan


___ 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] UCCX 10.6(1) SU1 CAD Upgrade Warning

[Justin Steinberg]

The current UCCX compatibility matrix lists CAD 10.6.1.95 for both UCCX
10.6(1) and 10.6(1)SU1, implying there is no CAD upgrade forced after the
SU1 upgrade.

This isn't the case.   Upgrading 10.6(1) to 10.6(1)su1 does force a CAD
upgrade.

Hopefully this helps someone else.

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

Re: [cisco-voip] LDAP error on CUC

[Jonathan Charles]

I was able to delete the users, and import them and they show up as AD
integrated... I think synching them from CUCM blew a lot up...


Jonathan

On Thu, Sep 24, 2015 at 11:14 AM, Ryan Huff  wrote:

> To convert local accounts to AD synced you should perform the directory
> sync, then use the checkbox in the account to integrate with ldap (or use
> the bat tool). After you import an account from AD, the account is no
> longer in Unity's cached ad account list for Unity to match the local
> account with.
>
> Thanks,
>
> Ryan
>
> Sent from my T-Mobile 4G LTE Device
>
>
>  Original message 
> From: Ryan Huff
> Date:09/24/2015 12:01 PM (GMT-05:00)
> To: Jonathan Charles ,cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] LDAP error on CUC
>
> I'm assuming that you have performed a directory synchronization in Unity
> Connections first, then attempted the import (and the local Unity
> Connections account name matches the AD account name).
>
> Thanks,
>
> Ryan
>
> --
> Date: Thu, 24 Sep 2015 10:45:25 -0500
> From: jonv...@gmail.com
> To: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] LDAP error on CUC
>
> Please note that this is for ALL users...
>
> On Thu, Sep 24, 2015 at 10:44 AM, Jonathan Charles 
> wrote:
>
> We are integrated CUC/CUCM with AD (version 10.5)...
>
> We can import users from AD (Users - Import Users - from LDAP)
> successfully.
>
> The same user cannot be converted from local to AD (checking box Integrate
> with LDAP Directory on the CUC User page)...
>
> The error returned is "This user cannot be associated with the LDAP
> Directory."
>
> Google returns no results...
>
> Any ideas?
>
>
>
>
> Jonathan
>
>
>
> ___ 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] Smart Call Home on CUCM 10.5 and DNS

[Brian Meade]

By setting the domain, all certificates will be regenerated to put the new
FQDN in the certs.  Setting the domain will force a CUCM reboot.  If you
have more than one node, you're pretty safe to let all phones re-register
and use another node's TVS to validate the new certs from the other node.
You definitely don't want to do more than one server at a time.

The way I do it to be extra safe is enable the Rollback to Pre-8.x
Enterprise Parameter which resets all phones giving them a blank ITL.  You
can then set the domain on each servers and have them reboot.  Once they're
all back online, disable the Rollback which will reset all of the phones
again and give them the new ITLs with the updated certs.

Any phones not connected during this process will have ITL issues and the
ITLs will need to be manually deleted or deleted via a 3rd party tool such
as Phone View from UnifiedFX.

On Thu, Sep 24, 2015 at 12:48 PM, Johnson, Ken  wrote:

> We recently upgraded to CUCM 10.5 and got an alert that we needed to
> configure Smart Call Home.
>
>
>
> We didn’t know much about it so researched it and it looked like something
> good to configure so we did – and then got the error that it couldn’t send
> the initial messages because we didn’t have DNS configured on our cluster.
>
>
>
> Researching that – it looked like adding DNS at the CLI level was
> straightforward:
>
>
>
> Set network dns
>
> set network dns primary 2.2.2.2
>
> set network dns secondary 1.1.1.1
>
> set network domain domain.com
>
>
>
> but per following document (admittedly for 8.x but presume it is similar
> for 10) it looks like adding the DNS server values could result in a need
> for careful re-push of ITL
>
>
>
>
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/8_6_1/install/cmins861.html#wp463644
>
>
>
> If this is the case we’d have to follow the processes at
>
>
> http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/10_0_1/ipchange/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100_chapter_0101.html#CUCM_TK_R63ED7F7_00
>
>
>
> My question is – since we have no DNS client active, no servers
> configured, and no domain name set on our cluster today – will adding any
> of those force the kind of careful ITL and other guidance the document
> above references – or is that only caused by changing these values.
>
>
>
> Alternately – since we don’t need the DNS domain set (unless Smart Home
> needs it) could we just enable the DNS client and add the DNS servers
> without setting the domain and avoid any cluster-wide major impact?
>
>
>
> Thanks!
>
>
>
> Ken Johnson
>
> ___
> 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 10.6(1) SU1 CAD Upgrade Warning

[Abhiram Kramadhati (akramadh)]

Thank you Justin, I will get this corrected. Appreciate your heads-up here.

Regards,
Abhiram Kramadhati
Technical Solutions Manager, CBABU
CCIE Collaboration # 40065

From: Justin Steinberg >
Date: Friday, 25 September 2015 2:41 am
To: Cisco VOIP >
Subject: [cisco-voip] UCCX 10.6(1) SU1 CAD Upgrade Warning

The current UCCX compatibility matrix lists CAD 10.6.1.95 for both UCCX 10.6(1) 
and 10.6(1)SU1, implying there is no CAD upgrade forced after the SU1 upgrade.

This isn't the case.   Upgrading 10.6(1) to 10.6(1)su1 does force a CAD upgrade.

Hopefully this helps someone else.

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

[cisco-voip] Smart Call Home on CUCM 10.5 and DNS

[Johnson, Ken]

We recently upgraded to CUCM 10.5 and got an alert that we needed to configure 
Smart Call Home.

We didn’t know much about it so researched it and it looked like something good 
to configure so we did – and then got the error that it couldn’t send the 
initial messages because we didn’t have DNS configured on our cluster.

Researching that – it looked like adding DNS at the CLI level was 
straightforward:

Set network dns
set network dns primary 2.2.2.2
set network dns secondary 1.1.1.1
set network domain domain.com

but per following document (admittedly for 8.x but presume it is similar for 
10) it looks like adding the DNS server values could result in a need for 
careful re-push of ITL

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/8_6_1/install/cmins861.html#wp463644

If this is the case we’d have to follow the processes at
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/install/10_0_1/ipchange/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100/CUCM_BK_C3782AAB_00_change-ipaddress-hostname-100_chapter_0101.html#CUCM_TK_R63ED7F7_00

My question is – since we have no DNS client active, no servers configured, and 
no domain name set on our cluster today – will adding any of those force the 
kind of careful ITL and other guidance the document above references – or is 
that only caused by changing these values.

Alternately – since we don’t need the DNS domain set (unless Smart Home needs 
it) could we just enable the DNS client and add the DNS servers without setting 
the domain and avoid any cluster-wide major impact?

Thanks!

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

Re: [cisco-voip] Comcast PRI in US and calls to international missing US country code +1

[Dave Goodwin]

Jason, I have seen different behaviors from different central office
switches/providers; there doesn't seem to be a lot of consistency. I have
often had to rely on trial and error until I find the right combination -
and make sure to try dialing both land-based and mobile lines, as the
behavior on the receiving end can vary based on the called party's provider
as well.

Have you tried both 10D and 11D using Type/Unknown and Plan/Unknown, as you
did for the *called *party number in the example above?

-Dave

On Thu, Sep 24, 2015 at 11:38 AM, NateCCIE  wrote:

> I’ve never had much success manipulating it.  With all of the NNIs it
> seems to be hit or miss.  I have had places where I have different
> dedicated LD providers and some will send good full number to a country and
> others wont.
>
>
>
> You could try just 11D and see if the far end any happier.
>
>
>
> -Nate
>
> *From:* cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] *On Behalf
> Of *Jason Aarons (AM)
> *Sent:* Thursday, September 24, 2015 9:31 AM
> *To:* cisco-voip 
> *Subject:* [cisco-voip] Comcast PRI in US and calls to international
> missing US country code +1
>
>
>
> Customer has a Comcast Business PRI.
>
>
>
> I am sending the Calling Party Number as 10 Digits and Type/National with
> Plan/ISDN for calls to Austria.
>
>
>
> Problem is Austria is not seeing the +1 country code for calls coming in.
>
>
>
> Comcast Support is taking a long time to tell me what the Type/Plan is
> they want to see on outgoing International calls.  If I send a 1 with Type
> International they give a switch error.   Anyone worked with Comcast
> Business PRIs before?
>
>
>
> Sep 23 12:42:48.830: ISDN Se0/1/0:23 Q931: TX -> SETUP pd = 8  callref =
> 0x00E4
>
> Bearer Capability i = 0x8090A2
>
> Standard = CCITT
>
> Transfer Capability = Speech
>
> Transfer Mode = Circuit
>
> Transfer Rate = 64 kbit/s
>
> Channel ID i = 0xA98397
>
> Exclusive, Channel 23
>
> Display i = 'DiData TEST'
>
> Calling Party Number i = 0x2181, '2484135692'
>
> Plan:ISDN, Type:National
>
> Called Party Number i = 0x80, '01143577336616'
>
> Plan:Unknown, Type:Unknown
>
> *Sep 23 12:42:48.846: ISDN Se0/1/0:23 Q931: RX <- CALL_PROC pd = 8
> callref = 0x80E4
>
> Channel ID i = 0xA98
>
>
>
> ___
> 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