Send cisco-voip mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."
Today's Topics:
1. 6941 firmware SRST (abbas Wali)
2. Anyone running 8961s with UCCX 8.5.1SU3? (Jason Aarons (AM))
3. Re: Anyone running 8961s with UCCX 8.5.1SU3?
(Ryan LaFountain (rlafount))
4. Re: Anyone running 8961s with UCCX 8.5.1SU3? (Bryant Onojeta)
5. Re: 'interesting' EMCC behavior (Erick Wellnitz)
6. Re: 'interesting' EMCC behavior (Brian Meade (brmeade))
7. Re: 'interesting' EMCC behavior (Erick Wellnitz)
8. Re: 'interesting' EMCC behavior (Brian Meade (brmeade))
9. Re: 'interesting' EMCC behavior (Brian Meade (brmeade))
10. Transfer to IVR in AMD is not working properly (shary shary)
11. Unity Connection SMTP Address (Tim Smith)
12. Re: CUCM 9.x ELM and Owner ID (Tim Smith)
13. Re: 'interesting' EMCC behavior (Erick Wellnitz)
----------------------------------------------------------------------
Message: 1
Date: Tue, 8 Oct 2013 17:03:04 +0100
From: abbas Wali <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] 6941 firmware SRST
Message-ID:
<cafdhcp4ht8a7fp1x59hgo4crf7z83j44vw_02edajwimwge...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
hi all
we have 6941 with the current load of 9.1.1
only shows active and standby cucm and doesnt get registered with srst
router
will upgrade to the latest 9.3(3) work for us.
also we are on cucm 8.5 do we have to install the device pack to support
these phones.
thanks
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/4d297b62/attachment-0001.html>
------------------------------
Message: 2
Date: Tue, 8 Oct 2013 14:04:34 -0400
From: "Jason Aarons (AM)" <[email protected]>
To: "cisco-voip ([email protected])"
<[email protected]>
Subject: [cisco-voip] Anyone running 8961s with UCCX 8.5.1SU3?
Message-ID:
<4e38db0a1959b04c8c83edcf069b53ed0d3bcb3...@usispclexdb01.na.didata.local>
Content-Type: text/plain; charset="windows-1252"
Anyone running 8961s with UCCX 8.5.1SU3?
Customer indicated they setup some 8961s and after logging into CAD they get an
error;
[cid:[email protected]]
CCM 8.6.2.22900-9 and UCCX 8.5.1SU3
These are 8961s running sip8961.9-3-4-24 seems other model phone's are fine.
They've had TAC case 627583127 open for awhile.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/70682a1f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10825 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/70682a1f/attachment-0001.png>
------------------------------
Message: 3
Date: Tue, 8 Oct 2013 18:27:23 +0000
From: "Ryan LaFountain (rlafount)" <[email protected]>
To: "Jason Aarons (AM)" <[email protected]>, "cisco-voip
([email protected])" <[email protected]>
Subject: Re: [cisco-voip] Anyone running 8961s with UCCX 8.5.1SU3?
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="windows-1252"
Hi Jason,
627583127 looks to be a WAAS SR. Is there a UCCX/CUCM SR? I'll take a look.
At any rate, when the phone registers, CTI Manager should send a message to the
JTAPI client on UCCX. JTAPI will update its state machine to recognize that the
phone is now in service. At any time later, if you come along and login to CAD,
the state machine is checked. CUCM is not contacted to verify phone state upon
logging into CAD. Since you're on 8.6(2a)SU2, you're past many of the well know
CTI bugs that may cause this.
If you want to enable the JTAPI debugs (Unified CM Telephony Client) with DEBUG
in the top box and all EXCEPT MISC_DEBUGGING in the bottom box and just bounce
the phone, you can search by the device name and see if UCCX is being notified
of the phone going down and then back up. If there is nothing in the JTAPI
client logs for the device name, look into the CM/CTI Manager traces on CUCM as
there may be a disconnect between CCM and CTI services especially if the phone
is registered to another node than the primary CTI provider for UCCX.
Send me the JTAPI logs and the device name/DN and I'll take a look.
Thank you,
Ryan LaFountain
Unified Contact Center
Cisco Services
Direct: +1 919 392 9898
Email: [email protected]
Hours: M ? F 9:00am ? 5:00pm
From: "Jason Aarons (AM)"
<[email protected]<mailto:[email protected]>>
Date: Tuesday, October 8, 2013 2:04 PM
To: "cisco-voip
([email protected]<mailto:[email protected]>)"
<[email protected]<mailto:[email protected]>>
Subject: [cisco-voip] Anyone running 8961s with UCCX 8.5.1SU3?
Anyone running 8961s with UCCX 8.5.1SU3?
Customer indicated they setup some 8961s and after logging into CAD they get an
error;
[cid:[email protected]]
CCM 8.6.2.22900-9 and UCCX 8.5.1SU3
These are 8961s running sip8961.9-3-4-24 seems other model phone?s are fine.
They?ve had TAC case 627583127 open for awhile.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/86ee5047/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10825 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/86ee5047/attachment-0001.png>
------------------------------
Message: 4
Date: Tue, 8 Oct 2013 14:01:52 -0500
From: Bryant Onojeta <[email protected]>
To: "Jason Aarons (AM)" <[email protected]>
Cc: "cisco-voip \([email protected]\)"
<[email protected]>
Subject: Re: [cisco-voip] Anyone running 8961s with UCCX 8.5.1SU3?
Message-ID:
<CAK5i2X6GWN6vXweA=j1uvkjjeas-atu7ee3e2t1ukxzkzjc...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
8971's....
On Tue, Oct 8, 2013 at 1:04 PM, Jason Aarons (AM) <
[email protected]> wrote:
> Anyone running 8961s with UCCX 8.5.1SU3?****
>
> ** **
>
> Customer indicated they setup some 8961s and after logging into CAD they
> get an error;****
>
> ** **
>
> [image: cid:[email protected]]****
>
> ** **
>
> ** **
>
> ** **
>
> CCM 8.6.2.22900-9 and UCCX 8.5.1SU3****
>
> ** **
>
> These are 8961s running sip8961.9-3-4-24 seems other model phone?s are
> fine.****
>
> ** **
>
> They?ve had TAC case 627583127 open for awhile.****
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
--
-Bryant
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/824f06a1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 10825 bytes
Desc: not available
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/824f06a1/attachment-0001.png>
------------------------------
Message: 5
Date: Tue, 8 Oct 2013 15:02:35 -0500
From: Erick Wellnitz <[email protected]>
To: "Ryan Ratliff (rratliff)" <[email protected]>
Cc: cisco-voip <[email protected]>
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
Message-ID:
<cak0wosb+7jrvovxe-fcm1usknew+jqmu-aqp-0xeoomunbp...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
I may have found something but I'm not sure.
In the packet capture, I see that the request
for SEPXXXXXXXXXXXX.cnf.xml.sgn is sent to the user's cluster but is not
found. At that point the logout is initiated.
On Mon, Oct 7, 2013 at 10:51 AM, Erick Wellnitz <[email protected]>wrote:
> And this:
>
>
> 7730: WRN 09:00:37.155813 SECD: WARN:getTLInfoFromFile: ** phone has no TL
> file /flash0/sec/ctl//CTLFile.tlv
>
>
> On Mon, Oct 7, 2013 at 10:48 AM, Erick Wellnitz
> <[email protected]>wrote:
>
>> The only 'abnormal' thing I see is this:
>>
>>
>> 7739: WRN 09:00:37.178303 SECD: WARN:getTLInfoFromFile: TL signer's
>> issuer name too big, may truncate
>>
>>
>> On Fri, Oct 4, 2013 at 6:26 PM, Ryan Ratliff (rratliff) <
>> [email protected]> wrote:
>>
>>> I it's easier get the console logs there will likely be something
>>> there to go off.
>>>
>>> Sent from my iPhone
>>>
>>> On Oct 4, 2013, at 5:10 PM, "Erick Wellnitz" <[email protected]>
>>> wrote:
>>>
>>> The profile logs in, phone resets, profile gets logged out, phone
>>> resets and displays 'extension mobility unavailable.
>>>
>>> We believe it is somehow related to DNS because when we register a phone
>>> to one of the 9.1 clusters in the other location login works as expected.
>>> I haven't had a chance to do a packet capture yet.
>>>
>>>
>>> On Fri, Oct 4, 2013 at 4:00 PM, Ryan Ratliff (rratliff) <
>>> [email protected]> wrote:
>>>
>>>> By the way what's the error code that the phone displays? EM has been
>>>> better than most about having useful errors, even if they are subject to
>>>> the secret decoder ring.
>>>>
>>>> -Ryan
>>>>
>>>> On Oct 4, 2013, at 4:10 PM, Erick Wellnitz <[email protected]>
>>>> wrote:
>>>>
>>>> Yes, it is also the primary tftp server.
>>>>
>>>>
>>>> On Fri, Oct 4, 2013 at 12:57 PM, Ryan Ratliff (rratliff) <
>>>> [email protected]> wrote:
>>>>
>>>>> System->Server values don't impact certificates. They will impact
>>>>> what the phone gets in config files so if you aren't using DNS this will
>>>>> be
>>>>> an issue. Is that pub also the TFTP server that is going to show up in
>>>>> the
>>>>> mini-config?
>>>>>
>>>>> -Ryan
>>>>>
>>>>> On Oct 4, 2013, at 1:13 PM, Erick Wellnitz <[email protected]>
>>>>> wrote:
>>>>>
>>>>> I always forget about doing a packet capture on the phone.
>>>>>
>>>>> I'm thinking it is cert related because on this one cluster the
>>>>> Publisher is set up under servers using it's hostname instead of IP while
>>>>> all the others are using IP.
>>>>>
>>>>> We're going to change this once we get approval then re-export,
>>>>> consolidate and import.
>>>>>
>>>>>
>>>>> On Thu, Oct 3, 2013 at 4:49 PM, Brian Meade (brmeade) <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> Erick,****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Can you grab a packet capture from the phone trying to log in? The
>>>>>> packet captures seem to show the EMCC issues very clearly. You should
>>>>>> see
>>>>>> after the login, the phone will download its mini-config with the new
>>>>>> TFTP
>>>>>> server info. You?ll then see it try to download its ITL from the other
>>>>>> cluster. If you don?t see the phone request anything after that, most
>>>>>> likely it didn?t trust the signer of the ITL and it will show the
>>>>>> ?Extension Mobility is unavailable? error message.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Usually that means you need to do a Re-Export, Consolidate, Import of
>>>>>> the certificates.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> Brian Meade****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> *From:* cisco-voip [mailto:[email protected]] *On
>>>>>> Behalf Of *Erick Wellnitz
>>>>>> *Sent:* Thursday, October 03, 2013 5:01 PM
>>>>>> *To:* Jason Aarons (AM)
>>>>>> *Cc:* cisco-voip
>>>>>> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> That's the odd thing. All of the traces look like it is successful
>>>>>> but the phone (7965) resets, logs the user out and displays a message
>>>>>> that
>>>>>> extension mobility is not available without an error code. I get similar
>>>>>> behavior on the 8945 but without the message.****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>> I've gon through the EMCC guide a number of times and nothing sticks
>>>>>> out as obvious.****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>> On Thu, Oct 3, 2013 at 3:41 PM, Jason Aarons (AM) <
>>>>>> [email protected]> wrote:****
>>>>>>
>>>>>> I was using 8.6 the first time I setup EMCC to another 8.6 box.****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>> *From:* cisco-voip [mailto:[email protected]] *On
>>>>>> Behalf Of *Anthony Holloway
>>>>>> *Sent:* Thursday, October 03, 2013 3:39 PM
>>>>>> *To:* Erick Wellnitz
>>>>>> *Cc:* cisco-voip
>>>>>> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>> I have one idea.****
>>>>>>
>>>>>> EMCC does not work very well in 8.5 because you cannot "home" a user
>>>>>> to a cluster. Therefore, if your LDAP integrations are the same for each
>>>>>> cluster, it would be impossible to know which cluster the user is homed
>>>>>> to. 9.1 on the other hand has this feature on the end user page, and
>>>>>> thus
>>>>>> overcomes this limitation.****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>> On Thu, Oct 3, 2013 at 1:50 PM, Erick Wellnitz <
>>>>>> [email protected]> wrote:****
>>>>>>
>>>>>> I have a strange situation.****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>> 3 Clusters. 2 on 9.1 and the other on 8.5 EMCC works except with
>>>>>> users configured on the 8.5 cluster. The profile logs in then
>>>>>> immediately
>>>>>> logs out without an error message.****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>> Any ideas would be greatly appreciated!****
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> cisco-voip mailing list
>>>>>> [email protected]
>>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip****
>>>>>>
>>>>>> ****
>>>>>>
>>>>>>
>>>>>>
>>>>>> itevomcid ****
>>>>>>
>>>>>> ** **
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> [email protected]
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/3a154a82/attachment-0001.html>
------------------------------
Message: 6
Date: Tue, 8 Oct 2013 20:16:48 +0000
From: "Brian Meade (brmeade)" <[email protected]>
To: Erick Wellnitz <[email protected]>, "Ryan Ratliff
(rratliff)" <[email protected]>
Cc: cisco-voip <[email protected]>
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Erick,
Does the user ever show up in the Remotely Logged-In Device Report on the home
cluster?
Brian Meade
From: Erick Wellnitz [mailto:[email protected]]
Sent: Tuesday, October 08, 2013 4:03 PM
To: Ryan Ratliff (rratliff)
Cc: Brian Meade (brmeade); cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
I may have found something but I'm not sure.
In the packet capture, I see that the request for SEPXXXXXXXXXXXX.cnf.xml.sgn
is sent to the user's cluster but is not found. At that point the logout is
initiated.
On Mon, Oct 7, 2013 at 10:51 AM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
And this:
7730: WRN 09:00:37.155813 SECD: WARN:getTLInfoFromFile: ** phone has no TL file
/flash0/sec/ctl//CTLFile.tlv
On Mon, Oct 7, 2013 at 10:48 AM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
The only 'abnormal' thing I see is this:
7739: WRN 09:00:37.178303 SECD: WARN:getTLInfoFromFile: TL signer's issuer name
too big, may truncate
On Fri, Oct 4, 2013 at 6:26 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
I it's easier get the console logs there will likely be something there to go
off.
Sent from my iPhone
On Oct 4, 2013, at 5:10 PM, "Erick Wellnitz"
<[email protected]<mailto:[email protected]>> wrote:
The profile logs in, phone resets, profile gets logged out, phone resets and
displays 'extension mobility unavailable.
We believe it is somehow related to DNS because when we register a phone to one
of the 9.1 clusters in the other location login works as expected. I haven't
had a chance to do a packet capture yet.
On Fri, Oct 4, 2013 at 4:00 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
By the way what's the error code that the phone displays? EM has been better
than most about having useful errors, even if they are subject to the secret
decoder ring.
-Ryan
On Oct 4, 2013, at 4:10 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
Yes, it is also the primary tftp server.
On Fri, Oct 4, 2013 at 12:57 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
System->Server values don't impact certificates. They will impact what the
phone gets in config files so if you aren't using DNS this will be an issue.
Is that pub also the TFTP server that is going to show up in the mini-config?
-Ryan
On Oct 4, 2013, at 1:13 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
I always forget about doing a packet capture on the phone.
I'm thinking it is cert related because on this one cluster the Publisher is
set up under servers using it's hostname instead of IP while all the others are
using IP.
We're going to change this once we get approval then re-export, consolidate and
import.
On Thu, Oct 3, 2013 at 4:49 PM, Brian Meade (brmeade)
<[email protected]<mailto:[email protected]>> wrote:
Erick,
Can you grab a packet capture from the phone trying to log in? The packet
captures seem to show the EMCC issues very clearly. You should see after the
login, the phone will download its mini-config with the new TFTP server info.
You'll then see it try to download its ITL from the other cluster. If you
don't see the phone request anything after that, most likely it didn't trust
the signer of the ITL and it will show the "Extension Mobility is unavailable"
error message.
Usually that means you need to do a Re-Export, Consolidate, Import of the
certificates.
Brian Meade
From: cisco-voip
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Erick Wellnitz
Sent: Thursday, October 03, 2013 5:01 PM
To: Jason Aarons (AM)
Cc: cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
That's the odd thing. All of the traces look like it is successful but the
phone (7965) resets, logs the user out and displays a message that extension
mobility is not available without an error code. I get similar behavior on the
8945 but without the message.
I've gon through the EMCC guide a number of times and nothing sticks out as
obvious.
On Thu, Oct 3, 2013 at 3:41 PM, Jason Aarons (AM)
<[email protected]<mailto:[email protected]>> wrote:
I was using 8.6 the first time I setup EMCC to another 8.6 box.
From: cisco-voip
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Anthony Holloway
Sent: Thursday, October 03, 2013 3:39 PM
To: Erick Wellnitz
Cc: cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
I have one idea.
EMCC does not work very well in 8.5 because you cannot "home" a user to a
cluster. Therefore, if your LDAP integrations are the same for each cluster,
it would be impossible to know which cluster the user is homed to. 9.1 on the
other hand has this feature on the end user page, and thus overcomes this
limitation.
On Thu, Oct 3, 2013 at 1:50 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
I have a strange situation.
3 Clusters. 2 on 9.1 and the other on 8.5 EMCC works except with users
configured on the 8.5 cluster. The profile logs in then immediately logs out
without an error message.
Any ideas would be greatly appreciated!
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
itevomcid
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/2a16a465/attachment-0001.html>
------------------------------
Message: 7
Date: Tue, 8 Oct 2013 15:27:11 -0500
From: Erick Wellnitz <[email protected]>
To: "Brian Meade (brmeade)" <[email protected]>
Cc: cisco-voip <[email protected]>
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
Message-ID:
<CAK0wOsC8fPaZdk+xcb4ecF2r05Pok+_RwaX=ofqh0fsnkg-...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
No, as soon as I get the 404 not found response in regards to the .sgn
config file the logout is initiated.
On Tue, Oct 8, 2013 at 3:16 PM, Brian Meade (brmeade) <[email protected]>wrote:
> Erick,****
>
> ** **
>
> Does the user ever show up in the Remotely Logged-In Device Report on the
> home cluster?****
>
> ** **
>
> Brian Meade****
>
> ** **
>
> *From:* Erick Wellnitz [mailto:[email protected]]
> *Sent:* Tuesday, October 08, 2013 4:03 PM
> *To:* Ryan Ratliff (rratliff)
> *Cc:* Brian Meade (brmeade); cisco-voip
> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>
> ** **
>
> I may have found something but I'm not sure.****
>
> ****
>
> In the packet capture, I see that the request
> for SEPXXXXXXXXXXXX.cnf.xml.sgn is sent to the user's cluster but is not
> found. At that point the logout is initiated.****
>
> ** **
>
> On Mon, Oct 7, 2013 at 10:51 AM, Erick Wellnitz <[email protected]>
> wrote:****
>
> And this:****
>
> ****
>
> 7730: WRN 09:00:37.155813 SECD: WARN:getTLInfoFromFile: ** phone has no TL
> file /flash0/sec/ctl//CTLFile.tlv****
>
> ** **
>
> On Mon, Oct 7, 2013 at 10:48 AM, Erick Wellnitz <[email protected]>
> wrote:****
>
> The only 'abnormal' thing I see is this:****
>
> ****
>
> 7739: WRN 09:00:37.178303 SECD: WARN:getTLInfoFromFile: TL signer's issuer
> name too big, may truncate****
>
> ** **
>
> On Fri, Oct 4, 2013 at 6:26 PM, Ryan Ratliff (rratliff) <
> [email protected]> wrote:****
>
> I it's easier get the console logs there will likely be something there to
> go off.
>
> Sent from my iPhone****
>
>
> On Oct 4, 2013, at 5:10 PM, "Erick Wellnitz" <[email protected]>
> wrote:****
>
> The profile logs in, phone resets, profile gets logged out, phone
> resets and displays 'extension mobility unavailable.****
>
> ****
>
> We believe it is somehow related to DNS because when we register a phone
> to one of the 9.1 clusters in the other location login works as expected.
> I haven't had a chance to do a packet capture yet.****
>
> ** **
>
> On Fri, Oct 4, 2013 at 4:00 PM, Ryan Ratliff (rratliff) <
> [email protected]> wrote:****
>
> By the way what's the error code that the phone displays? EM has been
> better than most about having useful errors, even if they are subject to
> the secret decoder ring. ****
>
> ** **
>
> -Ryan ****
>
> ** **
>
> On Oct 4, 2013, at 4:10 PM, Erick Wellnitz <[email protected]>
> wrote:****
>
> ** **
>
> Yes, it is also the primary tftp server.****
>
> ** **
>
> On Fri, Oct 4, 2013 at 12:57 PM, Ryan Ratliff (rratliff) <
> [email protected]> wrote:****
>
> System->Server values don't impact certificates. They will impact what
> the phone gets in config files so if you aren't using DNS this will be an
> issue. Is that pub also the TFTP server that is going to show up in the
> mini-config? ****
>
> ** **
>
> -Ryan ****
>
> ** **
>
> On Oct 4, 2013, at 1:13 PM, Erick Wellnitz <[email protected]>
> wrote:****
>
> ** **
>
> I always forget about doing a packet capture on the phone.****
>
> ****
>
> I'm thinking it is cert related because on this one cluster the Publisher
> is set up under servers using it's hostname instead of IP while all the
> others are using IP. ****
>
> ****
>
> We're going to change this once we get approval then re-export,
> consolidate and import.****
>
> ** **
>
> On Thu, Oct 3, 2013 at 4:49 PM, Brian Meade (brmeade) <[email protected]>
> wrote:****
>
> Erick,****
>
> ****
>
> Can you grab a packet capture from the phone trying to log in? The packet
> captures seem to show the EMCC issues very clearly. You should see after
> the login, the phone will download its mini-config with the new TFTP server
> info. You?ll then see it try to download its ITL from the other cluster.
> If you don?t see the phone request anything after that, most likely it
> didn?t trust the signer of the ITL and it will show the ?Extension Mobility
> is unavailable? error message.****
>
> ****
>
> Usually that means you need to do a Re-Export, Consolidate, Import of the
> certificates.****
>
> ****
>
> Brian Meade****
>
> ****
>
> *From:* cisco-voip [mailto:[email protected]] *On Behalf
> Of *Erick Wellnitz
> *Sent:* Thursday, October 03, 2013 5:01 PM
> *To:* Jason Aarons (AM)
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>
> ****
>
> That's the odd thing. All of the traces look like it is successful but
> the phone (7965) resets, logs the user out and displays a message that
> extension mobility is not available without an error code. I get similar
> behavior on the 8945 but without the message.****
>
> ****
>
> I've gon through the EMCC guide a number of times and nothing sticks out
> as obvious.****
>
> ****
>
> On Thu, Oct 3, 2013 at 3:41 PM, Jason Aarons (AM) <
> [email protected]> wrote:****
>
> I was using 8.6 the first time I setup EMCC to another 8.6 box.****
>
> ****
>
> *From:* cisco-voip [mailto:[email protected]] *On Behalf
> Of *Anthony Holloway
> *Sent:* Thursday, October 03, 2013 3:39 PM
> *To:* Erick Wellnitz
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>
> ****
>
> ****
>
> I have one idea.****
>
> EMCC does not work very well in 8.5 because you cannot "home" a user to a
> cluster. Therefore, if your LDAP integrations are the same for each
> cluster, it would be impossible to know which cluster the user is homed
> to. 9.1 on the other hand has this feature on the end user page, and thus
> overcomes this limitation.****
>
> ****
>
> On Thu, Oct 3, 2013 at 1:50 PM, Erick Wellnitz <[email protected]>
> wrote:****
>
> I have a strange situation.****
>
> ****
>
> 3 Clusters. 2 on 9.1 and the other on 8.5 EMCC works except with users
> configured on the 8.5 cluster. The profile logs in then immediately logs
> out without an error message.****
>
> ****
>
> Any ideas would be greatly appreciated!****
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ****
>
>
>
> itevomcid ****
>
> ****
>
> ** **
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/4e2afa7f/attachment-0001.html>
------------------------------
Message: 8
Date: Tue, 8 Oct 2013 20:32:17 +0000
From: "Brian Meade (brmeade)" <[email protected]>
To: Erick Wellnitz <[email protected]>
Cc: cisco-voip <[email protected]>
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Erick,
Would it be possible for you to send the packet capture so I can take a quick
look?
Thanks,
Brian Meade
From: Erick Wellnitz [mailto:[email protected]]
Sent: Tuesday, October 08, 2013 4:27 PM
To: Brian Meade (brmeade)
Cc: Ryan Ratliff (rratliff); cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
No, as soon as I get the 404 not found response in regards to the .sgn config
file the logout is initiated.
On Tue, Oct 8, 2013 at 3:16 PM, Brian Meade (brmeade)
<[email protected]<mailto:[email protected]>> wrote:
Erick,
Does the user ever show up in the Remotely Logged-In Device Report on the home
cluster?
Brian Meade
From: Erick Wellnitz
[mailto:[email protected]<mailto:[email protected]>]
Sent: Tuesday, October 08, 2013 4:03 PM
To: Ryan Ratliff (rratliff)
Cc: Brian Meade (brmeade); cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
I may have found something but I'm not sure.
In the packet capture, I see that the request for SEPXXXXXXXXXXXX.cnf.xml.sgn
is sent to the user's cluster but is not found. At that point the logout is
initiated.
On Mon, Oct 7, 2013 at 10:51 AM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
And this:
7730: WRN 09:00:37.155813 SECD: WARN:getTLInfoFromFile: ** phone has no TL file
/flash0/sec/ctl//CTLFile.tlv
On Mon, Oct 7, 2013 at 10:48 AM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
The only 'abnormal' thing I see is this:
7739: WRN 09:00:37.178303 SECD: WARN:getTLInfoFromFile: TL signer's issuer name
too big, may truncate
On Fri, Oct 4, 2013 at 6:26 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
I it's easier get the console logs there will likely be something there to go
off.
Sent from my iPhone
On Oct 4, 2013, at 5:10 PM, "Erick Wellnitz"
<[email protected]<mailto:[email protected]>> wrote:
The profile logs in, phone resets, profile gets logged out, phone resets and
displays 'extension mobility unavailable.
We believe it is somehow related to DNS because when we register a phone to one
of the 9.1 clusters in the other location login works as expected. I haven't
had a chance to do a packet capture yet.
On Fri, Oct 4, 2013 at 4:00 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
By the way what's the error code that the phone displays? EM has been better
than most about having useful errors, even if they are subject to the secret
decoder ring.
-Ryan
On Oct 4, 2013, at 4:10 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
Yes, it is also the primary tftp server.
On Fri, Oct 4, 2013 at 12:57 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
System->Server values don't impact certificates. They will impact what the
phone gets in config files so if you aren't using DNS this will be an issue.
Is that pub also the TFTP server that is going to show up in the mini-config?
-Ryan
On Oct 4, 2013, at 1:13 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
I always forget about doing a packet capture on the phone.
I'm thinking it is cert related because on this one cluster the Publisher is
set up under servers using it's hostname instead of IP while all the others are
using IP.
We're going to change this once we get approval then re-export, consolidate and
import.
On Thu, Oct 3, 2013 at 4:49 PM, Brian Meade (brmeade)
<[email protected]<mailto:[email protected]>> wrote:
Erick,
Can you grab a packet capture from the phone trying to log in? The packet
captures seem to show the EMCC issues very clearly. You should see after the
login, the phone will download its mini-config with the new TFTP server info.
You'll then see it try to download its ITL from the other cluster. If you
don't see the phone request anything after that, most likely it didn't trust
the signer of the ITL and it will show the "Extension Mobility is unavailable"
error message.
Usually that means you need to do a Re-Export, Consolidate, Import of the
certificates.
Brian Meade
From: cisco-voip
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Erick Wellnitz
Sent: Thursday, October 03, 2013 5:01 PM
To: Jason Aarons (AM)
Cc: cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
That's the odd thing. All of the traces look like it is successful but the
phone (7965) resets, logs the user out and displays a message that extension
mobility is not available without an error code. I get similar behavior on the
8945 but without the message.
I've gon through the EMCC guide a number of times and nothing sticks out as
obvious.
On Thu, Oct 3, 2013 at 3:41 PM, Jason Aarons (AM)
<[email protected]<mailto:[email protected]>> wrote:
I was using 8.6 the first time I setup EMCC to another 8.6 box.
From: cisco-voip
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Anthony Holloway
Sent: Thursday, October 03, 2013 3:39 PM
To: Erick Wellnitz
Cc: cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
I have one idea.
EMCC does not work very well in 8.5 because you cannot "home" a user to a
cluster. Therefore, if your LDAP integrations are the same for each cluster,
it would be impossible to know which cluster the user is homed to. 9.1 on the
other hand has this feature on the end user page, and thus overcomes this
limitation.
On Thu, Oct 3, 2013 at 1:50 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
I have a strange situation.
3 Clusters. 2 on 9.1 and the other on 8.5 EMCC works except with users
configured on the 8.5 cluster. The profile logs in then immediately logs out
without an error message.
Any ideas would be greatly appreciated!
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
itevomcid
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/6bd54840/attachment-0001.html>
------------------------------
Message: 9
Date: Tue, 8 Oct 2013 21:25:21 +0000
From: "Brian Meade (brmeade)" <[email protected]>
To: Erick Wellnitz <[email protected]>
Cc: cisco-voip <[email protected]>
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Eric,
Just checked your packet capture and see the 404 you're talking about from the
home cluster. It's indeed for the SEP<MAC>.cnf.cml.sgn file that's having the
problem.
Can you use a TFTP client to try downloading other signed files from that home
cluster?
>From your mini-config, it looks like the 2 TFTP servers it gets is
>XXX-XXX-UCMP-1 and 10.12x.xx.22.
I then see a failed DNS lookup for ASI-LNX-UCMP-1 so it uses the 10.12x.xx.22
address. I wonder if there's any sort of replication issues that may be
causing the 404 Not Found.
Can you check "utils dbreplication runtimestate" on the publisher of the home
cluster?
Thanks,
Brian
From: Erick Wellnitz [mailto:[email protected]]
Sent: Tuesday, October 08, 2013 4:27 PM
To: Brian Meade (brmeade)
Cc: Ryan Ratliff (rratliff); cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
No, as soon as I get the 404 not found response in regards to the .sgn config
file the logout is initiated.
On Tue, Oct 8, 2013 at 3:16 PM, Brian Meade (brmeade)
<[email protected]<mailto:[email protected]>> wrote:
Erick,
Does the user ever show up in the Remotely Logged-In Device Report on the home
cluster?
Brian Meade
From: Erick Wellnitz
[mailto:[email protected]<mailto:[email protected]>]
Sent: Tuesday, October 08, 2013 4:03 PM
To: Ryan Ratliff (rratliff)
Cc: Brian Meade (brmeade); cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
I may have found something but I'm not sure.
In the packet capture, I see that the request for SEPXXXXXXXXXXXX.cnf.xml.sgn
is sent to the user's cluster but is not found. At that point the logout is
initiated.
On Mon, Oct 7, 2013 at 10:51 AM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
And this:
7730: WRN 09:00:37.155813 SECD: WARN:getTLInfoFromFile: ** phone has no TL file
/flash0/sec/ctl//CTLFile.tlv
On Mon, Oct 7, 2013 at 10:48 AM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
The only 'abnormal' thing I see is this:
7739: WRN 09:00:37.178303 SECD: WARN:getTLInfoFromFile: TL signer's issuer name
too big, may truncate
On Fri, Oct 4, 2013 at 6:26 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
I it's easier get the console logs there will likely be something there to go
off.
Sent from my iPhone
On Oct 4, 2013, at 5:10 PM, "Erick Wellnitz"
<[email protected]<mailto:[email protected]>> wrote:
The profile logs in, phone resets, profile gets logged out, phone resets and
displays 'extension mobility unavailable.
We believe it is somehow related to DNS because when we register a phone to one
of the 9.1 clusters in the other location login works as expected. I haven't
had a chance to do a packet capture yet.
On Fri, Oct 4, 2013 at 4:00 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
By the way what's the error code that the phone displays? EM has been better
than most about having useful errors, even if they are subject to the secret
decoder ring.
-Ryan
On Oct 4, 2013, at 4:10 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
Yes, it is also the primary tftp server.
On Fri, Oct 4, 2013 at 12:57 PM, Ryan Ratliff (rratliff)
<[email protected]<mailto:[email protected]>> wrote:
System->Server values don't impact certificates. They will impact what the
phone gets in config files so if you aren't using DNS this will be an issue.
Is that pub also the TFTP server that is going to show up in the mini-config?
-Ryan
On Oct 4, 2013, at 1:13 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
I always forget about doing a packet capture on the phone.
I'm thinking it is cert related because on this one cluster the Publisher is
set up under servers using it's hostname instead of IP while all the others are
using IP.
We're going to change this once we get approval then re-export, consolidate and
import.
On Thu, Oct 3, 2013 at 4:49 PM, Brian Meade (brmeade)
<[email protected]<mailto:[email protected]>> wrote:
Erick,
Can you grab a packet capture from the phone trying to log in? The packet
captures seem to show the EMCC issues very clearly. You should see after the
login, the phone will download its mini-config with the new TFTP server info.
You'll then see it try to download its ITL from the other cluster. If you
don't see the phone request anything after that, most likely it didn't trust
the signer of the ITL and it will show the "Extension Mobility is unavailable"
error message.
Usually that means you need to do a Re-Export, Consolidate, Import of the
certificates.
Brian Meade
From: cisco-voip
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Erick Wellnitz
Sent: Thursday, October 03, 2013 5:01 PM
To: Jason Aarons (AM)
Cc: cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
That's the odd thing. All of the traces look like it is successful but the
phone (7965) resets, logs the user out and displays a message that extension
mobility is not available without an error code. I get similar behavior on the
8945 but without the message.
I've gon through the EMCC guide a number of times and nothing sticks out as
obvious.
On Thu, Oct 3, 2013 at 3:41 PM, Jason Aarons (AM)
<[email protected]<mailto:[email protected]>> wrote:
I was using 8.6 the first time I setup EMCC to another 8.6 box.
From: cisco-voip
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Anthony Holloway
Sent: Thursday, October 03, 2013 3:39 PM
To: Erick Wellnitz
Cc: cisco-voip
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
I have one idea.
EMCC does not work very well in 8.5 because you cannot "home" a user to a
cluster. Therefore, if your LDAP integrations are the same for each cluster,
it would be impossible to know which cluster the user is homed to. 9.1 on the
other hand has this feature on the end user page, and thus overcomes this
limitation.
On Thu, Oct 3, 2013 at 1:50 PM, Erick Wellnitz
<[email protected]<mailto:[email protected]>> wrote:
I have a strange situation.
3 Clusters. 2 on 9.1 and the other on 8.5 EMCC works except with users
configured on the 8.5 cluster. The profile logs in then immediately logs out
without an error message.
Any ideas would be greatly appreciated!
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
itevomcid
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131008/0d2baeaf/attachment-0001.html>
------------------------------
Message: 10
Date: Wed, 9 Oct 2013 05:51:41 +0000
From: shary shary <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Transfer to IVR in AMD is not working properly
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Hi Folks,I have configured the Progressive outbound IVR campaign in UCCX 8.5.x
and every thing is working fine except two points.
1- There is no Phone 2 and Phone 3 field in import window only Phone 1 field
with other options like first name , account num etc. I need to configure the
alternate numbers as well.
2- AMD feature is working for some calls not for all, infact i have to transfer
such calls to IVR. After some investigation i came to know there is difference
in "no of rings" to trigger the Answering machine at customer end. Customer
number after 4 rings trigger VM and call gets transferred to IVR while the
customer number which triggers its VM after 7 rings doesn't get transfer to IVR.
thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131009/0a50b57f/attachment-0001.html>
------------------------------
Message: 11
Date: Wed, 9 Oct 2013 06:47:02 +0000
From: Tim Smith <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Unity Connection SMTP Address
Message-ID:
<53cf8dd976b84dbe9c49760a41c2f...@hknpr04mb051.apcprd04.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Hi guys,
Is there a way to bulk update "SMTP address" in Unity Connection (9.1(2)) ?
Does this SMTP address matter if we are not doing VPIM networking etc?
I have migrated from no LDAP to LDAP.
I did try a COBRAS backup / restore (editing backup in between to change Alias)
And I notice you can edit SMTP address here as well and remap.
But this has other issues with it.
The easiest way seems to be to bulk export, update the LDAP user field, and
then sync with LDAP.
This updates the Alias as needed.
But SMTP address does not update to the new alias.
Cheers,
Tim.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131009/cecfeb70/attachment-0001.html>
------------------------------
Message: 12
Date: Wed, 9 Oct 2013 06:53:33 +0000
From: Tim Smith <[email protected]>
To: "Ryan Ratliff (rratliff)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] CUCM 9.x ELM and Owner ID
Message-ID:
<ed4093ea23aa449f900174b01c47e...@hknpr04mb051.apcprd04.prod.outlook.com>
Content-Type: text/plain; charset="us-ascii"
Thanks Ryan,
Sorry to keep banging on about this, but I'm still a bit confused.
I definitely don't want to get more licensing than we are entitled to.
I think from CUCM point of view, and based on below.
Phones without owners are essentially considered public space.
Phones with owners associated, would get attributed in the right place, i.e.
CUWL standard, pro etc.
In extension mobility environments, usually none of our phones have owners
associated.
So when we go to add CSF's for Jabber for instance, we come unstuck.
Cheers,
Tim
________________________________
From: Ryan Ratliff (rratliff) <[email protected]>
Sent: Wednesday, 9 October 2013 1:41 AM
To: Tim Smith
Cc: Joe Martini (joemar2); [email protected]
Subject: Re: [cisco-voip] CUCM 9.x ELM and Owner ID
I recommend when looking at the User Count Tool or whatever tool you are using
to do your license migration (before the upgrade) you should count your public
space phones as a separate user that will require a license.
I understand Licensing is being very generous for current migrations however I
would pay careful attention to what you ask for and what you get as compared to
what you currently pay for so there are no big surprises at your next renewal.
-Ryan
On Oct 8, 2013, at 10:25 AM, Tim Smith
<[email protected]<mailto:[email protected]>>
wrote:
Thanks Ryan
Does that mean we should ask licensing for a public space lic per em phone?
We don't actually need to buy more licenses right?
Cheers,
Tim
On 9 Oct 2013, at 1:09 am, "Ryan Ratliff (rratliff)"
<[email protected]<mailto:[email protected]>> wrote:
As soon as you add SNR or a soft client to those users you have to double up on
licenses to account for the public space phones.
Today that is the solution and when doing your DLU to ELM conversion you need
to plan accordingly.
-Ryan
On Oct 7, 2013, at 7:33 PM, Tim Smith
<[email protected]<mailto:[email protected]>> wrote:
Thanks Joe,
I have seen that one before, I'm not sure that is the same issue.
This is in regard to the physical phones not been allocated to a user. (i.e.
assigning phones owner ID's)
This seems to cause a double up for me when I create CSF profiles.
Cheers,
Tim
From: Joe Martini [mailto:[email protected]<http://cisco.com/>]
Sent: Tuesday, 8 October 2013 10:08 AM
To: Tim Smith
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [cisco-voip] CUCM 9.x ELM and Owner ID
Versions of CUCM that contain the fix for CSCue14471 no longer have this issue.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCue14471
Joe
On Oct 7, 2013, at 6:00 PM, Tim Smith
<[email protected]<mailto:[email protected]>> wrote:
Hi guys,
I've seen some discussion on this already
http://www.gossamer-threads.com/lists/cisco/voip/172472?search_string=owner%20cuwl;#172472
Most clients do not assign owner ID as they use extension mobility.
(I will admit it is true that a lot of mobility users actually stay logged into
the same phone and we could technically assign them as the owner)
Either way, I keep ending up with my licensing in ELM being out of balance due
to having phones and CSF's.
The TAC answer to me was that I should assign an owner ID.
Am I missing something here? Is there another solution?
Cheers,
Tim.
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131009/ba8bd9f7/attachment-0001.html>
------------------------------
Message: 13
Date: Wed, 9 Oct 2013 09:49:10 -0500
From: Erick Wellnitz <[email protected]>
To: "Brian Meade (brmeade)" <[email protected]>
Cc: cisco-voip <[email protected]>
Subject: Re: [cisco-voip] 'interesting' EMCC behavior
Message-ID:
<cak0wosbhhchuzjqywdrlgk-2nkie57bezh5rerlzupefnqu...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Well, I think we have a replication issue.
DB and Replication Services: ALL RUNNING
Cluster Replication State: BROADCAST SYNC Completed on 3 servers at:
2012-03-05-
18-58
Last Sync Result: SYNC COMPLETED 530 tables sync'ed out of 530
Sync Errors: NO ERRORS
DB Version: ccm8_5_1_13900_5
Number of replicated tables: 530
Cluster Detailed View from PUB (4 Servers):
PING REPLICATION REPL.
DBver&
R
EPL. REPLICATION SETUP
SERVER-NAME IP ADDRESS (msec) RPC? STATUS QUEUE
TABLES
L
OOP? (RTMT) & details
----------- ------------ ------ ---- ----------- -----
--------
---- -----------------
ASI-LNX-UCMP-1 10.129.146.20 0.032 Yes Connected 0
match
Y
es (2) PUB Setup Completed
ASI-LNX-UCMS-1 10.129.146.21 0.248 Yes Connected 148
match
Y
es (2) Setup Completed
ASI-LNX-UCMS-2 10.129.146.22 0.259 Yes Connected 148
match
Y
es (2) Setup Completed
ASI-LNX-UCMS-3 10.130.146.20 1.24 Yes Connected 148
match
Y
es (2) Setup Completed
All of our other clusters show 0 for Repl. Queue
On Tue, Oct 8, 2013 at 4:25 PM, Brian Meade (brmeade) <[email protected]>wrote:
> Eric,****
>
> ** **
>
> Just checked your packet capture and see the 404 you?re talking about from
> the home cluster. It?s indeed for the SEP<MAC>.cnf.cml.sgn file that?s
> having the problem.****
>
> ** **
>
> Can you use a TFTP client to try downloading other signed files from that
> home cluster?****
>
> ** **
>
> From your mini-config, it looks like the 2 TFTP servers it gets is
> XXX-XXX-UCMP-1 and 10.12x.xx.22.****
>
> ** **
>
> I then see a failed DNS lookup for ASI-LNX-UCMP-1 so it uses the
> 10.12x.xx.22 address. I wonder if there?s any sort of replication issues
> that may be causing the 404 Not Found.****
>
> ** **
>
> Can you check ?utils dbreplication runtimestate? on the publisher of the
> home cluster?****
>
> ** **
>
> Thanks,****
>
> Brian****
>
> ** **
>
> *From:* Erick Wellnitz [mailto:[email protected]]
> *Sent:* Tuesday, October 08, 2013 4:27 PM
> *To:* Brian Meade (brmeade)
> *Cc:* Ryan Ratliff (rratliff); cisco-voip
> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>
> ** **
>
> No, as soon as I get the 404 not found response in regards to the .sgn
> config file the logout is initiated.****
>
> ** **
>
> On Tue, Oct 8, 2013 at 3:16 PM, Brian Meade (brmeade) <[email protected]>
> wrote:****
>
> Erick,****
>
> ****
>
> Does the user ever show up in the Remotely Logged-In Device Report on the
> home cluster?****
>
> ****
>
> Brian Meade****
>
> ****
>
> *From:* Erick Wellnitz [mailto:[email protected]]
> *Sent:* Tuesday, October 08, 2013 4:03 PM
> *To:* Ryan Ratliff (rratliff)
> *Cc:* Brian Meade (brmeade); cisco-voip
> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>
> ****
>
> I may have found something but I'm not sure.****
>
> ****
>
> In the packet capture, I see that the request
> for SEPXXXXXXXXXXXX.cnf.xml.sgn is sent to the user's cluster but is not
> found. At that point the logout is initiated.****
>
> ****
>
> On Mon, Oct 7, 2013 at 10:51 AM, Erick Wellnitz <[email protected]>
> wrote:****
>
> And this:****
>
> ****
>
> 7730: WRN 09:00:37.155813 SECD: WARN:getTLInfoFromFile: ** phone has no TL
> file /flash0/sec/ctl//CTLFile.tlv****
>
> ****
>
> On Mon, Oct 7, 2013 at 10:48 AM, Erick Wellnitz <[email protected]>
> wrote:****
>
> The only 'abnormal' thing I see is this:****
>
> ****
>
> 7739: WRN 09:00:37.178303 SECD: WARN:getTLInfoFromFile: TL signer's issuer
> name too big, may truncate****
>
> ****
>
> On Fri, Oct 4, 2013 at 6:26 PM, Ryan Ratliff (rratliff) <
> [email protected]> wrote:****
>
> I it's easier get the console logs there will likely be something there to
> go off.
>
> Sent from my iPhone****
>
>
> On Oct 4, 2013, at 5:10 PM, "Erick Wellnitz" <[email protected]>
> wrote:****
>
> The profile logs in, phone resets, profile gets logged out, phone
> resets and displays 'extension mobility unavailable.****
>
> ****
>
> We believe it is somehow related to DNS because when we register a phone
> to one of the 9.1 clusters in the other location login works as expected.
> I haven't had a chance to do a packet capture yet.****
>
> ****
>
> On Fri, Oct 4, 2013 at 4:00 PM, Ryan Ratliff (rratliff) <
> [email protected]> wrote:****
>
> By the way what's the error code that the phone displays? EM has been
> better than most about having useful errors, even if they are subject to
> the secret decoder ring. ****
>
> ****
>
> -Ryan ****
>
> ****
>
> On Oct 4, 2013, at 4:10 PM, Erick Wellnitz <[email protected]>
> wrote:****
>
> ****
>
> Yes, it is also the primary tftp server.****
>
> ****
>
> On Fri, Oct 4, 2013 at 12:57 PM, Ryan Ratliff (rratliff) <
> [email protected]> wrote:****
>
> System->Server values don't impact certificates. They will impact what
> the phone gets in config files so if you aren't using DNS this will be an
> issue. Is that pub also the TFTP server that is going to show up in the
> mini-config? ****
>
> ****
>
> -Ryan ****
>
> ****
>
> On Oct 4, 2013, at 1:13 PM, Erick Wellnitz <[email protected]>
> wrote:****
>
> ****
>
> I always forget about doing a packet capture on the phone.****
>
> ****
>
> I'm thinking it is cert related because on this one cluster the Publisher
> is set up under servers using it's hostname instead of IP while all the
> others are using IP. ****
>
> ****
>
> We're going to change this once we get approval then re-export,
> consolidate and import.****
>
> ****
>
> On Thu, Oct 3, 2013 at 4:49 PM, Brian Meade (brmeade) <[email protected]>
> wrote:****
>
> Erick,****
>
> ****
>
> Can you grab a packet capture from the phone trying to log in? The packet
> captures seem to show the EMCC issues very clearly. You should see after
> the login, the phone will download its mini-config with the new TFTP server
> info. You?ll then see it try to download its ITL from the other cluster.
> If you don?t see the phone request anything after that, most likely it
> didn?t trust the signer of the ITL and it will show the ?Extension Mobility
> is unavailable? error message.****
>
> ****
>
> Usually that means you need to do a Re-Export, Consolidate, Import of the
> certificates.****
>
> ****
>
> Brian Meade****
>
> ****
>
> *From:* cisco-voip [mailto:[email protected]] *On Behalf
> Of *Erick Wellnitz
> *Sent:* Thursday, October 03, 2013 5:01 PM
> *To:* Jason Aarons (AM)
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>
> ****
>
> That's the odd thing. All of the traces look like it is successful but
> the phone (7965) resets, logs the user out and displays a message that
> extension mobility is not available without an error code. I get similar
> behavior on the 8945 but without the message.****
>
> ****
>
> I've gon through the EMCC guide a number of times and nothing sticks out
> as obvious.****
>
> ****
>
> On Thu, Oct 3, 2013 at 3:41 PM, Jason Aarons (AM) <
> [email protected]> wrote:****
>
> I was using 8.6 the first time I setup EMCC to another 8.6 box.****
>
> ****
>
> *From:* cisco-voip [mailto:[email protected]] *On Behalf
> Of *Anthony Holloway
> *Sent:* Thursday, October 03, 2013 3:39 PM
> *To:* Erick Wellnitz
> *Cc:* cisco-voip
> *Subject:* Re: [cisco-voip] 'interesting' EMCC behavior****
>
> ****
>
> ****
>
> I have one idea.****
>
> EMCC does not work very well in 8.5 because you cannot "home" a user to a
> cluster. Therefore, if your LDAP integrations are the same for each
> cluster, it would be impossible to know which cluster the user is homed
> to. 9.1 on the other hand has this feature on the end user page, and thus
> overcomes this limitation.****
>
> ****
>
> On Thu, Oct 3, 2013 at 1:50 PM, Erick Wellnitz <[email protected]>
> wrote:****
>
> I have a strange situation.****
>
> ****
>
> 3 Clusters. 2 on 9.1 and the other on 8.5 EMCC works except with users
> configured on the 8.5 cluster. The profile logs in then immediately logs
> out without an error message.****
>
> ****
>
> Any ideas would be greatly appreciated!****
>
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ****
>
>
>
> itevomcid ****
>
> ****
>
> ****
>
> _______________________________________________
> cisco-voip mailing list
> [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-voip****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ****
>
> ** **
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20131009/454d9568/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
------------------------------
End of cisco-voip Digest, Vol 120, Issue 9
******************************************
