AW: [cisco-voip] Upgrading 7960G firmware with CME 3.3
Lawrence E. Bakst
ml at iridescent.org
Sun Sep 4 20:49:21 EDT 2005
Wes/Ryan,
I want to thank Wes for the "magic-file" he sent me. Both phones are now up and running and have been upgraded to SCCP V 5.0.6 (what comes with CME 3.3) and have successfully registered with CME 3.3. I owe you big time. It's looks like my only other choice would have been to use the "OS79XX.txt" mechanism, let it run overnight, and hope for a perfect load.
I want to thank Ryan for offering to make .cnf files for me. That kind of offer is really appreciated. Also, thanks for the link which describes the boot process and for telling me that the old loader only checks the checksum after the entire TFTP load. That's critical info. I couldn't get to the link you posted because I am not a registered partner. However that's something I am considering. I'll post a separate email about that.
Now the real fun begins. I've got more phones on the way and probably a new router as well, so I can run Unity Express.
Thanks for all the great support. This is a great list. I've been reading it for over a year and I've learned a great deal.
Thanks to all again.
Best,
leb
At 12:57 PM -0400 9/4/05, Wes Sisk wrote:
>Content-Type: text/plain; format=flowed
>X-MIME-Autoconverted: from 8bit to quoted-printable by av-tac-rtp.cisco.com id j84H08i00927
>
>Lawrence,
>
>Looked around and found this from a previous case:
>
>"The logs were showing that the IP Phone was looking for load P00303020209.bin
>We placed this load in flash, added a tptf-server to the config for it and reset the phone
>in web admin. The phones upgraded. "
>
>Attached is the file in zip format. unzip and drop in your flash. configure the router to serve it by TFTP. Let me know how it goes.
>
>/Wes
>
>
>
>Lawrence E. Bakst wrote:
>
>>At 10:08 PM -0400 9/3/05, Jim McBurnett wrote:
>>
>>>Lawrence,
>>>We had so many problems with 3.3 we went back to 3.2.1.
>>>I had a TAC case open and they reccomended that..
>>>Have you lab tested this?
>>>
>>>
>>
>>Well I'm just trying to set up a lab. CCE isn't the real issue here, it's the old firmware loader on the phones and the fact that CCE can't generate .cnf files, just .cnf.xml files.
>>
>>However, thanks for the tip. Once the phones are up and running we'll see how much trouble CCE 3.3 gives me.
>>
>>Is there a certain area of 3.3 that was causing you the problems?
>>
>>Best,
>>
>>leb
>>
>>
>>>Later,
>>>Jim
>>>
>>>-----Original Message-----
>>>From: Lawrence E. Bakst [mailto:ml at iridescent.org]
>>>Sent: Saturday, September 03, 2005 9:41 PM
>>>To: Wes Sisk
>>>Cc: Jim McBurnett; Bernhard Albler; cisco-voip at puck.nether.net
>>>Subject: Re: AW: [cisco-voip] Upgrading 7960G firmware with CME 3.3
>>>
>>>Are you 100% sure that's true for all revs of firmware?
>>>
>>>Again, here are the files the phone is looking for as seen from the 3640 with "debug tftp events":
>>>
>>>00:05:41: TFTP: Looking for OS79XX.TXT
>>>00:05:41: TFTP: Opened flash:OS79XX.TXT, fd 0, size 16 for process 143
>>>00:05:41: TFTP: Finished flash:OS79XX.TXT, time 00:00:00 for process 143
>>>00:05:41: TFTP: Looking for SEP000DED9137XX.cnf
>>>00:05:41: TFTP: Looking for SEPDefault.cnf
>>>00:05:42: TFTP: Looking for SEPDefault.cnf
>>>00:05:43: TFTP: Opened system:/its/SEPDEFAULT.cnf, fd 0, size 57 for process 152
>>>00:05:44: TFTP: Finished system:/its/SEPDEFAULT.cnf, time 00:00:00 for process 152
>>>
>>>It's the same if "OS79XX.TXT" is removed, except for course that file isn't loaded.
>>>
>>>Best,
>>>
>>>leb
>>>
>>>
>>>At 8:22 PM -0400 9/3/05, Wes Sisk wrote:
>>>
>>>
>>>>The 79xx phones parse the load from 1 of 2 files: SEP<mac>.cnf.xml or XMLDefault.cnf.xml You will need one of these files present with the phone running the SCCP load to have it take a new load. The tags look like:
>>>>
>>>>XMLDefault.cnf.xml:
>>>><Default>
>>>><callManagerGroup>
>>>><members>
>>>><member priority="0">
>>>><callManager>
>>>><ports>
>>>><analogAccessPort>2002</analogAccessPort>
>>>><digitalAccessPort>2001</digitalAccessPort>
>>>><ethernetPhonePort>2000</ethernetPhonePort>
>>>><mgcpPorts>
>>>><listen>2427</listen>
>>>><keepAlive>2428</keepAlive>
>>>></mgcpPorts>
>>>></ports>
>>>><processNodeName>172.18.110.96</processNodeName>
>>>></callManager>
>>>></member>
>>>></members>
>>>></callManagerGroup>
>>>><loadInformation9 model="Cisco 7935">P00503010900</loadInformation9>
>>>><loadInformation4 model="Cisco 12 S">P00203010100</loadInformation4>
>>>><loadInformation3 model="Cisco 12 SP">P00203010100</loadInformation3>
>>>><loadInformation2 model="Cisco 12 SP+">P00203010100</loadInformation2>
>>>><loadInformation1 model="Cisco 30 SP+">P00103010100</loadInformation1>
>>>><loadInformation5 model="Cisco 30 VIP">P00203010100</loadInformation5>
>>>><loadInformation30 model="Analog Access">A001D031</loadInformation30>
>>>><loadInformation47 model="Analog Access
>>>>WS-X6624">A00204000010</loadInformation47>
>>>><loadInformation51 model="Conference Bridge
>>>>Hardware">C00104000001</loadInformation51>
>>>><loadInformation43 model="Digital Access
>>>>WS-X6608">D00404000019</loadInformation43>
>>>><loadInformation42 model="Digital
>>>>Access+">D00303010033</loadInformation42>
>>>><loadInformation7 model="Cisco 7960">P00307020200</loadInformation7>
>>>>
>>>>
>>>>SEP<mac>.cnf.xml:
>>>>
>>>><device xsi:type="axl:XIPPhone" ctiid="179854386"
>>>>uuid="{86663B64-329A-4F31-8A70-89727C674575}">
>>>><devicePool uuid="{1B1B9EB6-7803-11D3-BDF0-00108302EAD1}">
>>>><name>Default</name>
>>>><dateTimeSetting uuid="{9EC4850A-7748-11D3-BDF0-00108302EAD1}">
>>>><name>RTP</name>
>>>><dateTemplate>D.M.Y</dateTemplate>
>>>><timeZone>Eastern Standard/Daylight Time</timeZone> </dateTimeSetting>
>>>><callManagerGroup> <members> <member priority="0"> <callManager>
>>>><ports> <analogAccessPort>2002</analogAccessPort>
>>>><digitalAccessPort>2001</digitalAccessPort>
>>>><ethernetPhonePort>2000</ethernetPhonePort>
>>>><mgcpPorts>
>>>><listen>2427</listen>
>>>><keepAlive>2428</keepAlive>
>>>></mgcpPorts>
>>>></ports>
>>>><processNodeName>172.18.110.96</processNodeName>
>>>></callManager>
>>>></member>
>>>></members>
>>>></callManagerGroup>
>>>><srstInfo uuid="{CD241E11-4A58-4D3D-9661-F06C912A18A3}">
>>>><name>Disable</name>
>>>><srstOption>Disable</srstOption>
>>>><userModifiable>false</userModifiable>
>>>><ipAddr1></ipAddr1>
>>>><port1>2000</port1>
>>>><ipAddr2></ipAddr2>
>>>><port2>2000</port2>
>>>><ipAddr3></ipAddr3>
>>>><port3>2000</port3>
>>>><isSecure>false</isSecure>
>>>></srstInfo>
>>>><mlppDomainId>-1</mlppDomainId>
>>>><mlppIndicationStatus>Default</mlppIndicationStatus>
>>>><preemption>Default</preemption>
>>>><connectionMonitorDuration>120</connectionMonitorDuration>
>>>></devicePool>
>>>><loadInformation>P00307020200</loadInformation>
>>>>
>>>>/Wes
>>>>
>>>>Lawrence E. Bakst wrote:
>>>>
>>>>
>>>>
>>>>>All,
>>>>>
>>>>>1. Removing the "OS79XX.txt" file did not make any difference.
>>>>>
>>>>>2. I did issue "create cnf-files" files command and you can see the time stamp in the config in my previous post.
>>>>>
>>>>>
>>>>>3. Here is output from "show telephony-service tftp-bindings"
>>>>>tftp-server system:/its/SEPDEFAULT.cnf tftp-server
>>>>>system:/its/SEPDEFAULT.cnf alias SEPDefault.cnf tftp-server
>>>>>system:/its/XMLDefault.cnf.xml alias XMLDefault.cnf.xml tftp-server
>>>>>system:/its/ATADefault.cnf.xml tftp-server
>>>>>system:/its/united_states/7960-tones.xml alias
>>>>>United_States/7960-tones.xml tftp-server
>>>>>system:/its/united_states/7960-font.xml alias
>>>>>English_United_States/7960-font.xml
>>>>>tftp-server system:/its/united_states/7960-dictionary.xml alias
>>>>>English_United_States/7960-dictionary.xml
>>>>>tftp-server system:/its/united_states/7960-kate.xml alias
>>>>>English_United_States/7960-kate.xml
>>>>>tftp-server system:/its/united_states/SCCP-dictionary.xml alias
>>>>>English_United_States/SCCP-dictionary.xml
>>>>>tftp-server system:/its/XMLDefault7960.cnf.xml alias
>>>>>SEP000DED913780.cnf.xml
>>>>>
>>>>>4. The 7960G phone still wants:
>>>>>TFTP: Looking for P00303020209.bin
>>>>>
>>>>>5. Here is my theory.
>>>>>
>>>>>CME 3.3 is really only set up for phones that have the Universal Application Loader (UAL) flashed in them. CME 3.3 doesn't really have a way to upgrade phones that don't have the UAL. I say this because from what I can see I don't think CME 3.3 has any way to generate .cnf files with load info. The real question is how much are the "SEPDefault.cnf" file and it's alias "SEPDefault.cnf" affected by "load" and "create cnf-files"?
>>>>>
>>>>>Here are the contents:
>>>>>
>>>>>0000000 001 001 \0 001 002 H 020 001 001 001 003 320 007 \0 \0 004
>>>>>0000020 007 \0 h t t p : / / 7 2 . 1 6 . 1
>>>>>0000040 . 1 : 8 0 / l o c a l d i r e c
>>>>>0000060 t o r y \0 \0 \0 001 377
>>>>>0000071
>>>>>
>>>>>So while "create cnf-files" does change the ip address in the .cnf file I don't see anything in this file that specifies which firmware file to load. I am not convinced that CME 3.3 has a way to generate .cnf files that specify firmware files. It DOES has a way to generate ".cnf.xml" files that have this info, but my phone isn't looking for those. I believe you need UAL for that.
>>>>>
>>>>>I am really out of ideas. The best way I can see right now to do this is to load a non SCCP image using the OS79XX.txt mechanism and then load a newer SCCP image using that same mechanism. A kind of two step process.
>>>>>
>>>>>Any insight or ideas welcome.
>>>>>
>>>>>Best,
>>>>>
>>>>>leb
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: Lawrence E. Bakst [mailto:ml at iridescent.org]
>>>>>>Sent: Saturday, September 03, 2005 10:08 AM
>>>>>>To: Bernhard Albler
>>>>>>Cc: cisco-voip at puck.nether.net
>>>>>>Subject: Re: AW: [cisco-voip] Upgrading 7960G firmware with CME 3.3
>>>>>>
>>>>>>Sorry, my bad. "load" doesn't seem to work. It was the first thing I did. The 7960G phone still wants:
>>>>>>TFTP: Looking for P00303020209.bin
>>>>>>
>>>>>>Here's my config below.
>>>>>>
>>>>>>I really need to figure this out so I can get this up and running.
>>>>>>
>>>>>>Best,
>>>>>>
>>>>>>leb
>>>>>>
>>>>>>Current configuration : 2692 bytes
>>>>>>!
>>>>>>! Last configuration change at 07:02:16 pdt Sat Sep 3 2005 !
>>>>>>version 12.3
>>>>>>service timestamps debug uptime
>>>>>>service timestamps log uptime
>>>>>>no service password-encryption
>>>>>>!
>>>>>>hostname chatter
>>>>>>!
>>>>>>boot-start-marker
>>>>>>boot system flash c3640-is-mz.123-14.T3.bin boot-end-marker !
>>>>>>!
>>>>>>no aaa new-model
>>>>>>!
>>>>>>resource policy
>>>>>>!
>>>>>>memory-size iomem 10
>>>>>>clock timezone pst -8
>>>>>>clock summer-time pdt recurring
>>>>>>voice-card 0
>>>>>>!
>>>>>>voice-card 1
>>>>>>!
>>>>>>ip subnet-zero
>>>>>>!
>>>>>>!
>>>>>>ip cef
>>>>>>no ip dhcp use vrf connected
>>>>>>ip dhcp excluded-address 72.16.1.0 72.16.1.99 ip dhcp excluded-address 72.16.1.200 72.16.1.254 !
>>>>>>ip dhcp pool phone-pool
>>>>>>network 72.16.1.0 255.255.255.0
>>>>>>default-router 72.16.1.1
>>>>>>option 150 ip 72.16.1.1
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>username leb password 0 4dylan
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>interface BRI1/0
>>>>>>no ip address
>>>>>>!
>>>>>>interface BRI1/1
>>>>>>no ip address
>>>>>>!
>>>>>>interface FastEthernet2/0
>>>>>>ip address 192.168.0.254 255.255.0.0
>>>>>>duplex auto
>>>>>>speed auto
>>>>>>!
>>>>>>interface FastEthernet2/1
>>>>>>ip address 72.16.1.1 255.255.255.0
>>>>>>duplex auto
>>>>>>speed auto
>>>>>>!
>>>>>>interface Ethernet3/0
>>>>>>no ip address
>>>>>>shutdown
>>>>>>half-duplex
>>>>>>!
>>>>>>interface Ethernet3/1
>>>>>>no ip address
>>>>>>shutdown
>>>>>>half-duplex
>>>>>>!
>>>>>>interface Ethernet3/2
>>>>>>no ip address
>>>>>>shutdown
>>>>>>half-duplex
>>>>>>!
>>>>>>interface Ethernet3/3
>>>>>>no ip address
>>>>>>shutdown
>>>>>>half-duplex
>>>>>>!
>>>>>>ip default-gateway 192.168.0.1
>>>>>>ip http server
>>>>>>!
>>>>>>ip classless
>>>>>>ip route 0.0.0.0 0.0.0.0 192.168.0.1
>>>>>>ip route 72.16.1.0 255.255.255.0 FastEthernet2/1 ip route 192.168.0.1 255.255.255.255 FastEthernet2/0 !
>>>>>>!
>>>>>>!
>>>>>>tftp-server flash:P00305000600.bin
>>>>>>tftp-server flash:P00305000600.sbn
>>>>>>tftp-server flash:S00103020003.bin
>>>>>>tftp-server flash:OS79XX.TXT
>>>>>>tftp-server flash:P00305000500.bin
>>>>>>tftp-server flash:P00305000500.sbn
>>>>>>!
>>>>>>control-plane
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>voice-port 0/0/0
>>>>>>!
>>>>>>voice-port 0/0/1
>>>>>>!
>>>>>>voice-port 0/0/2
>>>>>>!
>>>>>>voice-port 0/0/3
>>>>>>!
>>>>>>voice-port 0/0/4
>>>>>>!
>>>>>>voice-port 0/0/5
>>>>>>!
>>>>>>voice-port 0/0/6
>>>>>>!
>>>>>>voice-port 0/0/7
>>>>>>!
>>>>>>voice-port 0/0/14
>>>>>>!
>>>>>>voice-port 0/0/15
>>>>>>!
>>>>>>voice-port 0/0/16
>>>>>>!
>>>>>>voice-port 0/0/17
>>>>>>!
>>>>>>voice-port 1/0/0
>>>>>>!
>>>>>>voice-port 1/0/1
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>dial-peer cor custom
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>dial-peer voice 901 pots
>>>>>>description dial 9 for line #1
>>>>>>destination-pattern 9
>>>>>>port 0/0/4
>>>>>>!
>>>>>>dial-peer voice 801 pots
>>>>>>description dial 8 for line #2
>>>>>>destination-pattern 8
>>>>>>port 0/0/5
>>>>>>!
>>>>>>dial-peer voice 701 pots
>>>>>>description dial 7 for line #3
>>>>>>destination-pattern 7
>>>>>>port 0/0/6
>>>>>>!
>>>>>>!
>>>>>>telephony-service
>>>>>>load 7960-7940 P00305000600
>>>>>>max-ephones 16
>>>>>>max-dn 64
>>>>>>ip source-address 72.16.1.1 port 2000 time-zone 5 create cnf-files
>>>>>>version-stamp 7960 Sep 03 2005 07:02:04 keepalive 31 max-conferences 4 gain -6 !
>>>>>>!
>>>>>>ephone-dn 1
>>>>>>number 101
>>>>>>!
>>>>>>!
>>>>>>ephone 1
>>>>>>mac-address 000D.ED91.37XX
>>>>>>type 7960
>>>>>>button 1:1
>>>>>>!
>>>>>>!
>>>>>>!
>>>>>>line con 0
>>>>>>line aux 0
>>>>>>line vty 0 4
>>>>>>login
>>>>>>!
>>>>>>ntp clock-period 17179993
>>>>>>ntp server 17.254.0.31
>>>>>>!
>>>>>>end
>>>>>>
>>>>>>chatter#
>>>>>>
>>>>>>
>>>>>>
>>>>>>At 1:59 PM +0200 9/3/05, Bernhard Albler wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Maybe I'm missing somethin here, but wouldn't you just upgrade via the load command with cme?
>>>>>>>e.g.
>>>>>>>
>>>>>>>telephony-service
>>>>>>>load 7960-7940 P00305000301 (or whatever the name of the load is,
>>>>>>>you want to use)
>>>>>>>
>>>>>>>regards
>>>>>>>bernhard
>>>>>>>
>>>>>>>-----Ursprüngliche Nachricht-----
>>>>>>>Von: cisco-voip-bounces at puck.nether.net
>>>>>>>[mailto:cisco-voip-bounces at puck.nether.net] Im Auftrag von Lawrence E.
>>>>>>>Bakst
>>>>>>>Gesendet: Samstag, 03. September 2005 12:26
>>>>>>>An: cisco-voip at puck.nether.net
>>>>>>>Betreff: [cisco-voip] Upgrading 7960G firmware with CME 3.3
>>>>>>>
>>>>>>>I know this is mostly a high end CM list but maybe someone can help
>>>>>>>me with CME. I have a 3640 which is running IOS 12.3(14)T3 and CME 3.3.
>>>>>>>I'm hoping to study up for CCIE/Voice. I've got a couple of 7960G
>>>>>>>phones that I am trying to upgrade the firmware on and get them to
>>>>>>>work with CME. I'm not having much luck. The 7960G phone has the
>>>>>>>following
>>>>>>>loads:
>>>>>>>Appl Load ID: P003A310
>>>>>>>Boot Load ID: PC030301
>>>>>>>
>>>>>>>I've read the 'Cisco IP Phone 7960 and 7940 Firmware Upgrade Matrix"
>>>>>>>which is invaluable if you want to understand the old and new boot
>>>>>>>mechanisms and signed vs unsigned images.
>>>>>>>
>>>>>>>http://www.cisco.com/en/US/products/sw/voicesw/ps4967/products_upgra
>>>>>>>de_
>>>>>>>guides09186a008022a968.html
>>>>>>>
>>>>>>>
>>>>>>>It says for any SCCP image upgrade they recommend "Procedure A" which reads:
>>>>>>>The SEP<mac-address>.cnf.xml file is downloaded when a phone is reset.
>>>>>>>This file contains the load_information tag that tells the phone
>>>>>>>which image it should be running. If the image load differs from the
>>>>>>>one currently loaded on the phone, the phone contacts the TFTP
>>>>>>>server to upgrade to the new image.
>>>>>>>
>>>>>>>However it lies a bit. Maybe this is true once you rev up to the
>>>>>>>"Universal Application Loader" but my phone doesn't look for this file.
>>>>>>>It looks for:
>>>>>>>
>>>>>>>00:05:41: TFTP: Looking for OS79XX.TXT
>>>>>>>00:05:41: TFTP: Opened flash:OS79XX.TXT, fd 0, size 16 for process
>>>>>>>143
>>>>>>>00:05:41: TFTP: Finished flash:OS79XX.TXT, time 00:00:00 for process
>>>>>>>143
>>>>>>>00:05:41: TFTP: Looking for SEP000DED9137XX.cnf
>>>>>>>00:05:41: TFTP: Looking for SEPDefault.cnf
>>>>>>>00:05:42: TFTP: Looking for SEPDefault.cnf
>>>>>>>00:05:43: TFTP: Opened system:/its/SEPDEFAULT.cnf, fd 0, size 57 for
>>>>>>>process 152
>>>>>>>00:05:44: TFTP: Finished system:/its/SEPDEFAULT.cnf, time 00:00:00
>>>>>>>for process 152
>>>>>>>
>>>>>>>I don't seem to be able to use the OS79XX.TXT mechanism. It doesn't
>>>>>>>seem to work and the above document seems to explain that it will
>>>>>>>only seek a new image if the first 4 characters of the file name are
>>>>>>>different. In this case they are always "P003".
>>>>>>>
>>>>>>>So it tries all the files and finally gets the SEPDefault.cnf file,
>>>>>>>which has an unknown format (I've peeked inside and it's mostly ascii).
>>>>>>>
>>>>>>>The phone tries to load:
>>>>>>>02:24:00: TFTP: Looking for P00303020209.bin which I don't have.
>>>>>>>
>>>>>>>It ends up in a loop of:
>>>>>>>
>>>>>>>02:17:57: %IPPHONE-6-REGISTER: ephone-1:SEP000DED9137XX
>>>>>>>IP:72.16.1.101 Socket:1 DeviceType:Phone has registered.
>>>>>>>02:17:57: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000DED9137XX
>>>>>>>IP:72.16.1.101 Socket:1 DeviceType:Phone has unregistered normally.
>>>>>>>02:17:57: TFTP: Looking for P00303020209.bin
>>>>>>>02:18:57: %IPPHONE-6-REG_ALARM: Name=SEP000DED9137XX Load=A3.10
>>>>>>>Parms=Status/IPaddr LastTime=Phone-Loading (see expanded "debug
>>>>>>>ephone register" below.
>>>>>>>
>>>>>>>Q:
>>>>>>>
>>>>>>>1. Any ideas on how to upgrade this phone to the newer SCCP V 5, 6,
>>>>>>>or
>>>>>>>7 images?
>>>>>>>
>>>>>>>2. Why is the phone trying to load " P00303020209.bin"?
>>>>>>>
>>>>>>>3. I tried copying a newer image (universal loader) such as
>>>>>>>"P00305000600.bin" to "P00303020209.bin" and it did load that file
>>>>>>>via TFTP, but then the image is rejected and it tries to reload it again.
>>>>>>>
>>>>>>>4. I am almost tempted to load a SIP or MGCP image temporally so I
>>>>>>>can use the OS79XX.TXT mechanism as those images will chnage the
>>>>>>>first 4 characters. Anyone have any opinions on that?
>>>>>>>
>>>>>>>5. Is the reason the phone registers and immediately unregisters
>>>>>>>because the firmware is old? Or is it something else?
>>>>>>>
>>>>>>>I could post my config if that would really help.
>>>>>>>
>>>>>>>Best,
>>>>>>>
>>>>>>>leb
>>>>>>>
>>>>>>>02:35:06: New Skinny socket accepted [1] (0 active)
>>>>>>>02:35:06: sin_family 2, sin_port 52106, in_addr 72.16.1.101
>>>>>>>02:35:06: skinny_add_socket 1 72.16.1.101 52106
>>>>>>>02:35:06: %IPPHONE-6-REG_ALARM: Name=SEP000DED9138XX Load=A3.10
>>>>>>>Parms=Status/IPaddr LastTime=Phone-Loading
>>>>>>>02:35:06:
>>>>>>>Skinny StationAlarmMessage on socket [1] 72.16.1.101 SEP000DED9138XX
>>>>>>>02:35:06: severityInformational p1=2312 [0x908] p2=1694568520
>>>>>>>[0x65011048]
>>>>>>>02:35:06: Name=SEP000DED9138XX Load=A3.10 Parms=Status/IPaddr
>>>>>>>LastTime=Phone-Loading
>>>>>>>02:35:06: ephone-(1)[1] StationRegisterMessage (0/0/16) from
>>>>>>>72.16.1.101
>>>>>>>02:35:06: ephone-(1)[1] Register StationIdentifier DeviceName SEP000DED9138XX
>>>>>>>02:35:06: ephone-(1)[1] StationIdentifier Instance 1 deviceType 7
>>>>>>>02:35:06: ephone-1[-1]:stationIpAddr 72.16.1.101
>>>>>>>02:35:06: ephone-1[-1]:maxStreams 0
>>>>>>>02:35:06: ephone-1[-1]:protocol Ver 0x3
>>>>>>>02:35:06: ephone-1[-1]:phone-size 2048 dn-size 480
>>>>>>>02:35:06: ephone-(1) Allow any Skinny Server IP address 72.16.1.1
>>>>>>>02:35:06: ephone-1[-1]:Found entry 0 for 000DED9138XX
>>>>>>>02:35:06: ephone-1[-1]:socket change -1 to 1
>>>>>>>02:35:06: ephone-1[-1]:FAILED: CLOSED old socket -1
>>>>>>>02:35:06: ephone-1[1]:***Force device subtype to 0
>>>>>>>02:35:06: ephone-1[1]:phone SEP000DED9138XX re-associate OK on
>>>>>>>socket [1]
>>>>>>>02:35:06: %IPPHONE-6-REGISTER: ephone-1:SEP000DED9138XX
>>>>>>>IP:72.16.1.101 Socket:1 DeviceType:Phone has registere d.
>>>>>>>02:35:06: Phone 0 socket 1
>>>>>>>02:35:06: Skinny Local IP address = 72.16.1.1 on port 2000
>>>>>>>
>>>>>>>02:35:06: Skinny Phone IP address = 72.16.1.101 52106
>>>>>>>02:35:06: ephone-1[1]:Signal protocol ver 5 to phone with ver 3
>>>>>>>02:35:06: ephone-1[1]:Date Format M/D/Y
>>>>>>>02:35:06: ephone-1[1]:RegisterAck sent to ephone 1: keepalive period
>>>>>>>31 use sccp-version 3
>>>>>>>02:35:06: ephone-1[1]:CapabilitiesReq sent
>>>>>>>02:35:06: ephone-1[1]:Skinny IP port 35531 set for socket [1]
>>>>>>>02:35:06: ephone-1[1]:VersionReq received
>>>>>>>02:35:06: ephone-1[1][SEP000DED9138XX]:Req Version for deviceType 7
>>>>>>>is P00305000500, size = 402484 needs imt l oad
>>>>>>>02:35:06: ephone-1[1]:Req Version deviceType 7 is P00303020209 [max
>>>>>>>16 chars]
>>>>>>>02:35:06: ephone-1[1]:Version Message sent
>>>>>>>02:35:06: ephone-1[1]:CapabilitiesRes received
>>>>>>>02:35:06: ephone-1[1]:Caps list 6
>>>>>>>G711Ulaw64k 40 ms
>>>>>>>G711Alaw64k 40 ms
>>>>>>>G729 60 ms
>>>>>>>G729AnnexA 60 ms
>>>>>>>G729AnnexB 60 ms
>>>>>>>G729AnnexAwAnnexB 60 ms
>>>>>>>
>>>>>>>02:35:06: ephone-1[1]:Phone Unregistered on socket [1]
>>>>>>>SEP000DED9138XX
>>>>>>>02:35:06: ephone-1[1]:UnregisterAck sent on socket [1] (0/0/16)
>>>>>>>02:35:06: %IPPHONE-6-UNREGISTER_NORMAL: ephone-1:SEP000DED9138XX
>>>>>>>IP:72.16.1.101 Socket:1 DeviceType:Phone has unregistered normally.
>>>>>>>02:35:06: TFTP: Looking for P00303020209.bin
>>>>>>>02:35:06: skinny_server_process: Socket error. errno=0
>>>>>>>02:35:06: ephone-1[1]:DisAssociate: Closed socket 1 for unregistered
>>>>>>>phone
>>>>>>>02:35:06: CLOSED Skinny socket 1 for de-registered phone
>>>>>>>
>>>>>>>--
>>>>>>>Lawrence E. Bakst
>>>>>>>leb at iridescent.org
>>>>>>>_______________________________________________
>>>>>>>cisco-voip mailing list
>>>>>>>cisco-voip at puck.nether.net
>>>>>>>https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>_______________________________________________
>>>>>>cisco-voip mailing list
>>>>>>cisco-voip at puck.nether.net
>>>>>>https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>_______________________________________________
>>>>>cisco-voip mailing list
>>>>>cisco-voip at puck.nether.net
>>>>>https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>>
>
>
>Attachment converted: std:P00303020209.bin.gz ( / ) (002B7308)
More information about the cisco-voip
mailing list