Re: [cisco-voip] 8800 Series firmware upgrade 12.0(1) text color

2017-12-13 Thread NateCCIE
The firmware has a feature to detect if the background is dark or light, and 
then adjust the labels as needed. But it has to be really dark to be dark. For 
the majority of picture. 

Sent from my iPhone

> On Dec 13, 2017, at 7:50 PM, Haas, Neal  wrote:
> 
> I wanted to push the new 12.0(1) firmware to our 8851/8861 phones. I did a 
> test and you cannot even see the line text on dark backgrounds, which is 90% 
> of the images . Anyone know how to fix line text color? The only image that 
> really works is the one that looks like someone socked the phone.
> 
> Neal
> 
> 
> ___
> 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] 8800 Series firmware upgrade 12.0(1) text color

2017-12-13 Thread Bill Talley
Nothing aside from the changes in color to the text and to the toast pop up.  
Toast was orange, now it’s white.  Opinions vary on that one though.

Sent from a mobile device with very tiny touchscreen input keys. Please excude 
my typtos.

> On Dec 13, 2017, at 9:23 PM, Haas, Neal  wrote:
> 
> I want to do that but we are hitting the answer/hold bug.
> 
> 
> I think my solution is to create a background image that doesn't look as bad 
> as the default cisco one.
> 
> 
> any other issues that you have seen with 12.0(1)?
> 
> 
> Neal Haas
> ITSD Analyst - Communications
> 559-600-5890
> 
> From: Bill Talley 
> Sent: Wednesday, December 13, 2017 7:12:32 PM
> To: Haas, Neal
> Cc: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] 8800 Series firmware upgrade 12.0(1) text color
> 
> We have the same issue and have been unable to find a fix short of reverting 
> to 11.7 firmware.
> 
> Sent from a mobile device with very tiny touchscreen input keys. Please 
> excude my typtos.
> 
>> On Dec 13, 2017, at 8:50 PM, Haas, Neal  wrote:
>> 
>> I wanted to push the new 12.0(1) firmware to our 8851/8861 phones. I did a 
>> test and you cannot even see the line text on dark backgrounds, which is 90% 
>> of the images . Anyone know how to fix line text color? The only image that 
>> really works is the one that looks like someone socked the phone.
>> 
>> Neal
>> 
>> 
>> ___
>> cisco-voip mailing list
>> cisco-voip@puck.nether.net
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cnhaas%40co.fresno.ca.us%7C4ea6d99a6fe8452e47e908d542a085e1%7C3ccce0182cd74123960d6cc1d47e3550%7C1%7C0%7C636488179563323057=u3FGVkFEzfnMyYC0YLOSH0QysgUKE2ihabRC%2BfSwdcI%3D=0
> 
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] 8800 Series firmware upgrade 12.0(1) text color

2017-12-13 Thread Haas, Neal
I want to do that but we are hitting the answer/hold bug.


I think my solution is to create a background image that doesn't look as bad as 
the default cisco one.


any other issues that you have seen with 12.0(1)?


Neal Haas
ITSD Analyst - Communications
559-600-5890

From: Bill Talley 
Sent: Wednesday, December 13, 2017 7:12:32 PM
To: Haas, Neal
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] 8800 Series firmware upgrade 12.0(1) text color

We have the same issue and have been unable to find a fix short of reverting to 
11.7 firmware.

Sent from a mobile device with very tiny touchscreen input keys. Please excude 
my typtos.

> On Dec 13, 2017, at 8:50 PM, Haas, Neal  wrote:
>
> I wanted to push the new 12.0(1) firmware to our 8851/8861 phones. I did a 
> test and you cannot even see the line text on dark backgrounds, which is 90% 
> of the images . Anyone know how to fix line text color? The only image that 
> really works is the one that looks like someone socked the phone.
>
> Neal
>
> 
> ___
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip=02%7C01%7Cnhaas%40co.fresno.ca.us%7C4ea6d99a6fe8452e47e908d542a085e1%7C3ccce0182cd74123960d6cc1d47e3550%7C1%7C0%7C636488179563323057=u3FGVkFEzfnMyYC0YLOSH0QysgUKE2ihabRC%2BfSwdcI%3D=0
<>___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] 8800 Series firmware upgrade 12.0(1) text color

2017-12-13 Thread Bill Talley
We have the same issue and have been unable to find a fix short of reverting to 
11.7 firmware.  

Sent from a mobile device with very tiny touchscreen input keys. Please excude 
my typtos.

> On Dec 13, 2017, at 8:50 PM, Haas, Neal  wrote:
> 
> I wanted to push the new 12.0(1) firmware to our 8851/8861 phones. I did a 
> test and you cannot even see the line text on dark backgrounds, which is 90% 
> of the images . Anyone know how to fix line text color? The only image that 
> really works is the one that looks like someone socked the phone.
> 
> Neal
> 
> 
> ___
> 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] Duplicate ipaddress space and vlans on separate vSwitches on same ESXi host

2017-12-13 Thread Lelio Fulgenzi
Yeah – that was a question I did have. Whether or not it would get confused 
with the same VLAN tagging but to different switches.

But I would suspect that it would still keep the traffic separate since they 
are separate switches.

I might open a TAC case for this one. I don’t like doing that for technical 
design issues, but I might not have any other avenue to confirm.

Other than try. 

From: michael.p.k...@gmail.com [mailto:michael.p.k...@gmail.com] On Behalf Of 
Mike King
Sent: Wednesday, December 13, 2017 2:27 PM
To: Lelio Fulgenzi 
Cc: cisco-voip voyp list 
Subject: Re: [cisco-voip] Duplicate ipaddress space and vlans on separate 
vSwitches on same ESXi host

Lelio,

Yes with a caveat.

You have to ensure that you don't cross pollinate  (Allow both VLANs to see 
each other).  But yes, this is pretty standard stuff.

I don't think you can do Trunking on in VMware if your trying to do this.  
(Carry multiple VLANs) since I think VMware will get confused which NIC has 
which VLAN.

This was via a google search, but it should give you the idea

[Inline image 1]

On Thu, Dec 7, 2017 at 9:40 PM, Lelio Fulgenzi 
> wrote:

Just following up on a conversation about online/offline networks and making 
things work on an esxi host.

I've now had a bit more experience with virtual environments, and as far as I 
can tell, there should be no issue creating a second (or third) vSwitch, 
assigning it vmnics connected to the offline network and building networks with 
the same VLAN information carried over the offline trunk that is carried over 
the production trunk.

Guests would be assigned to one vswitch or the other. Not both.

Have I got it all wrong?

Sent from my iPad
___
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] Teradici Zero Client packet loss when connected through Phones

2017-12-13 Thread Ryan Ratliff (rratliff)
Two things I can think of to investigate.
1. EEE settings on the phones (especially if they are on old software). This 
caused tons of problems with PCs a while back and may be coming into play here.
2. Automatic Port Synchronization - This setting forces the PC port to the same 
speed as the Switch port, so if your switch is 1000/Full and the Zero client 
doesn’t agree this could cause issues.

Given Mike’s reply about forcing them to 100/Full I’m guessing the 2nd setting 
could be coming into play.

-Ryan

On Dec 13, 2017, at 2:20 PM, Mike King 
> wrote:

We have some Teradici Zero Clients, and began to have issues with them last 
year.   We ended up hard coding them to 100/Full, and our issues went away.

We did have a different use case, as we were having the zero clients at the end 
of runs, not plugged into a device with what has to be less than a 14 foot 
cord.  So I don't know.  We were attributing it to some kind of attenuation on 
the cable plant (We didn't own the cable plant, nor did we have test results of 
it), and dropping to 100/Full cleared it up so we stopped investigating.   We 
only had about 5 of the devices, and they are extremely static, so it wasn't 
worth the effort to investigate further.

On Tue, Dec 12, 2017 at 10:54 PM, Nathan Reeves 
> wrote:
Interested to know if anyone's seen issues when connecting Teradici Zero 
Clients through the switchport on Cisco Phones.  In this case 8845 and 7841 
phones.

Customer is moving to CUCM and has an established base of Zero Clients.  
They're starting to see packet loss reported on their clients only when 
connected to the network via the phones.  Not previously noted packet loss with 
their previous IP Phone (Siemens).

Anyone know of any best practices / issues with this setup?

Thanks

Nathan

___
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] Teradici Zero Client packet loss when connected through Phones

2017-12-13 Thread Mike King
We have some Teradici Zero Clients, and began to have issues with them last
year.   We ended up hard coding them to 100/Full, and our issues went away.

We did have a different use case, as we were having the zero clients at the
end of runs, not plugged into a device with what has to be less than a 14
foot cord.  So I don't know.  We were attributing it to some kind of
attenuation on the cable plant (We didn't own the cable plant, nor did we
have test results of it), and dropping to 100/Full cleared it up so we
stopped investigating.   We only had about 5 of the devices, and they are
extremely static, so it wasn't worth the effort to investigate further.

On Tue, Dec 12, 2017 at 10:54 PM, Nathan Reeves 
wrote:

> Interested to know if anyone's seen issues when connecting Teradici Zero
> Clients through the switchport on Cisco Phones.  In this case 8845 and 7841
> phones.
>
> Customer is moving to CUCM and has an established base of Zero Clients.
> They're starting to see packet loss reported on their clients only when
> connected to the network via the phones.  Not previously noted packet loss
> with their previous IP Phone (Siemens).
>
> Anyone know of any best practices / issues with this setup?
>
> Thanks
>
> Nathan
>
> ___
> 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] AnyConnect Wireless and Jabber Voice

2017-12-13 Thread Ryan Huff
Time for wire captures I’d say.

Compare headers with and without AnyConnect. Do the markings change? Is there 
excessive broadcast traffic hitting the NIC when using AnyConnect? ... etc.

TAC will want that anyway so getting traces setup won’t be a wasted effort. 
Outside of that, you’re just going to be stabbing in the dark hoping to hit 
something :).

-Ryan

On Dec 13, 2017, at 12:30 PM, Casper, Steven 
> wrote:

Hi Ryan,

Thanks for responding. Running Cisco Jabber 11.8.3. We are only using 
AnyConnect NAM as a supplicant for 802.1x/ ISE. Not using for  VPN at all. This 
is happening internally on site connected to our Cisco wireless environment 
that uses 3602/3702 APs and 5508 WLCs. I know it is crazy but it seems directly 
related to us installing AnyConnect.

Steve

From: Ryan Huff [mailto:ryanh...@outlook.com]
Sent: Wednesday, December 13, 2017 12:05 PM
To: Casper, Steven
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] AnyConnect Wireless and Jabber Voice

Sounds like jitter  usually QoS related.


Spitballing here cause I don’t know your topology but it sounds like the 
traffic is getting marked best effort when traversing the VPN connection.


If you can illustrate the Jabber client’s connection path (and type of Jabber 
client), I might be able to help a little more.


Is this an on-prem Jabber install? Always a good idea to run through this guide 
as well for on-perm installs: 
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_010001.html

Sent from my iPhone

On Dec 13, 2017, at 11:45 AM, Casper, Steven via cisco-voip 
> wrote:
We have installed AnyConnect 4.5 and have started to have issues with Jabber 
calls using wireless.  Every minute outbound voice becomes garbled for several 
seconds  Running a continuous ping from a PC to the wireless default gateway we 
jump from 2ms to 160+ms every minute that corresponds to the garbed voice. 
Opening a TAC case but curious if anyone else has seen this behavior. This does 
not occur on a device without AnyConnect and if you uninstall the software  
everything  works fine. This also does occur when connected wired using 
AnyConnect.

Steve




This email may contain privileged and/or confidential information that is 
intended solely for the use of the addressee.  If you are not the intended 
recipient or entity, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the transmission.  If 
you received this communication in error, please contact the sender immediately 
and destroy the material in its entirety, whether electronic or hard copy.  
This communication may contain nonpublic personal information about consumers 
subject to the restrictions of the Gramm-Leach-Bliley Act and the 
Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such 
information for any purpose other than to provide the services for which you 
are receiving the information.
There are risks associated with the use of electronic transmission.  The sender 
of this information does not control the method of transmittal or service 
providers and assumes no duty or obligation for the security, receipt, or third 
party interception of this transmission.

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


This email may contain privileged and/or confidential information that is 
intended solely for the use of the addressee.  If you are not the intended 
recipient or entity, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the transmission.  If 
you received this communication in error, please contact the sender immediately 
and destroy the material in its entirety, whether electronic 

Re: [cisco-voip] FXO hang due to connectivity loss?

2017-12-13 Thread Norton, Mike
Are you sure that the gateway is properly detecting the tone and hanging up 
when connectivity *is* working? FXO disconnect is terribly hit-and-miss even at 
the best of times. Disconnect supervision on FXO is more of a best-effort 
attempt than an actual thing.

If the disconnect signal is properly interpreted by the gateway then like you I 
would expect the gateway to end that leg of the call regardless of SIP 
reachability. But I consider that a pretty big if!

-mn

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of Ki Wi
Sent: December 13, 2017 12:34 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] FXO hang due to connectivity loss?

Hi Folks,
If the voice gateway is defined with disconnect tone/ cadence,etc. Should a 
loss of connectivity (SIP signaling between VG and CUCM) cause the FXO port not 
to hang up ?

To me , SIP is peer to peer signaling. It should not affect the voice gateway 
decision for going on-hook when a disconnect tone is detected even there is a 
loss of connectivity to CUCM.
--
Regards,
Ki Wi
___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip


Re: [cisco-voip] AnyConnect Wireless and Jabber Voice

2017-12-13 Thread Casper, Steven via cisco-voip
Hi Ryan,

Thanks for responding. Running Cisco Jabber 11.8.3. We are only using 
AnyConnect NAM as a supplicant for 802.1x/ ISE. Not using for  VPN at all. This 
is happening internally on site connected to our Cisco wireless environment 
that uses 3602/3702 APs and 5508 WLCs. I know it is crazy but it seems directly 
related to us installing AnyConnect.

Steve

From: Ryan Huff [mailto:ryanh...@outlook.com]
Sent: Wednesday, December 13, 2017 12:05 PM
To: Casper, Steven
Cc: cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] AnyConnect Wireless and Jabber Voice

Sounds like jitter  usually QoS related.


Spitballing here cause I don’t know your topology but it sounds like the 
traffic is getting marked best effort when traversing the VPN connection.


If you can illustrate the Jabber client’s connection path (and type of Jabber 
client), I might be able to help a little more.


Is this an on-prem Jabber install? Always a good idea to run through this guide 
as well for on-perm installs: 
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_010001.html

Sent from my iPhone

On Dec 13, 2017, at 11:45 AM, Casper, Steven via cisco-voip 
> wrote:
We have installed AnyConnect 4.5 and have started to have issues with Jabber 
calls using wireless.  Every minute outbound voice becomes garbled for several 
seconds  Running a continuous ping from a PC to the wireless default gateway we 
jump from 2ms to 160+ms every minute that corresponds to the garbed voice. 
Opening a TAC case but curious if anyone else has seen this behavior. This does 
not occur on a device without AnyConnect and if you uninstall the software  
everything  works fine. This also does occur when connected wired using 
AnyConnect.

Steve




This email may contain privileged and/or confidential information that is 
intended solely for the use of the addressee.  If you are not the intended 
recipient or entity, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the transmission.  If 
you received this communication in error, please contact the sender immediately 
and destroy the material in its entirety, whether electronic or hard copy.  
This communication may contain nonpublic personal information about consumers 
subject to the restrictions of the Gramm-Leach-Bliley Act and the 
Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such 
information for any purpose other than to provide the services for which you 
are receiving the information.
There are risks associated with the use of electronic transmission.  The sender 
of this information does not control the method of transmittal or service 
providers and assumes no duty or obligation for the security, receipt, or third 
party interception of this transmission.

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

This email may contain privileged and/or confidential information that is 
intended solely for the use of the addressee.  If you are not the intended 
recipient or entity, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the transmission.  If 
you received this communication in error, please contact the sender immediately 
and destroy the material in its entirety, whether electronic or hard copy.  
This communication may contain nonpublic personal information about consumers 
subject to the restrictions of the Gramm-Leach-Bliley Act and the 
Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such 
information for any purpose other than to provide the services for which you 
are receiving the information.
There are risks associated with the use of electronic transmission.  The sender 
of this information does not control the method of transmittal or 

Re: [cisco-voip] AnyConnect Wireless and Jabber Voice

2017-12-13 Thread Ryan Huff
Sounds like jitter  usually QoS related.

Spitballing here cause I don’t know your topology but it sounds like the 
traffic is getting marked best effort when traversing the VPN connection.

If you can illustrate the Jabber client’s connection path (and type of Jabber 
client), I might be able to help a little more.

Is this an on-prem Jabber install? Always a good idea to run through this guide 
as well for on-perm installs: 
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115/CJAB_BK_D00D8CBD_00_deployment-installation-guide-cisco-jabber115_chapter_010001.html

Sent from my iPhone

On Dec 13, 2017, at 11:45 AM, Casper, Steven via cisco-voip 
> wrote:

We have installed AnyConnect 4.5 and have started to have issues with Jabber 
calls using wireless.  Every minute outbound voice becomes garbled for several 
seconds  Running a continuous ping from a PC to the wireless default gateway we 
jump from 2ms to 160+ms every minute that corresponds to the garbed voice. 
Opening a TAC case but curious if anyone else has seen this behavior. This does 
not occur on a device without AnyConnect and if you uninstall the software  
everything  works fine. This also does occur when connected wired using 
AnyConnect.

Steve




This email may contain privileged and/or confidential information that is 
intended solely for the use of the addressee.  If you are not the intended 
recipient or entity, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the transmission.  If 
you received this communication in error, please contact the sender immediately 
and destroy the material in its entirety, whether electronic or hard copy.  
This communication may contain nonpublic personal information about consumers 
subject to the restrictions of the Gramm-Leach-Bliley Act and the 
Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such 
information for any purpose other than to provide the services for which you 
are receiving the information.
There are risks associated with the use of electronic transmission.  The sender 
of this information does not control the method of transmittal or service 
providers and assumes no duty or obligation for the security, receipt, or third 
party interception of this transmission.


___
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] AnyConnect Wireless and Jabber Voice

2017-12-13 Thread Casper, Steven via cisco-voip
We have installed AnyConnect 4.5 and have started to have issues with Jabber 
calls using wireless.  Every minute outbound voice becomes garbled for several 
seconds  Running a continuous ping from a PC to the wireless default gateway we 
jump from 2ms to 160+ms every minute that corresponds to the garbed voice. 
Opening a TAC case but curious if anyone else has seen this behavior. This does 
not occur on a device without AnyConnect and if you uninstall the software  
everything  works fine. This also does occur when connected wired using 
AnyConnect.

Steve



This email may contain privileged and/or confidential information that is 
intended solely for the use of the addressee.  If you are not the intended 
recipient or entity, you are strictly prohibited from disclosing, copying, 
distributing or using any of the information contained in the transmission.  If 
you received this communication in error, please contact the sender immediately 
and destroy the material in its entirety, whether electronic or hard copy.  
This communication may contain nonpublic personal information about consumers 
subject to the restrictions of the Gramm-Leach-Bliley Act and the 
Sarbanes-Oxley Act.  You may not directly or indirectly reuse or disclose such 
information for any purpose other than to provide the services for which you 
are receiving the information.
There are risks associated with the use of electronic transmission.  The sender 
of this information does not control the method of transmittal or service 
providers and assumes no duty or obligation for the security, receipt, or third 
party interception of this transmission.

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


Re: [cisco-voip] CUCM Trunk timer

2017-12-13 Thread Jason Aarons (Americas)
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuj19006


From: Erick Bergquist [mailto:erick...@gmail.com]
Sent: Wednesday, December 6, 2017 2:25 AM
To: Jason Aarons (Americas) 
Cc: cisco-voip (cisco-voip@puck.nether.net) 
Subject: Re: [cisco-voip] CUCM Trunk timer


It’s 0 days and the same hours and minutes right?

It’s been like that for awhile as far as I recall next to the trunk 
destination. Likely a cosmetic item.

I usually have only one destination per trunk and use route groups to order how 
they are used.

Erick


On Tue, Dec 5, 2017 at 12:56 PM Jason Aarons (Americas) 
> wrote:

On a CUCM trunk, you have the status showing the duration it’s been in service, 
then under SIP information there is another timer for the individual links.

CUCM is showing a difference in the timers.  Do you know why that is?



Jason Aarons, CCIEx2 No. 38564
Advanced Technology Consultant
Dimension Data
904-338-3245



This email and all contents are subject to the following disclaimer:
"http://www.dimensiondata.com/emaildisclaimer;
___
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] FXO hang due to connectivity loss?

2017-12-13 Thread Brian Meade
I believe it should disconnect on the FXO side but the IP Phone isn't going
to know about it due to the signaling losee.  What behavior are you
seeing?  This is also assuming the FXO side is initiating the disconnect.

On Wed, Dec 13, 2017 at 2:33 AM, Ki Wi  wrote:

> Hi Folks,
> If the voice gateway is defined with disconnect tone/ cadence,etc. Should
> a loss of connectivity (SIP signaling between VG and CUCM) cause the FXO
> port not to hang up ?
>
> To me , SIP is peer to peer signaling. It should not affect the voice
> gateway decision for going on-hook when a disconnect tone is detected even
> there is a loss of connectivity to CUCM.
> --
> Regards,
> Ki Wi
>
> ___
> 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