[cisco-voip] Help with first time VOIP setup.
Anthony R. Mattke
a.mattke at gmail.com
Mon Jun 15 23:34:01 EDT 2009
Actually, I got this to work via a SIPDefaults.cnf on my TFTP server
containing image_version: P00308000400 (the Image I had from CME)
Its complaining about some missing files, but.. its progress! We're now
registered!
The only files I'm missing are..
Mar 1 01:45:22.643: TFTP: Looking for XMLDefault.cnf.xml
Mar 1 01:45:23.336: TFTP: Looking for RINGLIST.XML
Mar 1 01:45:23.492: TFTP: Looking for DISTINCTIVERINGLIST.XML
# Don't think I need these 3
Mar 1 01:43:49.839: TFTP: Looking for SIPDefault.cnf
Mar 1 01:43:49.867: TFTP: Looking for MGCDefault.cnf
Mar 1 01:45:22.491: TFTP: Looking for CTLSEP001794CF1E45.tlv
I'm happy to say that I can make phone calls from my 7960 to my FXS
ports... :D
Now, I just have to wait for my FXO ports to come in and figure out how
to add each of them as extensions on the 7960, and also ring the FXS on
one of them, and failover the other FXO after a few seconds to the same
FXS port.
Aka, 1 home phone line comming in, 1 office. Both can ring the 7960 on
separate lines... The home line also rings a FXS port. And I want to
ring that same FXS after a no answer on my 7960..
Should be pretty simple, right?
-Tony
Nick Matthews wrote:
> I would start by using CME as your TFTP server. Upload the files from
> the latest SCCP load out on the voice software download for your phone
> load, and unzip them onto the router. Then use the global config
> command 'tftp-server flash:filename.ext' to enable TFTP for the file.
> Normal SCCP loads are 5-7 files, you would need to copy and enable
> tftp for each.
>
> In telephony service:
>
> telephony-service
> load <phone type> <phone load filename minus .LOADS>
>
> Then, 'debug tftp events' and match the files the phone is looking
> for. The OS79XX file is the key to getting this to work.
>
>
> -nick
>
> On Mon, Jun 15, 2009 at 8:35 PM, Anthony R. Mattke<a.mattke at gmail.com> wrote:
>> Yeah, I read that and it makes about as much sense to me as watching grass
>> grow.. or something.
>>
>> Anyway, so, my phone shows..
>>
>> Application Load ID
>> P0S3-08-4-00
>>
>> Boot Load ID
>> PC030301
>>
>>
>> From what I understood, I could setup a TFTP server with P00308000400.bin
>> and a file named OS79XX.TXT containing the text P00308000400 -- I tried
>> this, and don't see the phone attempting to connect... Eventhough the phone
>> shows the new TFTP server.
>>
>> this page
>> http://www.cisco.com/en/US/docs/voice_ip_comm/cuipph/7960g_7940g/mgcp/firmware/matrix/frmwrup.html#wp1049010
>>
>> tells me to use a different method... which I also don't understand.
>>
>> Any tips for a simple firmware upgrade on these things?
>>
>> Thanks,
>>
>> -Tony
>>
>>
>> Adam Blomfield wrote:
>>> If you want to use this phone with CME you will want to convert it back to
>>> SCCP from SIP. Check out the following document:
>>>
>>>
>>> http://www.cisco.com/en/US/products/hw/phones/ps379/products_tech_note09186a0080094584.shtml
>>>
>>> -Adam
>>>
>>> On Mon, Jun 15, 2009 at 6:29 PM, Anthony R. Mattke <a.mattke at gmail.com
>>> <mailto:a.mattke at gmail.com>> wrote:
>>>
>>> Well, this is what I did as far as DHCP and TFTP setup...
>>>
>>> ip dhcp pool VOIP
>>> network 10.1.8.0 255.255.255.0
>>> domain-name test.net <http://test.net>
>>> option 150 ip 10.1.8.1
>>> lease 7
>>> !
>>> ip dhcp excluded-address 10.1.8.0 10.1.8.100
>>> !
>>>
>>> tftp-server flash:/phone/7940-7960/P00308000400.bin alias
>>> P00308000400.bin
>>> tftp-server flash:/phone/7940-7960/P00308000400.loads alias
>>> P00308000400.loads
>>> tftp-server flash:/phone/7940-7960/P00308000400.sb2 alias
>>> P00308000400.sb2
>>> tftp-server flash:/phone/7940-7960/P00308000400.sbn alias
>>> P00308000400.sbn
>>>
>>> dir flash shows those files there
>>> 36 -rw- 129828 Feb 19 2007 19:47:55 +00:00
>>> phone/7940-7960/P00308000400.bin
>>> 37 -rw- 461 Feb 19 2007 19:47:55 +00:00
>>> phone/7940-7960/P00308000400.loads
>>> 38 -rw- 701768 Feb 19 2007 19:48:08 +00:00
>>> phone/7940-7960/P00308000400.sb2
>>> 39 -rw- 130232 Feb 19 2007 19:48:10 +00:00
>>> phone/7940-7960/P00308000400.sbn
>>>
>>> While the phone loads, it just goes back and forth between
>>> configuring VLAN and Configuring IP and then ends up at Phone
>>> Unprovisione
>>>
>>> I went ahead and did a debug ephone registration and I got 0 output...
>>> Next I tried.
>>>
>>> #show debug
>>> EPHONE error debugging is enabled
>>> EPHONE registration debugging is enabled
>>> for 12 ephones (too many to list)
>>> voice-register:
>>> voice-register error debugging is on
>>> voice-register events debugging is on
>>>
>>> Still nothing on the terminal while the phone boots..
>>>
>>> I must have something configured wrong... Could it be because this
>>> is a SIP phone and the only files I have on the tftp server are the
>>> stock ones from the CME 4.1 package??
>>>
>>> Thanks!
>>>
>>> -Tony
>>>
>>>
>>> Larry Hadrava wrote:
>>>
>>> Also - how is your dhcp setup for the IP phones? Is the option
>>> 150 setup correctly?
>>> What are the phone displays telling you during the boot process?
>>> You can also check the ephone registration process with debug
>>> commands.
>>>
>>> Larry Hadrava
>>> CCIE #12203 CCNP CCNA
>>> Sr. Support Engineer – IPexpert, Inc.
>>> URL: http://www.IPexpert.com
>>>
>>>
>>> On Mon, Jun 15, 2009 at 6:20 PM, Paul <asobihoudai at yahoo.com
>>> <mailto:asobihoudai at yahoo.com> <mailto:asobihoudai at yahoo.com
>>> <mailto:asobihoudai at yahoo.com>>> wrote:
>>>
>>>
>>> Anthony,
>>>
>>> Have you entered your tftp-server statements to actually give
>>> your
>>> phones their firmware and load files?
>>>
>>> Paul
>>>
>>>
>>> ----- Original Message ----
>>> From: Anthony R. Mattke <a.mattke at gmail.com
>>> <mailto:a.mattke at gmail.com> <mailto:a.mattke at gmail.com
>>> <mailto:a.mattke at gmail.com>>>
>>> To: cisco-voip at puck.nether.net
>>> <mailto:cisco-voip at puck.nether.net>
>>> <mailto:cisco-voip at puck.nether.net
>>> <mailto:cisco-voip at puck.nether.net>>
>>> Sent: Monday, June 15, 2009 4:52:04 PM
>>> Subject: [cisco-voip] Help with first time VOIP setup.
>>>
>>> Ok, I admit it. I need a bit of help! Who doesn't from time
>>> to time?
>>>
>>> I am attempting to setup a home VOIP lab to try and learn a
>>> little
>>> bit about how it all works. I have 2 1760 routers, 2x
>>> vic-2fxs and
>>> 1x 2fxo a couple of analog phones, and a cisco 7960 phone
>>> (running
>>> sip firmware currently). One of my 1760s is running CME 4.1
>>>
>>> I'm having trouble getting the 7960 setup properly, and think
>>> it may
>>> be the firmware on it. At first, it would come up and act like
>>> it
>>> was going to work, but not really do anything. I'd attempt
>>> dialing
>>> and it wouldn't seem to actually connect to my fxs ports. Not
>>> sure
>>> if I need a dialplan or something else in place for this to work
>>> properly or what. The dial-peers between pots phones works
>>> fine...
>>> but I digress.
>>>
>>> The phone was from eBay and kept coming up with some Company
>>> name on
>>> the lines, so I decided to do a reset on it. Upon resetting,
>>> it no
>>> longer registers.. Just shows Phone Unprovisioned
>>>
>>> My configuration is pretty bare.. here are some of the bits
>>> and such.
>>>
>>> telephony-service
>>> load 7960-7940 P00308000400
>>> max-ephones 12
>>> max-dn 24
>>> ip source-address 10.1.8.1 port 2000
>>> system message BGP Guru
>>> cnf-file location flash:
>>> cnf-file perphone
>>> max-conferences 4 gain -6
>>> moh music-on-hold.au
>>> web admin system name admin secret 5
>>> $1$bQT5$BrB0dtZH2sS3gKqh3PdDe0
>>> dn-webedit
>>> time-webedit
>>> transfer-system full-consult
>>> create cnf-files version-stamp 7960 Mar 01 2002 01:26:49
>>> !
>>> ephone-dn 1
>>> number 8669
>>> name test
>>> call-forward noan 5555 timeout 30
>>> hold-alert 30 originator
>>> !
>>> !
>>> ephone 1
>>> mac-address 0027.94CF.1E45
>>> type 7960
>>> !
>>>
>>>
>>> #show ephone
>>>
>>> ephone-1 Mac:0027.94CF.1E45 TCP socket:[-1] activeLine:0
>>> UNREGISTERED
>>> mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0
>>> debug:0 caps:0
>>> IP:0.0.0.0 0 Unknown 0 keepalive 0 max_line 0
>>>
>>>
>>> Anyway, thats what I got, and I know enough to know I could use
>>> a
>>> point in the right direction.
>>>
>>> Thanks in advance.
>>>
>>> -Tony
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> <mailto:cisco-voip at puck.nether.net>
>>> <mailto:cisco-voip at puck.nether.net
>>> <mailto:cisco-voip at puck.nether.net>>
>>>
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> <mailto:cisco-voip at puck.nether.net>
>>> <mailto:cisco-voip at puck.nether.net
>>> <mailto:cisco-voip at puck.nether.net>>
>>>
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net <mailto: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
>>
More information about the cisco-voip
mailing list