Upgrade from 1.2.4 from to 1.2.7


#1

Hi,

i wish to upgrade the 1.2.4 to 1.2.7. i shall be thankfull if you give your valauable advice , so that i can do it.


#2

download the new tarball (from digium’s site)
extract (normally in /usr/src)
make
make install

you’re done…


#3

only asterisk tar, i need to do that or enite zaptel…


#4

if you’re up to date on zaptel, then no, you don’t need to update zaptel…but if you’re not running zaptel 1.2.5, do so - there were several bug fixes in the newest release, apparently. if you do need to update zaptel, it’s the same procedure - download, extract, make, make install. do zaptel first, then asterisk.

good luck.


#5

Here before doing so , do i need to delete anything???


#6

[quote=“whoiswes”]download the new tarball (from digium’s site)
extract (normally in /usr/src)
make
make install

you’re done…[/quote]

No modification needed in dialplan at all ?

I want to do the same upgrade, but I’m afraid having something not working anymore after…


#7

1.2.x upgrades are bug fixes only…

once 1.4.0 comes out 1.4.x will only be bug fixes…

the only time you have to change your dialplan should be between on new minor (1.2, 1.4, 1.6 etc) updates


#8

[quote=“SwK”]1.2.x upgrades are bug fixes only…

once 1.4.0 comes out 1.4.x will only be bug fixes…

the only time you have to change your dialplan should be between on new minor (1.2, 1.4, 1.6 etc) updates[/quote]

Ok thanks.
But, one time, I tried to upgrade from 1.2.4 to 1.2.5, and my AGI script wasn’t started anymore at calls hangup. That’s why I asked that.
I’ll try upgrade to 1.2.7 on monday and will be able to tell you more.


#9

There ARE diff. from 1.24 to 1.27, but you can read it in the CHANGE and UPDATE.TXT of the tarball.

Make a backup of

/var/spool/asterisk/sounds

before, incase you have customized soundfiles: They are ALWAYS overwritten by updates ! :imp:

(Which most dont realize, using the standardsounds anyway - but here in germany, with german sounds, you realize that FAST…)


#10

But i have g729 codec installed, if i do si ,anychance of loosing the same? or i need to take some precventive actions ?


#11

[quote=“novazur”]Ok thanks.
But, one time, I tried to upgrade from 1.2.4 to 1.2.5, and my AGI script wasn’t started anymore at calls hangup. That’s why I asked that.
I’ll try upgrade to 1.2.7 on monday and will be able to tell you more.[/quote]

Tried, and same problem again…
So, I need help.

first, I have to tell that I have a AAH based configuration, but I don’t use AAH anymore. I just use AMP with a gentoo/asterisk. I have modified this configuration a lot.

Actually, I have this :

[code][from-internal]
;allow phones to use applications
include => app-callsip
include => app-userlogonoff
include => app-directory
include => app-dnd
include => app-callforward
include => app-callwaiting
include => app-messagecenter
include => app-calltrace
include => parkedcalls
include => from-internal-custom
;allow phones to dial other extensions
include => ext-fax
include => ext-local
include => ext-zapbarge
include => ext-chanspy
include => ext-pickup
include => ext-trash
include => ext-group
include => ext-queues
include => ext-meetme
include => ext-record
include => ext-test
;allow phones to access trunks
include => outbound-allroutes
exten => s,1,Macro(hangupcall)
exten => h,1,Macro(hangupcall)

[outbound-allroutes]
include => outbound-allroutes-custom
include => outrt-001-fwd
include => outrt-002-wengo
include => outrt-003-martfixe
include => outrt-004-martfixe2
include => outrt-005-martspec
include => outrt-006-martmob
include => outrt-007-guadfixe
include => outrt-008-dommob
include => outrt-009-francemob
include => outrt-010-francefixe
include => outrt-011-us
include => outrt-012-francevoip
include => outrt-013-sipphone
include => outrt-014-phonesys
include => outrt-015-qatarfixe
include => outrt-016-ukfixe
include => outrt-017-stana[/code]

And, for example, one route like :

[outrt-010-francefixe] include => outrt-010-francefixe-custom exten => _0[1-5]XXXXXXXX,1,Set(NOVA_ROUTE=010-francefixe) exten => _0[1-5]XXXXXXXX,2,Macro(dialout-enum,20,${EXTEN:1},) exten => _0[1-5]XXXXXXXX,3,Macro(dialout-trunk,9,${EXTEN:1},) exten => _0[1-5]XXXXXXXX,4,Macro(dialout-trunk,36,${EXTEN:1},) exten => _0[1-5]XXXXXXXX,5,Macro(outisbusy)

macro-dialout-trunk is correctly called, and seems working fine.

; What to do on hangup. [macro-hangupcall] exten => s,1,ResetCDR(w) exten => s,2,NoCDR() exten => s,3,Set(NOVA_STATE=END) exten => s,4,DeadAGI(novasterix.php) exten => s,5,Wait(2) exten => s,6,Hangup

But now, macro-hangupcall is never called anymore with 1.2.7 version. So my AGI script is never started. All my application is broken…

If someone could tell me why…
thanks

PS : sorry for my bad english.


#12

[quote=“novazur”]macro-dialout-trunk is correctly called, and seems working fine.
[…]
But now, macro-hangupcall is never called anymore with 1.2.7 version. So my AGI script is never started. All my application is broken…[/quote]

I just added :

at the end of the context [macro-dialout-trunk], and it seems to work now.


#13

Unless you run the AGI as a DeadAGI from the h extension the agi will die or get terminated on call hangup.

If It did this before then changed post 1.2.0 release this is because it was a bug before and should not have worked that way in the first place. AGI scripts as killed when the call is hungup unless DeadAGI is used,

thake the following

exten => 2500,1,NoOp(SomeExample)
exten => 2500,2,Dial(sip/somegate/9995551212)
exten => 2500,3,AGI(script.agi)

the above example will not produce the desired effect of running the AGI after the DIAL is hungup. it will ony run the AGI if the DIAL times out… be careful here may people have issues with this


#14

I’m not sure I understand all what you mean (I even don’t know if you tell me the solution I used is correct or not), but did you really and correctly see my config ?

I can see :
exten => h,1,Macro(hangupcall)

at the end of [from-internal]
I suppose that’s this exten which was calling the hangupcall macro.