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. Re: 7.15 Subscriber not syslogging to remote syslog server..
(Lelio Fulgenzi)
2. FW: phone background (Sean Knight)
3. Re: FW: phone background (Adel Abushaev)
4. Re: 7.15 Subscriber not syslogging to remote syslog server..
(Lelio Fulgenzi)
5. Re: UC 9.0 NFR (kiwi.voice)
6. Cisco 7912 phone registration issue (Faye Day)
7. Re: Cisco 7912 phone registration issue (Nate VanMaren)
8. Re: Cisco 7912 phone registration issue (Lelio Fulgenzi)
9. Re: Cisco 7912 phone registration issue (Jason Aarons (AM))
10. Re: Cisco 7912 phone registration issue (Nate VanMaren)
11. Re: phone background (Collins, Matthew)
12. DTMF Issue with one external number ([email protected])
13. Re: DTMF Issue with one external number (Derek Wyss)
14. Re: DTMF Issue with one external number
([email protected])
----------------------------------------------------------------------
Message: 1
Date: Mon, 15 Oct 2012 14:31:38 -0400 (EDT)
From: Lelio Fulgenzi <[email protected]>
To: Tim Reimers <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] 7.15 Subscriber not syslogging to remote
syslog server..
Message-ID:
<510878780.41166.1350325898352.javamail.r...@squeaky.cs.uoguelph.ca>
Content-Type: text/plain; charset="utf-8"
My subscribers seem to send lots of syslog data. Make sure there are no ACLs
blocking communications.
A simple test you can do is unplug a phone registered to the subscriber. It
should send something.
While on the sub, do a 'utils network capture dest <syslog_ip_addr>'. You
should see something. You can then start troubleshooting upstream.
Hopefully that helps.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Tim Reimers" <[email protected]>
To: [email protected]
Sent: Thursday, October 11, 2012 3:00:38 PM
Subject: [cisco-voip] 7.15 Subscriber not syslogging to remote syslog server..
Hi all ?
I?m trying to figure out some things using syslog.
I believe I?ve correctly configured remote syslog on both my pub/sub.
The publisher is correctly sending syslog data to the remote syslog server.
The subscriber never seems to send anything.
For the basics, the publisher is in subnet 192.168.200.X
Subscriber in subnet 192.168.201.X
Most phones are in some 10.16.X.Y subnet
All subnets are Vlan interfaces on one L3 switchstack, no firewalls or WAN
links, etc.
i.e, everything?s locally connected, so this isn?t about slow links,
access-control lists, or anything like that.
I?m seeing the below error in the syslog I do get from the CM1 (Publisher)
Device IP address shown below is the IP of the Subscriber itself.
cm1.2011-08-26.log:Aug 26 19:29:20 cm1 57: Aug 26 23:29:20.699 UTC :
%CCM_CALLMANAGER-CALLMANAGER-3-DeviceTransientConnection: Transient connection
attempt. Connecting Port:42653 Device name [Optional].: Device IP address
[Optional].:192.168.201.6 Device type. [Optional]:255 Reason Code [Optional].:6
Protocol.:SCCP IPAddressAttributes [Optional].:0 App ID:Cisco CallManager
Cluster ID:CM1-Cluster Node ID:CM1
I can?t figure out whether that mention of the Subscriber IP having a ?device
transient connection?
has anything to do with this or not.
What my ultimate goal is, is to figure out whether an ATA is registering and
sometimes falling offline and reregistering.
So I thought I?d just grep my syslogs looking for that event from that device.
Not so easy when most devices are registered to the Subscriber, and it ain?t
sayin? anything?
;-) Tim
_______________________________________________
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/20121015/bd6683c0/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 15 Oct 2012 14:34:42 -0400
From: "Sean Knight" <[email protected]>
To: <[email protected]>
Subject: [cisco-voip] FW: phone background
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
I was wondering how I edit List.xml in Linux? Because that needs to be
done in order for the pics to get pushed to the phones. And Restart
TFTP services.
From: Jason Aarons (AM) [mailto:[email protected]]
Sent: Monday, October 15, 2012 1:04 PM
To: Sean Knight
Subject: RE: phone background
If you search cisco.com for Customizing 7970 Background image, there is
a tech note with details (the 7970 screen has same resolution as
7945/65). The technote is under CME however the background image size
is the same and it has notes around CallManager/CME. The per phone type
is actually per screen resolution type (eg 320x212x16, etc)
From: [email protected]
[mailto:[email protected]] On Behalf Of Sean Knight
Sent: Monday, October 15, 2012 10:34 AM
To: [email protected]
Subject: [cisco-voip] phone background
Hello, I have CUCM 7.1 and I uploaded pictures with the correct format
to the TFTP server in the desktops directory and can see them uploaded.
7945/7965
320x212
80x53
Desktops/320x212x16/
So now it says that I need to edit the List.XML file. How do I do this?
And should I be able to make an .XML file for the particular phone type
or actually edit the existing List.XML file on the Linux server?
Any help is appreciated.
thanks
itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121015/9c9faf19/attachment-0001.html>
------------------------------
Message: 3
Date: Mon, 15 Oct 2012 11:37:53 -0700
From: Adel Abushaev <[email protected]>
To: Sean Knight <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] FW: phone background
Message-ID:
<CAEsuig9yqGfOvermjj2Ddo0=apvl-bx2r2valykuks8n6jk...@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
You could get the file from CUCM in admin CLI. You can then reupload the
List.XML using TFTP client in CUCM Administration web page in TFTP section.
You will need to restart TFTP process once you are done uploading to
refresh TFTP cache in memory.
On Mon, Oct 15, 2012 at 11:34 AM, Sean Knight <[email protected]> wrote:
> ** **
>
> I was wondering how I edit List.xml in Linux? Because that needs to be
> done in order for the pics to get pushed to the phones. And Restart TFTP
> services. ****
>
> ** **
>
> *From:* Jason Aarons (AM)
> [mailto:[email protected]<[email protected]>]
>
> *Sent:* Monday, October 15, 2012 1:04 PM
> *To:* Sean Knight
> *Subject:* RE: phone background****
>
> ** **
>
> ** **
>
> If you search cisco.com for Customizing 7970 Background image, there is a
> tech note with details (the 7970 screen has same resolution as 7945/65).
> The technote is under CME however the background image size is the same and
> it has notes around CallManager/CME. The per phone type is actually per
> screen resolution type (eg 320x212x16, etc)****
>
> ** **
>
> ** **
>
> *From:* [email protected] [
> mailto:[email protected]<[email protected]>]
> *On Behalf Of *Sean Knight
> *Sent:* Monday, October 15, 2012 10:34 AM
> *To:* [email protected]
> *Subject:* [cisco-voip] phone background****
>
> ** **
>
> ** **
>
> Hello, I have CUCM 7.1 and I uploaded pictures with the correct format to
> the TFTP server in the desktops directory and can see them uploaded. ****
>
> ** **
>
> 7945/7965****
>
> 320x212****
>
> 80x53****
>
> Desktops/320x212x16/****
>
> ** **
>
> ** **
>
> So now it says that I need to edit the List.XML file. How do I do this?
> And should I be able to make an .XML file for the particular phone type or
> actually edit the existing List.XML file on the Linux server?****
>
> ** **
>
> Any help is appreciated.****
>
> ** **
>
> ** **
>
> ** **
>
> thanks****
>
> ** **
>
>
>
> 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/20121015/e1883053/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 15 Oct 2012 14:54:04 -0400 (EDT)
From: Lelio Fulgenzi <[email protected]>
To: Tim Reimers <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] 7.15 Subscriber not syslogging to remote
syslog server..
Message-ID:
<609690913.41362.1350327244386.javamail.r...@squeaky.cs.uoguelph.ca>
Content-Type: text/plain; charset="utf-8"
here's an example of what you might/should see:
admin:utils network capture dest <syslog_ip_addr>
Executing command with options:
size=128 count=1000 interface=eth0
src= dest=<syslog_ip_addr> port=
ip=
14:41:12.939324 IP <sub_ip_addr -or- hostname>.32795 > <syslog_ip_addr -or-
hostname>: UDP, length 416
14:41:12.939538 IP <sub_ip_addr -or- hostname>.32790 > <syslog_ip_addr -or-
hostname>: UDP, length 405
14:50:46.422754 IP <sub_ip_addr -or- hostname>.32795 > <syslog_ip_addr -or-
hostname>: UDP, length 431
14:50:46.422935 IP <sub_ip_addr -or- hostname>.32790 > <syslog_ip_addr -or-
hostname>: UDP, length 420
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Lelio Fulgenzi" <[email protected]>
To: "Tim Reimers" <[email protected]>
Cc: [email protected]
Sent: Monday, October 15, 2012 2:31:38 PM
Subject: Re: [cisco-voip] 7.15 Subscriber not syslogging to remote syslog
server..
My subscribers seem to send lots of syslog data. Make sure there are no ACLs
blocking communications.
A simple test you can do is unplug a phone registered to the subscriber. It
should send something.
While on the sub, do a 'utils network capture dest <syslog_ip_addr>'. You
should see something. You can then start troubleshooting upstream.
Hopefully that helps.
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Tim Reimers" <[email protected]>
To: [email protected]
Sent: Thursday, October 11, 2012 3:00:38 PM
Subject: [cisco-voip] 7.15 Subscriber not syslogging to remote syslog server..
Hi all ?
I?m trying to figure out some things using syslog.
I believe I?ve correctly configured remote syslog on both my pub/sub.
The publisher is correctly sending syslog data to the remote syslog server.
The subscriber never seems to send anything.
For the basics, the publisher is in subnet 192.168.200.X
Subscriber in subnet 192.168.201.X
Most phones are in some 10.16.X.Y subnet
All subnets are Vlan interfaces on one L3 switchstack, no firewalls or WAN
links, etc.
i.e, everything?s locally connected, so this isn?t about slow links,
access-control lists, or anything like that.
I?m seeing the below error in the syslog I do get from the CM1 (Publisher)
Device IP address shown below is the IP of the Subscriber itself.
cm1.2011-08-26.log:Aug 26 19:29:20 cm1 57: Aug 26 23:29:20.699 UTC :
%CCM_CALLMANAGER-CALLMANAGER-3-DeviceTransientConnection: Transient connection
attempt. Connecting Port:42653 Device name [Optional].: Device IP address
[Optional].:192.168.201.6 Device type. [Optional]:255 Reason Code [Optional].:6
Protocol.:SCCP IPAddressAttributes [Optional].:0 App ID:Cisco CallManager
Cluster ID:CM1-Cluster Node ID:CM1
I can?t figure out whether that mention of the Subscriber IP having a ?device
transient connection?
has anything to do with this or not.
What my ultimate goal is, is to figure out whether an ATA is registering and
sometimes falling offline and reregistering.
So I thought I?d just grep my syslogs looking for that event from that device.
Not so easy when most devices are registered to the Subscriber, and it ain?t
sayin? anything?
;-) Tim
_______________________________________________
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/20121015/13080b2d/attachment-0001.html>
------------------------------
Message: 5
Date: Tue, 16 Oct 2012 03:09:55 +0800
From: "kiwi.voice" <[email protected]>
To: [email protected], [email protected]
Subject: Re: [cisco-voip] UC 9.0 NFR
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
It was there earlier last week, I even screenshot the final step with the total
cost for approval.
Now, it's gone somehow. The site was down for quite a while when I wanted to
order it after getting approval. When it returns, all the payable items are
missing. Left with those free items.?"Heim, Dennis" <[email protected]>
wrote:I saw the the 9.0 NFR kit is supposed to be orderable now. However, it is
now showing up in the marketplace
(http://www.cisco.com/pcgi-bin/marketplace/welcome.pl) . Has it just not been
added to the store yet?
?
Thanks,
?
Dennis Heim
Sr. UC Engineer
World Wide Technology
Office: 314.212.1814
Email: [email protected]
www.wwt.com
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121016/5c7583c8/attachment-0001.html>
------------------------------
Message: 6
Date: Mon, 15 Oct 2012 16:50:56 -0400
From: Faye Day <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] Cisco 7912 phone registration issue
Message-ID:
<7e87f2033a8ba04fb813beea70b4828b12b32e1...@wcoexchange07.wilson-co.com>
Content-Type: text/plain; charset="us-ascii"
We are running CM 7.1.5 (recently upgraded from 7.1.2). We've always used SCCP.
I have 22 of the Cisco 7912 one-line phones currently registered in my system
that were legacy items when we did the upgrade. Today, I tried to add a
new/off-the-shelf/never been plugged in since purchased in 2008 7912 to my call
manager but it won't register. Additionally, the phone display shows auto-reg
(which we've never used) in the upper right corner, and the network
configuration info on the phone shows odd items - host name with gk in front of
it, time zone 20 or 17 (varies on reboot).
The SIP configuration item is fully populated with proxy, user id auto-reg,
password, SIP port number, register with proxy: Yes, etc.
I've tried erasing the config, factory reset, and every tip I can find anywhere
but it still won't lose the SIP info and register with Call Manager. Can anyone
give me some ideas of what to do with this phone (other than trash it), please?
Thanks,
Faye Day
Wilson County Technology Services
Assistant Director
(252) 206-1024
(252) 265-5960 fax
"The Greatness of a nation and its moral progress can be judged by the way its
animals are treated."
Mahatma Gandhi
Opinions in this message may not represent the policy of Wilson County. Email
correspondence to and from me, in connection with the transaction of public
business, is subject to the North Carolina Public Records Law and may be
disclosed to third parties.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121015/fba7a7ed/attachment-0001.html>
------------------------------
Message: 7
Date: Mon, 15 Oct 2012 22:29:48 +0000
From: Nate VanMaren <[email protected]>
To: Faye Day <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Faye,
I feel reluctant to share this, because it took me so very much time to figure
it out. TAC was not very helpful, and there are some guides on the internet
that are not very good.
But since I am a really nice guy and hopefully it will be paid forward:
The best #1 way to fix this! (assuming you have auto-registration enabled)
In you device defaults for the SIP 7912 change it to the same exact firmware
that you have as the default for your SCCP 7912. If you're like normal people
you'll never want a SIP 7912 to this will not be a problem.
[cid:[email protected]]
Then delete all of the SIP 7912 devices, and keep deleting them until they
don't pop up.
Thanks
-Nate
From: [email protected]
[mailto:[email protected]] On Behalf Of Faye Day
Sent: Monday, October 15, 2012 2:51 PM
To: [email protected]
Subject: [cisco-voip] Cisco 7912 phone registration issue
We are running CM 7.1.5 (recently upgraded from 7.1.2). We've always used SCCP.
I have 22 of the Cisco 7912 one-line phones currently registered in my system
that were legacy items when we did the upgrade. Today, I tried to add a
new/off-the-shelf/never been plugged in since purchased in 2008 7912 to my call
manager but it won't register. Additionally, the phone display shows auto-reg
(which we've never used) in the upper right corner, and the network
configuration info on the phone shows odd items - host name with gk in front of
it, time zone 20 or 17 (varies on reboot).
The SIP configuration item is fully populated with proxy, user id auto-reg,
password, SIP port number, register with proxy: Yes, etc.
I've tried erasing the config, factory reset, and every tip I can find anywhere
but it still won't lose the SIP info and register with Call Manager. Can anyone
give me some ideas of what to do with this phone (other than trash it), please?
Thanks,
Faye Day
Wilson County Technology Services
Assistant Director
(252) 206-1024
(252) 265-5960 fax
"The Greatness of a nation and its moral progress can be judged by the way its
animals are treated."
Mahatma Gandhi
Opinions in this message may not represent the policy of Wilson County. Email
correspondence to and from me, in connection with the transaction of public
business, is subject to the North Carolina Public Records Law and may be
disclosed to third parties.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121015/bebd0d62/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7334 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121015/bebd0d62/attachment-0001.png>
------------------------------
Message: 8
Date: Mon, 15 Oct 2012 22:36:27 -0400 (EDT)
From: Lelio Fulgenzi <[email protected]>
To: Nate VanMaren <[email protected]>
Cc: [email protected]
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
Message-ID:
<537183924.42931.1350354987730.javamail.r...@squeaky.cs.uoguelph.ca>
Content-Type: text/plain; charset="utf-8"
interesting approach.
there was a thread a while back regarding factory defaults that may have
something to do with this. if i recall correctly, basically, the last firmware
loaded is what the system uses for factory resets. if you want SCCP to be the
factory reset load, then you have to load that onto the TFTP server. there's
also something about bridged firmware versions. so if these phones were never
used, they might not be able to be upgraded to the latest version necessary for
v7.1.5.
i think you can also edit an XML file on the tftp server to force the default
to SCCP.
if you search the archives, cisco-voip.markmail.org, you might find some
additional information to help.
lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
----- Original Message -----
From: "Nate VanMaren" <[email protected]>
To: "Faye Day" <[email protected]>, [email protected]
Sent: Monday, 15 October, 2012 6:29:48 PM
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
Faye,
I feel reluctant to share this, because it took me so very much time to figure
it out. TAC was not very helpful, and there are some guides on the internet
that are not very good.
But since I am a really nice guy and hopefully it will be paid forward:
The best #1 way to fix this! (assuming you have auto-registration enabled)
In you device defaults for the SIP 7912 change it to the same exact firmware
that you have as the default for your SCCP 7912. If you?re like normal people
you?ll never want a SIP 7912 to this will not be a problem.
Then delete all of the SIP 7912 devices, and keep deleting them until they
don?t pop up.
Thanks
-Nate
From: [email protected]
[mailto:[email protected]] On Behalf Of Faye Day
Sent: Monday, October 15, 2012 2:51 PM
To: [email protected]
Subject: [cisco-voip] Cisco 7912 phone registration issue
We are running CM 7.1.5 (recently upgraded from 7.1.2). We?ve always used SCCP.
I have 22 of the Cisco 7912 one-line phones currently registered in my system
that were legacy items when we did the upgrade. Today, I tried to add a
new/off-the-shelf/never been plugged in since purchased in 2008 7912 to my call
manager but it won?t register. Additionally, the phone display shows auto-reg
(which we?ve never used) in the upper right corner, and the network
configuration info on the phone shows odd items ? host name with gk in front of
it, time zone 20 or 17 (varies on reboot).
The SIP configuration item is fully populated with proxy, user id auto-reg,
password, SIP port number, register with proxy: Yes, etc.
I?ve tried erasing the config, factory reset, and every tip I can find anywhere
but it still won?t lose the SIP info and register with Call Manager. Can anyone
give me some ideas of what to do with this phone (other than trash it), please?
Thanks,
Faye Day
Wilson County Technology Services
Assistant Director
(252) 206-1024
(252) 265-5960 fax
"The Greatness of a nation and its moral progress can be judged by the way its
animals are treated."
Mahatma Gandhi
Opinions in this message may not represent the policy of Wilson County. Email
correspondence to and from me, in connection with the transaction of public
business, is subject to the North Carolina Public Records Law and may be
disclosed to third parties.
_______________________________________________
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/20121015/1ddea02a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7334 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121015/1ddea02a/attachment-0001.png>
------------------------------
Message: 9
Date: Mon, 15 Oct 2012 23:07:56 -0400
From: "Jason Aarons (AM)" <[email protected]>
To: Lelio Fulgenzi <[email protected]>, Nate VanMaren
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
Message-ID:
<4e38db0a1959b04c8c83edcf069b53ed0d2a21c...@usispclexdb01.na.didata.local>
Content-Type: text/plain; charset="utf-8"
Whatever the last cop file installed (sccp vs sip) will determine if default
load is sccp or sip for that model.
From: [email protected]
[mailto:[email protected]] On Behalf Of Lelio Fulgenzi
Sent: Monday, October 15, 2012 10:36 PM
To: Nate VanMaren
Cc: [email protected]
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
interesting approach.
there was a thread a while back regarding factory defaults that may have
something to do with this. if i recall correctly, basically, the last firmware
loaded is what the system uses for factory resets. if you want SCCP to be the
factory reset load, then you have to load that onto the TFTP server. there's
also something about bridged firmware versions. so if these phones were never
used, they might not be able to be upgraded to the latest version necessary for
v7.1.5.
i think you can also edit an XML file on the tftp server to force the default
to SCCP.
if you search the archives, cisco-voip.markmail.org, you might find some
additional information to help.
lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
________________________________
From: "Nate VanMaren" <[email protected]>
To: "Faye Day" <[email protected]>, [email protected]
Sent: Monday, 15 October, 2012 6:29:48 PM
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
Faye,
I feel reluctant to share this, because it took me so very much time to figure
it out. TAC was not very helpful, and there are some guides on the internet
that are not very good.
But since I am a really nice guy and hopefully it will be paid forward:
The best #1 way to fix this! (assuming you have auto-registration enabled)
In you device defaults for the SIP 7912 change it to the same exact firmware
that you have as the default for your SCCP 7912. If you?re like normal people
you?ll never want a SIP 7912 to this will not be a problem.
[cid:[email protected]]
Then delete all of the SIP 7912 devices, and keep deleting them until they
don?t pop up.
Thanks
-Nate
From: [email protected]
[mailto:[email protected]] On Behalf Of Faye Day
Sent: Monday, October 15, 2012 2:51 PM
To: [email protected]
Subject: [cisco-voip] Cisco 7912 phone registration issue
We are running CM 7.1.5 (recently upgraded from 7.1.2). We?ve always used SCCP.
I have 22 of the Cisco 7912 one-line phones currently registered in my system
that were legacy items when we did the upgrade. Today, I tried to add a
new/off-the-shelf/never been plugged in since purchased in 2008 7912 to my call
manager but it won?t register. Additionally, the phone display shows auto-reg
(which we?ve never used) in the upper right corner, and the network
configuration info on the phone shows odd items ? host name with gk in front of
it, time zone 20 or 17 (varies on reboot).
The SIP configuration item is fully populated with proxy, user id auto-reg,
password, SIP port number, register with proxy: Yes, etc.
I?ve tried erasing the config, factory reset, and every tip I can find anywhere
but it still won?t lose the SIP info and register with Call Manager. Can anyone
give me some ideas of what to do with this phone (other than trash it), please?
Thanks,
Faye Day
Wilson County Technology Services
Assistant Director
(252) 206-1024
(252) 265-5960 fax
"The Greatness of a nation and its moral progress can be judged by the way its
animals are treated."
Mahatma Gandhi
Opinions in this message may not represent the policy of Wilson County. Email
correspondence to and from me, in connection with the transaction of public
business, is subject to the North Carolina Public Records Law and may be
disclosed to third parties.
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121015/5147a41b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7334 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121015/5147a41b/attachment-0001.png>
------------------------------
Message: 10
Date: Tue, 16 Oct 2012 03:36:26 +0000
From: Nate VanMaren <[email protected]>
To: "Jason Aarons (AM)" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
Message-ID: <[email protected]>
Content-Type: text/plain; charset="windows-1252"
Correct, what ever the last image on the phone was it will continue to download
that. That is why you tell it to download the SCCP firmware when it registers
as sip.
We've been setting the default protocol for auto registration to SIP on our
clusters. And we hand a bunch of these decide to get SIP firmware.
The problem is with the 7912 it doesn't use the same XML configuration filename
between the two protocols. Most of the other phones (I think just the 7905)
use the same config file name so they'll just switch back to the correct
firmware.
Thanks,
-Nate
Sent from my iPhone
On Oct 15, 2012, at 9:08 PM, "Jason Aarons (AM)"
<[email protected]<mailto:[email protected]>> wrote:
Whatever the last cop file installed (sccp vs sip) will determine if default
load is sccp or sip for that model.
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Lelio Fulgenzi
Sent: Monday, October 15, 2012 10:36 PM
To: Nate VanMaren
Cc: [email protected]<mailto:[email protected]>
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
interesting approach.
there was a thread a while back regarding factory defaults that may have
something to do with this. if i recall correctly, basically, the last firmware
loaded is what the system uses for factory resets. if you want SCCP to be the
factory reset load, then you have to load that onto the TFTP server. there's
also something about bridged firmware versions. so if these phones were never
used, they might not be able to be upgraded to the latest version necessary for
v7.1.5.
i think you can also edit an XML file on the tftp server to force the default
to SCCP.
if you search the archives,
cisco-voip.markmail.org<http://cisco-voip.markmail.org>, you might find some
additional information to help.
lelio
---
Lelio Fulgenzi, B.A.
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Cooking with unix is easy. You just sed it and forget it.
- LFJ (with apologies to Mr. Popeil)
________________________________
From: "Nate VanMaren"
<[email protected]<mailto:[email protected]>>
To: "Faye Day" <[email protected]<mailto:[email protected]>>,
[email protected]<mailto:[email protected]>
Sent: Monday, 15 October, 2012 6:29:48 PM
Subject: Re: [cisco-voip] Cisco 7912 phone registration issue
Faye,
I feel reluctant to share this, because it took me so very much time to figure
it out. TAC was not very helpful, and there are some guides on the internet
that are not very good.
But since I am a really nice guy and hopefully it will be paid forward:
The best #1 way to fix this! (assuming you have auto-registration enabled)
In you device defaults for the SIP 7912 change it to the same exact firmware
that you have as the default for your SCCP 7912. If you?re like normal people
you?ll never want a SIP 7912 to this will not be a problem.
<image001.png>
Then delete all of the SIP 7912 devices, and keep deleting them until they
don?t pop up.
Thanks
-Nate
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Faye Day
Sent: Monday, October 15, 2012 2:51 PM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] Cisco 7912 phone registration issue
We are running CM 7.1.5 (recently upgraded from 7.1.2). We?ve always used SCCP.
I have 22 of the Cisco 7912 one-line phones currently registered in my system
that were legacy items when we did the upgrade. Today, I tried to add a
new/off-the-shelf/never been plugged in since purchased in 2008 7912 to my call
manager but it won?t register. Additionally, the phone display shows auto-reg
(which we?ve never used) in the upper right corner, and the network
configuration info on the phone shows odd items ? host name with gk in front of
it, time zone 20 or 17 (varies on reboot).
The SIP configuration item is fully populated with proxy, user id auto-reg,
password, SIP port number, register with proxy: Yes, etc.
I?ve tried erasing the config, factory reset, and every tip I can find anywhere
but it still won?t lose the SIP info and register with Call Manager. Can anyone
give me some ideas of what to do with this phone (other than trash it), please?
Thanks,
Faye Day
Wilson County Technology Services
Assistant Director
(252) 206-1024
(252) 265-5960 fax
"The Greatness of a nation and its moral progress can be judged by the way its
animals are treated."
Mahatma Gandhi
Opinions in this message may not represent the policy of Wilson County. Email
correspondence to and from me, in connection with the transaction of public
business, is subject to the North Carolina Public Records Law and may be
disclosed to third parties.
_______________________________________________
cisco-voip mailing list
[email protected]<mailto:[email protected]>
https://puck.nether.net/mailman/listinfo/cisco-voip
itevomcid
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121016/12fb127b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7334 bytes
Desc: image001.png
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121016/12fb127b/attachment-0001.png>
------------------------------
Message: 11
Date: Tue, 16 Oct 2012 10:16:23 +0100
From: "Collins, Matthew" <[email protected]>
To: "'Sean Knight'" <[email protected]>, "[email protected]"
<[email protected]>
Subject: Re: [cisco-voip] phone background
Message-ID:
<693f4a831363c74fab2cf018128caa34842e71f...@erepex40.practice.linklaters.net>
Content-Type: text/plain; charset="us-ascii"
Hi Sean,
Attached is a doc I had to create for our internal IT support guys. This was
specifically for a 7970 and on CUCM 6.1 but should still be the same.
From: [email protected]
[mailto:[email protected]] On Behalf Of Sean Knight
Sent: 15 October 2012 19:35
To: [email protected]
Subject: [cisco-voip] FW: phone background
I was wondering how I edit List.xml in Linux? Because that needs to be done in
order for the pics to get pushed to the phones. And Restart TFTP services.
From: Jason Aarons (AM) [mailto:[email protected]]
Sent: Monday, October 15, 2012 1:04 PM
To: Sean Knight
Subject: RE: phone background
If you search cisco.com for Customizing 7970 Background image, there is a tech
note with details (the 7970 screen has same resolution as 7945/65). The
technote is under CME however the background image size is the same and it has
notes around CallManager/CME. The per phone type is actually per screen
resolution type (eg 320x212x16, etc)
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Sean Knight
Sent: Monday, October 15, 2012 10:34 AM
To: [email protected]<mailto:[email protected]>
Subject: [cisco-voip] phone background
Hello, I have CUCM 7.1 and I uploaded pictures with the correct format to the
TFTP server in the desktops directory and can see them uploaded.
7945/7965
320x212
80x53
Desktops/320x212x16/
So now it says that I need to edit the List.XML file. How do I do this? And
should I be able to make an .XML file for the particular phone type or actually
edit the existing List.XML file on the Linux server?
Any help is appreciated.
thanks
itevomcid
________________________________
Any business communication, sent by or on behalf of Linklaters LLP or one of
its affiliated firms or other entities (together "Linklaters"), is confidential
and may be privileged or otherwise protected. If you receive it in error please
inform us and then delete it from your system. You should not copy it or
disclose its contents to anyone. Messages sent to and from Linklaters may be
monitored to ensure compliance with internal policies and to protect our
business. Emails are not secure and cannot be guaranteed to be error free.
Anyone who communicates with us by email is taken to accept these risks.
Linklaters LLP is a limited liability partnership registered in England and
Wales with registered number OC326345. It is a law firm authorised and
regulated by the Solicitors Regulation Authority (www.sra.org.uk). The term
partner in relation to Linklaters LLP is used to refer to a member of
Linklaters LLP or an employee or consultant of Linklaters LLP or any of its
affiliated firms or entities with equivalent standing and qualifications.
Please refer to www.linklaters.com/regulation for important information on our
regulatory position.
A list of Linklaters LLP members together with a list of those non-members who
are designated as partners and their professional qualifications, may be
inspected at our registered office, One Silk Street, London EC2Y 8HQ and such
persons are either solicitors, registered foreign lawyers or European lawyers.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121016/469e82ca/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Creating a Background imange.pdf
Type: application/pdf
Size: 137805 bytes
Desc: Creating a Background imange.pdf
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121016/469e82ca/attachment-0001.pdf>
------------------------------
Message: 12
Date: Tue, 16 Oct 2012 12:25:36 +0000
From: [email protected]
To: "[email protected]" <[email protected]>
Subject: [cisco-voip] DTMF Issue with one external number
Message-ID:
<255f57bb43f894468da6bd4f2f5dd1ce6425c...@rstn-s-mbx01.net.its.l-3com.com>
Content-Type: text/plain; charset="us-ascii"
Hey guys,
We have an odd issue going on with DTMF. Below is the path to the PSTN.
CUCM <-> h.323 Gateway <-> SIP Provider.
The problem is that when we dial into this one external number and press 1 to
select option 1, it doesn't seem to accept the digit. If we dial into that
same number from anywhere else, it works fine. Having said that, I can dial
into other numbers from the system and have no issue at all with dtmf. Any
ideas of what this issue is?
Thanks,
Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://puck.nether.net/pipermail/cisco-voip/attachments/20121016/24dffa94/attachment-0001.html>
------------------------------
Message: 13
Date: Tue, 16 Oct 2012 07:40:24 -0500
From: Derek Wyss <[email protected]>
To: [email protected]
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] DTMF Issue with one external number
Message-ID:
<calh9dxe+h3z3ztfym9qcsqgln2kaby-0kxvvmte_b0+atzw...@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
What does your SDP show using debug ccsip all?
I've ran into this before where the provider had a different RTP map to
their IP customers vs their ISDN customers. What I had to do was create
separate dialpeers for those numbers with a different RTP map. See example
below:
v=0
o=CiscoSystemsSIP-GW-UserAgent 9601 2828 IN IP4 X.X.X.X
s=SIP Call
c=IN IP4 X.X.X.X
t=0 0
m=audio 16384 RTP/AVP 18 0 101
c=IN IP4 10.8.2.4
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:0 PCMU/8000
a=rtpmap:101 X-NSE/8000
a=fmtp:101 192-194
v=0
o=Sonus_UAC 16372 5325 IN IP4 X.X.X.X
s=SIP Media Capabilities
c=IN IP4 X.X.X.X
t=0 0
m=audio 23002 RTP/AVP 18 0 100
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:100 telephone-event/8000
a=fmtp:100 0-15
a=sendrecv
a=maxptime:20
As mentioned above the yellow highlighted portion of the SDP?s is where we
can see a mismatch in our payload type. You can see the telco is sending
100 and we are sending 101. To resolve this issue you have to remap the
rtp payload type for signaling and telephony events. Here is the commands
I had to run to send 100 as our NTE to match what the provider was
expecting?
Lincoln-VG01(config-dial-peer)#rtp payload-type nse 98
Lincoln-VG01(config-dial-peer)#rtp payload-type nte 100
Lincoln-VG01(config-dial-peer)#rtp payload-type nse 101
Because the signaling is defaulted at nte 101 and nse 100 you have to
remove 100 from nse by assigning it a random unused value before you can
assign 100 to nte. See this image for the default reserved values:
https://communities.cisco.com/servlet/JiveServlet/downloadImage/2-5295-2243/450-185/defaultpayloadtype.png
Hope this helps,
Derek
On Tue, Oct 16, 2012 at 7:25 AM, <[email protected]> wrote:
> Hey guys,****
>
> ** **
>
> We have an odd issue going on with DTMF. Below is the path to the PSTN.
> ****
>
> ** **
>
> CUCM <-> h.323 Gateway <-> SIP Provider.****
>
> ** **
>
> The problem is that when we dial into this one external number and press 1
> to select option 1, it doesn?t seem to accept the digit. If we dial into
> that same number from anywhere else, it works fine. Having said that, I
> can dial into other numbers from the system and have no issue at all with
> dtmf. Any ideas of what this issue is?****
>
> ** **
>
> Thanks,****
>
> Bill****
>
> ** **
>
> ** **
>
> _______________________________________________
> 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/20121016/76df6700/attachment-0001.html>
------------------------------
Message: 14
Date: Tue, 16 Oct 2012 13:49:03 +0000
From: [email protected]
To: Derek Wyss <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [cisco-voip] DTMF Issue with one external number
Message-ID:
<255f57bb43f894468da6bd4f2f5dd1ce6425c...@rstn-s-mbx01.net.its.l-3com.com>
Content-Type: text/plain; charset="us-ascii"
Thanks for the info. I will do a debug on this and see what I get. Also, even
on the numbers I call that work, it appears the router is sending double
digits. If you look below, it sent * twice even though I only pressed it once.
Oct 16 07:36:35.343: //137015/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_begin:
Consume mask is not set. Relaying Digit * to dstCallId 0x21738
Oct 16 07:36:35.343:
//137015/xxxxxxxxxxxx/CCAPI/cc_relay_digit_begin_for_3way_conference:
Check DTMF relay digit begin for 3way conf
Oct 16 07:36:35.419: //137015/xxxxxxxxxxxx/CCAPI/cc_api_call_digit_end
Consume mask is not set. Relaying Digit * to dstCallId 0x21738
Oct 16 07:36:35.419:
//137015/xxxxxxxxxxxx/CCAPI/cc_relay_digit_end_for_3way_conference:
Check DTMF relay digit end for 3way conf
-Bill
From: Derek Wyss [mailto:[email protected]]
Sent: Tuesday, October 16, 2012 8:40 AM
To: Hendrix, George (Bill) @ NSS - STRATIS
Cc: [email protected]
Subject: Re: [cisco-voip] DTMF Issue with one external number
What does your SDP show using debug ccsip all?
I've ran into this before where the provider had a different RTP map to their
IP customers vs their ISDN customers. What I had to do was create separate
dialpeers for those numbers with a different RTP map. See example below:
v=0
o=CiscoSystemsSIP-GW-UserAgent 9601 2828 IN IP4 X.X.X.X
s=SIP Call
c=IN IP4 X.X.X.X
t=0 0
m=audio 16384 RTP/AVP 18 0 101
c=IN IP4 10.8.2.4
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:0 PCMU/8000
a=rtpmap:101 X-NSE/8000
a=fmtp:101 192-194
v=0
o=Sonus_UAC 16372 5325 IN IP4 X.X.X.X
s=SIP Media Capabilities
c=IN IP4 X.X.X.X
t=0 0
m=audio 23002 RTP/AVP 18 0 100
a=rtpmap:18 G729/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:100 telephone-event/8000
a=fmtp:100 0-15
a=sendrecv
a=maxptime:20
As mentioned above the yellow highlighted portion of the SDP's is where we can
see a mismatch in our payload type. You can see the telco is sending 100 and
we are sending 101. To resolve this issue you have to remap the rtp payload
type for signaling and telephony events. Here is the commands I had to run to
send 100 as our NTE to match what the provider was expecting...
Lincoln-VG01(config-dial-peer)#rtp payload-type nse 98
Lincoln-VG01(config-dial-peer)#rtp payload-type nte 100
Lincoln-VG01(config-dial-peer)#rtp payload-type nse 101
Because the signaling is defaulted at nte 101 and nse 100 you have to remove
100 from nse by assigning it a random unused value before you can assign 100 to
nte. See this image for the default reserved values:
https://communities.cisco.com/servlet/JiveServlet/downloadImage/2-5295-2243/450-185/defaultpayloadtype.png
Hope this helps,
Derek
On Tue, Oct 16, 2012 at 7:25 AM,
<[email protected]<mailto:[email protected]>> wrote:
Hey guys,
We have an odd issue going on with DTMF. Below is the path to the PSTN.
CUCM <-> h.323 Gateway <-> SIP Provider.
The problem is that when we dial into this one external number and press 1 to
select option 1, it doesn't seem to accept the digit. If we dial into that
same number from anywhere else, it works fine. Having said that, I can dial
into other numbers from the system and have no issue at all with dtmf. Any
ideas of what this issue is?
Thanks,
Bill
_______________________________________________
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/20121016/4b188fff/attachment-0001.html>
------------------------------
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip
End of cisco-voip Digest, Vol 108, Issue 17
*******************************************
