Re: [cisco-voip] [External] [External] Re: CUCM call set up issue after migration

2021-01-12 Thread Hunter Fuller via cisco-voip 
Well you’re no fun.

On Wed, Jan 13, 2021 at 00:17 Kent Roberts  wrote:

> Ah, except I edge was rebooted 4 hours before cause it went stupid.
>
>
> On Jan 12, 2021, at 11:10 PM, Hunter Fuller  wrote:
>
> Easy peasy. Reboot half of the E nodes after x/2 days. Now the reboots are
> staggered, no further impact to users. Next question. Am I rich yet?
>
> On Wed, Jan 13, 2021 at 00:08 Kent Roberts  wrote:
>
>> We have a new expressway funness.   Edge side of the cluster all reboot
>> at one time.. every x number of days….
>>
>> Take the easy ones!
>>
>>
>> On Jan 12, 2021, at 10:41 PM, Hunter Fuller via cisco-voip <
>> cisco-voip@puck.nether.net> wrote:
>>
>> Whoever said that has clearly never administered Expressway.
>>
>> On Tue, Jan 12, 2021 at 23:25 Anthony Holloway <
>> avholloway+cisco-v...@gmail.com> wrote:
>>
>>> Nice! That was easy.  This email chain goes into my folder called: When
>>> Someone Says Only Windows Servers Need Reboots.
>>>
>>> On Tue, Jan 12, 2021 at 7:40 PM Riley, Sean 
>>> wrote:
>>>
 So far it seems the reboot resolved this problem.  Thanks for all the
 replies with guidance and help.



 *From:* Kent Roberts 
 *Sent:* Tuesday, January 12, 2021 4:42 PM
 *To:* Riley, Sean 
 *Cc:* cisco-voip@puck.nether.net
 *Subject:* Re: [cisco-voip] CUCM call set up issue after migration



 Ah split brains. Gotta love it.   Did you restart the ones that did not
 move?I have seen this when things go stupid. The sync usually isn’t the
 problem it’s the real-time communication between the nodes that’s all
 messed up. Usually can fix with a node reboot or restarting the cucm
 and cti services.   Course their maybe more to it but if things are in sync
  should not be hard to fix



 Kent



 On Jan 12, 2021, at 14:06, Riley, Sean 
 wrote:

 

 This past weekend we migrated 2 CUCM servers to a new datacenter.  This
 involved changing the IP address on these 2 CUCM nodes.  These 2 nodes
 consist of the Publisher and 1 Subscriber.  We have another Sub at a remote
 datacenter that was not touched this past weekend.



 Node configuration:



 DC A

 CM1: Pub which was re-ip’d

 CM2: Sub which was re-ip’d



 DC B:

 CM3: Sub at remote site that was not changed



 Phones are at many sites, but issue is independent of the phone type,
 phone location or subnet.  Also, Expressway phones have the same issue.



 The issue is any phone that is registered to CM3 cannot call phones
 registered to CM1 or CM2 and vice versa.  The phones do not see the call
 coming in.  If SNR is configured, the call will ring to the remote
 destination. Phones registered to CM3 can make outbound PSTN calls without
 issue, but not receive inbound from PSTN (probably because the gateway is
 handing off to CM1 or CM2).  While the gateways are not unique to the
 issue, they are running H323.



 If the phones are both registered to CM3, they can call each other, but
 not phones registered to CM1 or CM2.



 I have had my network team verify there is not anything they can see in
 the network causing this behavior. Database replication checks out OK and I
 can ping from/to each node.



 Anyone able to point me in the right direction to figure this out?



 Thanks.

 ___
 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
>>>
>> --
>>
>> --
>> Hunter Fuller (they)
>> Router Jockey
>> VBH Annex B-5
>> +1 256 824 5331
>>
>> Office of Information Technology
>> The University of Alabama in Huntsville
>> Network Engineering
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>> --
>
> --
> Hunter Fuller (they)
> Router Jockey
> VBH Annex B-5
> +1 256 824 5331
>
> Office of Information Technology
> The University of Alabama in Huntsville
> Network Engineering
>
>
> --

--
Hunter Fuller (they)
Router Jockey
VBH Annex B-5
+1 256 824 5331

Office of Information Technology
The University of Alabama in Huntsville
Network Engineering
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] [External] [External] Re: CUCM call set up issue after migration

2021-01-12 Thread Kent Roberts 
Ah, except I edge was rebooted 4 hours before cause it went stupid.

> On Jan 12, 2021, at 11:10 PM, Hunter Fuller  wrote:
> 
> Easy peasy. Reboot half of the E nodes after x/2 days. Now the reboots are 
> staggered, no further impact to users. Next question. Am I rich yet? 
> 
> On Wed, Jan 13, 2021 at 00:08 Kent Roberts  > wrote:
> We have a new expressway funness.   Edge side of the cluster all reboot at 
> one time.. every x number of days….
> 
> Take the easy ones!
> 
> 
>> On Jan 12, 2021, at 10:41 PM, Hunter Fuller via cisco-voip 
>> mailto:cisco-voip@puck.nether.net>> wrote:
>> 
>> Whoever said that has clearly never administered Expressway. 
>> 
>> On Tue, Jan 12, 2021 at 23:25 Anthony Holloway 
>> mailto:avholloway%2bcisco-v...@gmail.com>> 
>> wrote:
>> Nice! That was easy.  This email chain goes into my folder called: When 
>> Someone Says Only Windows Servers Need Reboots.
>> 
>> On Tue, Jan 12, 2021 at 7:40 PM Riley, Sean > > wrote:
>> So far it seems the reboot resolved this problem.  Thanks for all the 
>> replies with guidance and help.
>> 
>>  
>> 
>> From: Kent Roberts mailto:k...@fredf.org>> 
>> Sent: Tuesday, January 12, 2021 4:42 PM
>> To: Riley, Sean > >
>> Cc: cisco-voip@puck.nether.net 
>> Subject: Re: [cisco-voip] CUCM call set up issue after migration
>> 
>>  
>> 
>> Ah split brains. Gotta love it.   Did you restart the ones that did not 
>> move?I have seen this when things go stupid. The sync usually isn’t the 
>> problem it’s the real-time communication between the nodes that’s all messed 
>> up. Usually can fix with a node reboot or restarting the cucm and cti 
>> services.   Course their maybe more to it but if things are in sync  should 
>> not be hard to fix
>> 
>>  
>> 
>> Kent
>> 
>> 
>> 
>> 
>> On Jan 12, 2021, at 14:06, Riley, Sean > > wrote:
>> 
>> 
>> 
>> This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
>> involved changing the IP address on these 2 CUCM nodes.  These 2 nodes 
>> consist of the Publisher and 1 Subscriber.  We have another Sub at a remote 
>> datacenter that was not touched this past weekend.
>> 
>>  
>> 
>> Node configuration:
>> 
>>  
>> 
>> DC A
>> 
>> CM1: Pub which was re-ip’d
>> 
>> CM2: Sub which was re-ip’d
>> 
>>  
>> 
>> DC B:
>> 
>> CM3: Sub at remote site that was not changed
>> 
>>  
>> 
>> Phones are at many sites, but issue is independent of the phone type, phone 
>> location or subnet.  Also, Expressway phones have the same issue.
>> 
>>  
>> 
>> The issue is any phone that is registered to CM3 cannot call phones 
>> registered to CM1 or CM2 and vice versa.  The phones do not see the call 
>> coming in.  If SNR is configured, the call will ring to the remote 
>> destination. Phones registered to CM3 can make outbound PSTN calls without 
>> issue, but not receive inbound from PSTN (probably because the gateway is 
>> handing off to CM1 or CM2).  While the gateways are not unique to the issue, 
>> they are running H323.
>> 
>>  
>> 
>> If the phones are both registered to CM3, they can call each other, but not 
>> phones registered to CM1 or CM2.
>> 
>>  
>> 
>> I have had my network team verify there is not anything they can see in the 
>> network causing this behavior. Database replication checks out OK and I can 
>> ping from/to each node.
>> 
>>  
>> 
>> Anyone able to point me in the right direction to figure this out?
>> 
>>  
>> 
>> Thanks.
>> 
>> ___
>> 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 
>> 
>> -- 
>> 
>> --
>> Hunter Fuller (they)
>> Router Jockey
>> VBH Annex B-5
>> +1 256 824 5331
>> 
>> Office of Information Technology
>> The University of Alabama in Huntsville
>> Network Engineering
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net 
>> https://puck.nether.net/mailman/listinfo/cisco-voip 
>> 
> 
> -- 
> 
> --
> Hunter Fuller (they)
> Router Jockey
> VBH Annex B-5
> +1 256 824 5331
> 
> Office of Information Technology
> The University of Alabama in Huntsville
> Network Engineering

Re: [cisco-voip] [External] Re: CUCM call set up issue after migration

2021-01-12 Thread Kent Roberts 
We have a new expressway funness.   Edge side of the cluster all reboot at one 
time.. every x number of days….

Take the easy ones!

> On Jan 12, 2021, at 10:41 PM, Hunter Fuller via cisco-voip 
>  wrote:
> 
> Whoever said that has clearly never administered Expressway. 
> 
> On Tue, Jan 12, 2021 at 23:25 Anthony Holloway 
> mailto:avholloway%2bcisco-v...@gmail.com>> 
> wrote:
> Nice! That was easy.  This email chain goes into my folder called: When 
> Someone Says Only Windows Servers Need Reboots.
> 
> On Tue, Jan 12, 2021 at 7:40 PM Riley, Sean  > wrote:
> So far it seems the reboot resolved this problem.  Thanks for all the replies 
> with guidance and help.
> 
>  
> 
> From: Kent Roberts mailto:k...@fredf.org>> 
> Sent: Tuesday, January 12, 2021 4:42 PM
> To: Riley, Sean  >
> Cc: cisco-voip@puck.nether.net 
> Subject: Re: [cisco-voip] CUCM call set up issue after migration
> 
>  
> 
> Ah split brains. Gotta love it.   Did you restart the ones that did not move? 
>I have seen this when things go stupid. The sync usually isn’t the problem 
> it’s the real-time communication between the nodes that’s all messed up. 
> Usually can fix with a node reboot or restarting the cucm and cti services.   
> Course their maybe more to it but if things are in sync  should not be hard 
> to fix
> 
>  
> 
> Kent
> 
> 
> 
> 
> On Jan 12, 2021, at 14:06, Riley, Sean  > wrote:
> 
> 
> 
> This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
> involved changing the IP address on these 2 CUCM nodes.  These 2 nodes 
> consist of the Publisher and 1 Subscriber.  We have another Sub at a remote 
> datacenter that was not touched this past weekend.
> 
>  
> 
> Node configuration:
> 
>  
> 
> DC A
> 
> CM1: Pub which was re-ip’d
> 
> CM2: Sub which was re-ip’d
> 
>  
> 
> DC B:
> 
> CM3: Sub at remote site that was not changed
> 
>  
> 
> Phones are at many sites, but issue is independent of the phone type, phone 
> location or subnet.  Also, Expressway phones have the same issue.
> 
>  
> 
> The issue is any phone that is registered to CM3 cannot call phones 
> registered to CM1 or CM2 and vice versa.  The phones do not see the call 
> coming in.  If SNR is configured, the call will ring to the remote 
> destination. Phones registered to CM3 can make outbound PSTN calls without 
> issue, but not receive inbound from PSTN (probably because the gateway is 
> handing off to CM1 or CM2).  While the gateways are not unique to the issue, 
> they are running H323.
> 
>  
> 
> If the phones are both registered to CM3, they can call each other, but not 
> phones registered to CM1 or CM2.
> 
>  
> 
> I have had my network team verify there is not anything they can see in the 
> network causing this behavior. Database replication checks out OK and I can 
> ping from/to each node.
> 
>  
> 
> Anyone able to point me in the right direction to figure this out?
> 
>  
> 
> Thanks.
> 
> ___
> 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 
> 
> -- 
> 
> --
> Hunter Fuller (they)
> Router Jockey
> VBH Annex B-5
> +1 256 824 5331
> 
> Office of Information Technology
> The University of Alabama in Huntsville
> Network Engineering
> ___
> 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] [External] Re: CUCM call set up issue after migration

2021-01-12 Thread Hunter Fuller via cisco-voip 
Whoever said that has clearly never administered Expressway.

On Tue, Jan 12, 2021 at 23:25 Anthony Holloway <
avholloway+cisco-v...@gmail.com> wrote:

> Nice! That was easy.  This email chain goes into my folder called: When
> Someone Says Only Windows Servers Need Reboots.
>
> On Tue, Jan 12, 2021 at 7:40 PM Riley, Sean 
> wrote:
>
>> So far it seems the reboot resolved this problem.  Thanks for all the
>> replies with guidance and help.
>>
>>
>>
>> *From:* Kent Roberts 
>> *Sent:* Tuesday, January 12, 2021 4:42 PM
>> *To:* Riley, Sean 
>> *Cc:* cisco-voip@puck.nether.net
>> *Subject:* Re: [cisco-voip] CUCM call set up issue after migration
>>
>>
>>
>> Ah split brains. Gotta love it.   Did you restart the ones that did not
>> move?I have seen this when things go stupid. The sync usually isn’t the
>> problem it’s the real-time communication between the nodes that’s all
>> messed up. Usually can fix with a node reboot or restarting the cucm
>> and cti services.   Course their maybe more to it but if things are in sync
>>  should not be hard to fix
>>
>>
>>
>> Kent
>>
>>
>>
>> On Jan 12, 2021, at 14:06, Riley, Sean 
>> wrote:
>>
>> 
>>
>> This past weekend we migrated 2 CUCM servers to a new datacenter.  This
>> involved changing the IP address on these 2 CUCM nodes.  These 2 nodes
>> consist of the Publisher and 1 Subscriber.  We have another Sub at a remote
>> datacenter that was not touched this past weekend.
>>
>>
>>
>> Node configuration:
>>
>>
>>
>> DC A
>>
>> CM1: Pub which was re-ip’d
>>
>> CM2: Sub which was re-ip’d
>>
>>
>>
>> DC B:
>>
>> CM3: Sub at remote site that was not changed
>>
>>
>>
>> Phones are at many sites, but issue is independent of the phone type,
>> phone location or subnet.  Also, Expressway phones have the same issue.
>>
>>
>>
>> The issue is any phone that is registered to CM3 cannot call phones
>> registered to CM1 or CM2 and vice versa.  The phones do not see the call
>> coming in.  If SNR is configured, the call will ring to the remote
>> destination. Phones registered to CM3 can make outbound PSTN calls without
>> issue, but not receive inbound from PSTN (probably because the gateway is
>> handing off to CM1 or CM2).  While the gateways are not unique to the
>> issue, they are running H323.
>>
>>
>>
>> If the phones are both registered to CM3, they can call each other, but
>> not phones registered to CM1 or CM2.
>>
>>
>>
>> I have had my network team verify there is not anything they can see in
>> the network causing this behavior. Database replication checks out OK and I
>> can ping from/to each node.
>>
>>
>>
>> Anyone able to point me in the right direction to figure this out?
>>
>>
>>
>> Thanks.
>>
>> ___
>> 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
>
-- 

--
Hunter Fuller (they)
Router Jockey
VBH Annex B-5
+1 256 824 5331

Office of Information Technology
The University of Alabama in Huntsville
Network Engineering
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Re: [cisco-voip] CUCM call set up issue after migration

2021-01-12 Thread Riley, Sean 
So far it seems the reboot resolved this problem.  Thanks for all the replies 
with guidance and help.

From: Kent Roberts 
Sent: Tuesday, January 12, 2021 4:42 PM
To: Riley, Sean 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] CUCM call set up issue after migration

Ah split brains. Gotta love it.   Did you restart the ones that did not move?   
 I have seen this when things go stupid. The sync usually isn’t the problem 
it’s the real-time communication between the nodes that’s all messed up. 
Usually can fix with a node reboot or restarting the cucm and cti services.   
Course their maybe more to it but if things are in sync  should not be hard to 
fix

Kent


On Jan 12, 2021, at 14:06, Riley, Sean 
mailto:sri...@robinsonbradshaw.com>> wrote:

This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
involved changing the IP address on these 2 CUCM nodes.  These 2 nodes consist 
of the Publisher and 1 Subscriber.  We have another Sub at a remote datacenter 
that was not touched this past weekend.

Node configuration:

DC A
CM1: Pub which was re-ip’d
CM2: Sub which was re-ip’d

DC B:
CM3: Sub at remote site that was not changed

Phones are at many sites, but issue is independent of the phone type, phone 
location or subnet.  Also, Expressway phones have the same issue.

The issue is any phone that is registered to CM3 cannot call phones registered 
to CM1 or CM2 and vice versa.  The phones do not see the call coming in.  If 
SNR is configured, the call will ring to the remote destination. Phones 
registered to CM3 can make outbound PSTN calls without issue, but not receive 
inbound from PSTN (probably because the gateway is handing off to CM1 or CM2).  
While the gateways are not unique to the issue, they are running H323.

If the phones are both registered to CM3, they can call each other, but not 
phones registered to CM1 or CM2.

I have had my network team verify there is not anything they can see in the 
network causing this behavior. Database replication checks out OK and I can 
ping from/to each node.

Anyone able to point me in the right direction to figure this out?

Thanks.
___
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] CUCM call set up issue after migration

2021-01-12 Thread Kent Roberts 
After your reboot login into that box, do your standard silly checkes…..   ping 
by name,  db replication, reverse lookup etc….


Once you shut down CM3.   The phones, (I assume….. you have other cm’s in the 
devicepool before SRST if your using it..))  should go over to your other cm’s. 
At that point you should be able to call them and everything should work as 
expected.   (Never hurts to check this while your box is down, easier then 
doing another outage window)

My place has about 15 nodes, and thousands of end points.This happens at 
times with upgrade etc,   TAC says its not supposed to happen, but…

Hopefully that will fix it for you.

If it doesn’t fix it, after 20 mins or so,  you might need to get tac involved 
if you are not good with reading traces to figure out why. 




> On Jan 12, 2021, at 2:47 PM, Riley, Sean  wrote:
> 
> Thanks for the quick reply.  I have a change request to restart the node that 
> did not move tonight.  I will follow up to let you know if this helped.
>  
> From: Kent Roberts  
> Sent: Tuesday, January 12, 2021 4:42 PM
> To: Riley, Sean 
> Cc: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] CUCM call set up issue after migration
>  
> Ah split brains. Gotta love it.   Did you restart the ones that did not move? 
>I have seen this when things go stupid. The sync usually isn’t the problem 
> it’s the real-time communication between the nodes that’s all messed up. 
> Usually can fix with a node reboot or restarting the cucm and cti services.   
> Course their maybe more to it but if things are in sync  should not be hard 
> to fix
> 
>  
> Kent
> 
> 
> On Jan 12, 2021, at 14:06, Riley, Sean  > wrote:
> 
>  
> This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
> involved changing the IP address on these 2 CUCM nodes.  These 2 nodes 
> consist of the Publisher and 1 Subscriber.  We have another Sub at a remote 
> datacenter that was not touched this past weekend.
>  
> Node configuration:
>  
> DC A
> CM1: Pub which was re-ip’d
> CM2: Sub which was re-ip’d
>  
> DC B:
> CM3: Sub at remote site that was not changed
>  
> Phones are at many sites, but issue is independent of the phone type, phone 
> location or subnet.  Also, Expressway phones have the same issue.
>  
> The issue is any phone that is registered to CM3 cannot call phones 
> registered to CM1 or CM2 and vice versa.  The phones do not see the call 
> coming in.  If SNR is configured, the call will ring to the remote 
> destination. Phones registered to CM3 can make outbound PSTN calls without 
> issue, but not receive inbound from PSTN (probably because the gateway is 
> handing off to CM1 or CM2).  While the gateways are not unique to the issue, 
> they are running H323.
>  
> If the phones are both registered to CM3, they can call each other, but not 
> phones registered to CM1 or CM2.
>  
> I have had my network team verify there is not anything they can see in the 
> network causing this behavior. Database replication checks out OK and I can 
> ping from/to each node.
>  
> Anyone able to point me in the right direction to figure this out?
>  
> Thanks.
> ___
> 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] CUCM call set up issue after migration

2021-01-12 Thread Ryan Huff 
This would be discovered in the “utils diagnose test” however, I have seen on 
more than one occasion, in a “node-move-IP-change” situation, where either the 
reverse DNS entry didn’t get changed, or more scrupulously, the incorrect one 
exists along with the correct one.

-Ryan

On Jan 12, 2021, at 16:55, Wes Sisk (wsisk) via cisco-voip 
 wrote:

 On UCM cli ‘utils diagnose test’ to ensure things look mostly okay from OS 
and low level perspective.

After that in UCMadmin ensure system->server shows the correct IP/name for each 
server.

After that ensure ccm process restarted (or whole server rebooted). Based on 
your description SDL links on tcp:8002 are not coming up because remote name/ip 
is not recognized against what is the the database and hosts file for name 
resolution.

-w

On Jan 12, 2021, at 4:05 PM, Riley, Sean 
mailto:sri...@robinsonbradshaw.com>> wrote:

This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
involved changing the IP address on these 2 CUCM nodes.  These 2 nodes consist 
of the Publisher and 1 Subscriber.  We have another Sub at a remote datacenter 
that was not touched this past weekend.

Node configuration:

DC A
CM1: Pub which was re-ip’d
CM2: Sub which was re-ip’d

DC B:
CM3: Sub at remote site that was not changed

Phones are at many sites, but issue is independent of the phone type, phone 
location or subnet.  Also, Expressway phones have the same issue.

The issue is any phone that is registered to CM3 cannot call phones registered 
to CM1 or CM2 and vice versa.  The phones do not see the call coming in.  If 
SNR is configured, the call will ring to the remote destination. Phones 
registered to CM3 can make outbound PSTN calls without issue, but not receive 
inbound from PSTN (probably because the gateway is handing off to CM1 or CM2).  
While the gateways are not unique to the issue, they are running H323.

If the phones are both registered to CM3, they can call each other, but not 
phones registered to CM1 or CM2.

I have had my network team verify there is not anything they can see in the 
network causing this behavior. Database replication checks out OK and I can 
ping from/to each node.

Anyone able to point me in the right direction to figure this out?

Thanks.
___
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] CUCM call set up issue after migration

2021-01-12 Thread Wes Sisk (wsisk) via cisco-voip 
On UCM cli ‘utils diagnose test’ to ensure things look mostly okay from OS and 
low level perspective.

After that in UCMadmin ensure system->server shows the correct IP/name for each 
server.

After that ensure ccm process restarted (or whole server rebooted). Based on 
your description SDL links on tcp:8002 are not coming up because remote name/ip 
is not recognized against what is the the database and hosts file for name 
resolution.

-w

On Jan 12, 2021, at 4:05 PM, Riley, Sean 
mailto:sri...@robinsonbradshaw.com>> wrote:

This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
involved changing the IP address on these 2 CUCM nodes.  These 2 nodes consist 
of the Publisher and 1 Subscriber.  We have another Sub at a remote datacenter 
that was not touched this past weekend.

Node configuration:

DC A
CM1: Pub which was re-ip’d
CM2: Sub which was re-ip’d

DC B:
CM3: Sub at remote site that was not changed

Phones are at many sites, but issue is independent of the phone type, phone 
location or subnet.  Also, Expressway phones have the same issue.

The issue is any phone that is registered to CM3 cannot call phones registered 
to CM1 or CM2 and vice versa.  The phones do not see the call coming in.  If 
SNR is configured, the call will ring to the remote destination. Phones 
registered to CM3 can make outbound PSTN calls without issue, but not receive 
inbound from PSTN (probably because the gateway is handing off to CM1 or CM2).  
While the gateways are not unique to the issue, they are running H323.

If the phones are both registered to CM3, they can call each other, but not 
phones registered to CM1 or CM2.

I have had my network team verify there is not anything they can see in the 
network causing this behavior. Database replication checks out OK and I can 
ping from/to each node.

Anyone able to point me in the right direction to figure this out?

Thanks.
___
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] CUCM call set up issue after migration

2021-01-12 Thread Riley, Sean 
Thanks for the quick reply.  I have a change request to restart the node that 
did not move tonight.  I will follow up to let you know if this helped.

From: Kent Roberts 
Sent: Tuesday, January 12, 2021 4:42 PM
To: Riley, Sean 
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] CUCM call set up issue after migration

Ah split brains. Gotta love it.   Did you restart the ones that did not move?   
 I have seen this when things go stupid. The sync usually isn’t the problem 
it’s the real-time communication between the nodes that’s all messed up. 
Usually can fix with a node reboot or restarting the cucm and cti services.   
Course their maybe more to it but if things are in sync  should not be hard to 
fix

Kent


On Jan 12, 2021, at 14:06, Riley, Sean 
mailto:sri...@robinsonbradshaw.com>> wrote:

This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
involved changing the IP address on these 2 CUCM nodes.  These 2 nodes consist 
of the Publisher and 1 Subscriber.  We have another Sub at a remote datacenter 
that was not touched this past weekend.

Node configuration:

DC A
CM1: Pub which was re-ip’d
CM2: Sub which was re-ip’d

DC B:
CM3: Sub at remote site that was not changed

Phones are at many sites, but issue is independent of the phone type, phone 
location or subnet.  Also, Expressway phones have the same issue.

The issue is any phone that is registered to CM3 cannot call phones registered 
to CM1 or CM2 and vice versa.  The phones do not see the call coming in.  If 
SNR is configured, the call will ring to the remote destination. Phones 
registered to CM3 can make outbound PSTN calls without issue, but not receive 
inbound from PSTN (probably because the gateway is handing off to CM1 or CM2).  
While the gateways are not unique to the issue, they are running H323.

If the phones are both registered to CM3, they can call each other, but not 
phones registered to CM1 or CM2.

I have had my network team verify there is not anything they can see in the 
network causing this behavior. Database replication checks out OK and I can 
ping from/to each node.

Anyone able to point me in the right direction to figure this out?

Thanks.
___
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] CUCM call set up issue after migration

2021-01-12 Thread Kent Roberts 
Ah split brains. Gotta love it.   Did you restart the ones that did not move?   
 I have seen this when things go stupid. The sync usually isn’t the problem 
it’s the real-time communication between the nodes that’s all messed up. 
Usually can fix with a node reboot or restarting the cucm and cti services.   
Course their maybe more to it but if things are in sync  should not be hard to 
fix


Kent

> On Jan 12, 2021, at 14:06, Riley, Sean  wrote:
> 
> This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
> involved changing the IP address on these 2 CUCM nodes.  These 2 nodes 
> consist of the Publisher and 1 Subscriber.  We have another Sub at a remote 
> datacenter that was not touched this past weekend.
>  
> Node configuration:
>  
> DC A
> CM1: Pub which was re-ip’d
> CM2: Sub which was re-ip’d
>  
> DC B:
> CM3: Sub at remote site that was not changed
>  
> Phones are at many sites, but issue is independent of the phone type, phone 
> location or subnet.  Also, Expressway phones have the same issue.
>  
> The issue is any phone that is registered to CM3 cannot call phones 
> registered to CM1 or CM2 and vice versa.  The phones do not see the call 
> coming in.  If SNR is configured, the call will ring to the remote 
> destination. Phones registered to CM3 can make outbound PSTN calls without 
> issue, but not receive inbound from PSTN (probably because the gateway is 
> handing off to CM1 or CM2).  While the gateways are not unique to the issue, 
> they are running H323.
>  
> If the phones are both registered to CM3, they can call each other, but not 
> phones registered to CM1 or CM2.
>  
> I have had my network team verify there is not anything they can see in the 
> network causing this behavior. Database replication checks out OK and I can 
> ping from/to each node.
>  
> Anyone able to point me in the right direction to figure this out?
>  
> Thanks.
> ___
> 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] CUCM call set up issue after migration

2021-01-12 Thread Riley, Sean 
This past weekend we migrated 2 CUCM servers to a new datacenter.  This 
involved changing the IP address on these 2 CUCM nodes.  These 2 nodes consist 
of the Publisher and 1 Subscriber.  We have another Sub at a remote datacenter 
that was not touched this past weekend.

Node configuration:

DC A
CM1: Pub which was re-ip'd
CM2: Sub which was re-ip'd

DC B:
CM3: Sub at remote site that was not changed

Phones are at many sites, but issue is independent of the phone type, phone 
location or subnet.  Also, Expressway phones have the same issue.

The issue is any phone that is registered to CM3 cannot call phones registered 
to CM1 or CM2 and vice versa.  The phones do not see the call coming in.  If 
SNR is configured, the call will ring to the remote destination. Phones 
registered to CM3 can make outbound PSTN calls without issue, but not receive 
inbound from PSTN (probably because the gateway is handing off to CM1 or CM2).  
While the gateways are not unique to the issue, they are running H323.

If the phones are both registered to CM3, they can call each other, but not 
phones registered to CM1 or CM2.

I have had my network team verify there is not anything they can see in the 
network causing this behavior. Database replication checks out OK and I can 
ping from/to each node.

Anyone able to point me in the right direction to figure this out?

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

Re: [cisco-voip] Alternatives for MediaSense simple recording?

2021-01-12 Thread Brian V 
I believe the SOX utility has a windows and MAC-OS version as well.  You
can just run it from the CLI
http://sox.sourceforge.net/
I use a text to speech program called Balabolka that utilizes it on Windows
to convert sound files to G711.
I use this app for UCCX prompts during testing. Keeps my voice off the
customers server.  :)
http://balabolka.site/balabolka.htm



On Tue, Jan 12, 2021 at 9:22 AM Nick Barnett  wrote:

> That PLAR idea is fun :)
>
> 2 audio files at once is not ideal...
>
> I haven't tested this yet, but this is where I'm going. Looking at
> possibly turning this into a container to post audio files to and get back
> a muxed Left / Right "stereo" conversation.
>
> https://securitronlinux.com/debian-testing/merge-left-and-right-audio-tracks-into-a-stereo-file-with-sox-on-linux/
>
> Now I just need to figure out how long a recorded call can be... I guess I
> hadn't thought of that part as either a requirement or request...
>
>
> On Mon, Jan 11, 2021, at 9:52 PM, Lelio Fulgenzi wrote:
>
>
> I wonder if a PLAR on a DN that is listed as an alternate extension would
> help.
>
> So,
>
> Tap PLAR
> Then merge calls
>
> You could even move the merge Soft key earlier?
>
>
> Sent from my iPhone
>
> On Jan 11, 2021, at 9:53 PM, Kent Roberts  wrote:
>
> 
>
>
> *CAUTION:* This email originated from outside of the University of
> Guelph. Do not click links or open attachments unless you recognize the
> sender and know the content is safe. If in doubt, forward suspicious emails
> to ith...@uoguelph.ca
>
>
> My guess is it won’t get fixed as it would help us all out! LOL.
>
>
> On Jan 11, 2021, at 2:18 PM, NateCCIE  wrote:
>
> There is a record softkey that does what you’re asking Leilo.  The problem
> with Unity Live record is the CUCM BIB calls the number twice, one for TX
> and one for RX, and you get two-one sided voicemails in the inbox.  If that
> gets fixed, it’s an amazing option.
>
> *From:* cisco-voip  *On Behalf Of *Lelio
> Fulgenzi
> *Sent:* Monday, January 11, 2021 2:00 PM
> *To:* Nick Barnett ; Brian Meade 
> *Cc:* cisco-voip 
> *Subject:* Re: [cisco-voip] Alternatives for MediaSense simple recording?
>
> It’s too bad that CUCM doesn’t have a LiveRecord softkey macro that does
> the conferencing and dialing of the live record extension.
>
> To ask people to press conference and then dial live record and the
> conference again, is just way to much to ask. I think.
>
> Has Live Record support from CUCM side improved at all?
>
>
> *From:* Nick Barnett 
> *Sent:* Monday, January 11, 2021 3:50 PM
> *To:* Brian Meade ; Lelio Fulgenzi 
> *Cc:* cisco-voip 
> *Subject:* Re: [cisco-voip] Alternatives for MediaSense simple recording?
>
> *CAUTION:* This email originated from outside of the University of
> Guelph. Do not click links or open attachments unless you recognize the
> sender and know the content is safe. If in doubt, forward suspicious emails
> to ith...@uoguelph.ca
>
> Unity live record, that's one I haven't thought of yet. Thanks!
>
> I'm pretty sure, mediasense is totally dead. We just upgraded to CUCM 12.5
> SU3 in October. MediaSense 11.5 su2 said it was compatible with CUCM 12.x,
> but in this case, it only meant 12.x THRU 12.5 SU2.  The BU's solution was
> to downgrade to SU2. We kind of pushed them and they came back with a fix.
> Apparently between CUCM 12.5 SU2 and 12.5 SU3, CUCM forced HTTPs for AXL
> connections.  to fix it, TAC had to root into my nodes and make a change to
> the haproxy.conf file to stop forcing HTTPS.
>
> This whole mess took me right up to the last day of support and I think
> everyone at cisco hated me, but they were clear there would be no more
> support for this monster. meh
>
> Thanks,
> Nick
>
> On Mon, Jan 11, 2021, at 2:24 PM, Brian Meade wrote:
>
> Unity Connection Live Record may be an option you could try and have it
> conference in that number.
>
> I think MediaSense is still around for video call handlers/video
> voicemail/video on hold if I remember correctly.  I think they only killed
> it for recording calls.
>
> On Mon, Jan 11, 2021 at 1:56 PM Lelio Fulgenzi  wrote:
>
> I sure was sad when they EOL’ed Media Sense. I really wanted to do video
> call handlers and video voicemail and greetings.
>
>
>
> Take a look at https://www.mns.vc/ they might have what you’re looking
> for.
>
>
>
> Lelio
>
>
>
>
> *From:* cisco-voip  *On Behalf Of *Nick
> Barnett
> *Sent:* Monday, January 11, 2021 12:54 PM
> *To:* cisco-voip 
> *Subject:* [cisco-voip] Alternatives for MediaSense simple recording?
>
>
>
> *CAUTION:* This email originated from outside of the University of
> Guelph. Do not click links or open attachments unless you recognize the
> sender and know the content is safe. If in doubt, forward suspicious emails
> to ith...@uoguelph.ca
>
>
>
> Hey folks. What are people using now that MediaSense is EOL? It was fine
> for what it was. It just recorded anything you threw into it. it weaseled
> it's way into some weird apps we have, and now I'm

Re: [cisco-voip] Alternatives for MediaSense simple recording?

2021-01-12 Thread Nick Barnett 
That PLAR idea is fun :)

2 audio files at once is not ideal...

I haven't tested this yet, but this is where I'm going. Looking at possibly 
turning this into a container to post audio files to and get back a muxed Left 
/ Right "stereo" conversation.
https://securitronlinux.com/debian-testing/merge-left-and-right-audio-tracks-into-a-stereo-file-with-sox-on-linux/

Now I just need to figure out how long a recorded call can be... I guess I 
hadn't thought of that part as either a requirement or request...


On Mon, Jan 11, 2021, at 9:52 PM, Lelio Fulgenzi wrote:
> 
> I wonder if a PLAR on a DN that is listed as an alternate extension would 
> help.  
> 
> So, 
> 
> Tap PLAR
> Then merge calls
> 
> You could even move the merge Soft key earlier?
> 
> 
> Sent from my iPhone
> 
>> On Jan 11, 2021, at 9:53 PM, Kent Roberts  wrote:
>> 
>>  
>> 

>> *CAUTION:* This email originated from outside of the University of Guelph. 
>> Do not click links or open attachments unless you recognize the sender and 
>> know the content is safe. If in doubt, forward suspicious emails to 
>> ith...@uoguelph.ca
>> 
>> 

>> My guess is it won’t get fixed as it would help us all out! LOL. 
>> 
>> 
>>> On Jan 11, 2021, at 2:18 PM, NateCCIE  wrote:
>>> 
>>> There is a record softkey that does what you’re asking Leilo.  The problem 
>>> with Unity Live record is the CUCM BIB calls the number twice, one for TX 
>>> and one for RX, and you get two-one sided voicemails in the inbox.  If that 
>>> gets fixed, it’s an amazing option.
>>>  
>>> *From:* cisco-voip  *On Behalf Of 
>>> *Lelio Fulgenzi
>>> *Sent:* Monday, January 11, 2021 2:00 PM
>>> *To:* Nick Barnett ; Brian Meade 
>>> *Cc:* cisco-voip 
>>> *Subject:* Re: [cisco-voip] Alternatives for MediaSense simple recording?
>>>  
>>> It’s too bad that CUCM doesn’t have a LiveRecord softkey macro that does 
>>> the conferencing and dialing of the live record extension.
>>>  
>>> To ask people to press conference and then dial live record and the 
>>> conference again, is just way to much to ask. I think.
>>>  
>>> Has Live Record support from CUCM side improved at all?
>>>  
>>>  
>>> *From:* Nick Barnett  
>>> *Sent:* Monday, January 11, 2021 3:50 PM
>>> *To:* Brian Meade ; Lelio Fulgenzi 
>>> *Cc:* cisco-voip 
>>> *Subject:* Re: [cisco-voip] Alternatives for MediaSense simple recording?
>>>  
>>> *CAUTION:* This email originated from outside of the University of Guelph. 
>>> Do not click links or open attachments unless you recognize the sender and 
>>> know the content is safe. If in doubt, forward suspicious emails to 
>>> ith...@uoguelph.ca
>>>  
>>> Unity live record, that's one I haven't thought of yet. Thanks!
>>>  
>>> I'm pretty sure, mediasense is totally dead. We just upgraded to CUCM 12.5 
>>> SU3 in October. MediaSense 11.5 su2 said it was compatible with CUCM 12.x, 
>>> but in this case, it only meant 12.x THRU 12.5 SU2.  The BU's solution was 
>>> to downgrade to SU2. We kind of pushed them and they came back with a fix. 
>>> Apparently between CUCM 12.5 SU2 and 12.5 SU3, CUCM forced HTTPs for AXL 
>>> connections.  to fix it, TAC had to root into my nodes and make a change to 
>>> the haproxy.conf file to stop forcing HTTPS.
>>>  
>>> This whole mess took me right up to the last day of support and I think 
>>> everyone at cisco hated me, but they were clear there would be no more 
>>> support for this monster. meh
>>>  
>>> Thanks,
>>> Nick
>>>  
>>> On Mon, Jan 11, 2021, at 2:24 PM, Brian Meade wrote:
 Unity Connection Live Record may be an option you could try and have it 
 conference in that number.
  
 I think MediaSense is still around for video call handlers/video 
 voicemail/video on hold if I remember correctly.  I think they only killed 
 it for recording calls.
  
 On Mon, Jan 11, 2021 at 1:56 PM Lelio Fulgenzi  wrote:
> I sure was sad when they EOL’ed Media Sense. I really wanted to do video 
> call handlers and video voicemail and greetings. 

>  

> Take a look at https://www.mns.vc/ they might have what you’re looking 
> for.

>  

> Lelio

>  

>  

> *From:* cisco-voip  *On Behalf Of 
> *Nick Barnett
> *Sent:* Monday, January 11, 2021 12:54 PM
> *To:* cisco-voip 
> *Subject:* [cisco-voip] Alternatives for MediaSense simple recording?
>  

> *CAUTION:* This email originated from outside of the University of 
> Guelph. Do not click links or open attachments unless you recognize the 
> sender and know the content is safe. If in doubt, forward suspicious 
> emails to ith...@uoguelph.ca

>  

> Hey folks. What are people using now that MediaSense is EOL? It was fine 
> for what it was. It just recorded anything you threw into it. it weaseled 
> it's way into some weird apps we have, and now I'm kinda stuck.  We have 
> an iphone app that was developed to work in areas with poor data 
> connectivity. It creates a conference