Re: convert cisco skinny phone to mgcp

very friendly and active list. Thanks .

yes, that was exactly the problem. 7960 had 5.(4) version
so it did not have universal application loader.
skinny  application loader is 6.x version onward and
MGCP and SIP are 7.x version onward.
(actually I did find this out on cisco website eventually).
I upgraded phone to 6.x  skinny and then converted them to mgcp 7(2).

Currently 2 mgcp phones can communicate using asterisk
but after some call sequence, phones hang, as if they are stuck
in some state. I have even seen phones rebooting by themselves.
Initially it was happening very often then on adding lines in extension.conf
to Hangup in second try they are ok for some time and then they hang.

May be there is some trick needed in extensions.conf to avoid this problem.
I will explore such possibilities. Does anyone know a  fix for this problem?

-Purvi

----- Original Message ----- 
From: "Dennis Boylan" <[email protected]>
To: "Purvi" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, November 17, 2004 8:02 AM
Subject: Re: [Vocal] convert cisco skinny phone to mgcp


> On Tue, Nov 16, 2004 at 05:31:08PM -0800, Purvi wrote:
> > Hi,
> >
> > I am in the process of converting cisco skinny phone to mgcp phone.
> > Looked up all the instructions and created OS79XX.TXT with mgcp firmware
> > and also created protocol specific files, all on tftp server.
>
> I recently came across an issue where a skinny 7960G did not want to
accept
> the SIP software.  The issue involved that the skinny version was before
> the universal loader.  I unzipped the SIP files into the tftp directory
> but the OS79XX.TXT file had P003 as the first 4 characters.  Since the
> phone was already running the P00 (skinny) software, it would not load
> the image.  I copied the P00 bin file to P0S and updated the OS79XX.TXT
> file.  After rebooting the phone, it successfully loaded the SIP load.
> I suspect that the same thing should work for the mgcp load.
>
> - Dennis
> >
> > server logs will show the os79xx.txt getting downloaded  by the phone
but
> > phone still
> > requests for SEP... file instead of asking for new image or new MGC
file.
> >
> > Are there any limitation on how many time a phone can be converted from
one
> > protocol to other?
> >
> > I also tried updating the loadinformation in SEP file to indicate
> > POM3-05-3-00
> > file thinking that this might trigger the phone to fetch new image but
> > nothing happens. Phone starts its procedure of considering tftp server
> > as default call manager and starts the skinny messages, which ofcourse
> > will fail and phone will go back to start of osx79xx.txt file.
> >
> > Its as if cisco phone ignores os79xx.txt and continue acting as per the
> > stored image.
> >
> > Idea on how to over come this will be of great help.
> >
> > -Purvi
> > _______________________________________________
> > vocal mailing list
> > [email protected]
> > To unsubscribe, please go to
http://www.vovida.org/mailman/listinfo/vocal
>
_______________________________________________
vocal mailing list
[email protected]
To unsubscribe, please go to http://www.vovida.org/mailman/listinfo/vocal