asterisk users - Apr 2009 - Step-by-Step Asterisk and Cisco 1760 Help

I am up to post 5 on my step-by-step but I hit a bit of a snag and so far my
searches have failed me, I hope someone can help.  (By the way, I added an
asterisk index for quick navigation on the blog
http://qvlweb.blogspot.com/2009/04/asterisk-pbx-install-index.html.)

Here is the snag and I am hoping for a little help from the collective. Inbound
I have 2 different numbers. I can call in on both of them at the same time and
have two inbound concurrent calls going.  The problem is with outbound calls. 
The first call goes out fine but the second call fails with a busy error.  So it
looks like it is not failing over to the second line (which is what I expected
the 1760 to do) and I am not sure if this is a Cisco setting or an Asterisk
setting (or both).  I played with the Cisco setting, whichever line I set to
preference 1 works but the preference 2 line does not pick up if line 1 is busy.
----See details below (asterisk console / sip.conf / extensions.conf / 1760
config)---

First call out the asterisk console looks like
this-----------------------------------------------------:

    -- Executing [92952210 at internal:1] Dial("SIP/207-09a75e70",
"SIP/Cisco1760/2952210") in new stack
    -- Called Cisco1760/2952210
[Apr 22 16:08:29] NOTICE[3450]: chan_sip.c:14489 handle_request_invite: Call
from '207' to extension '2952210' rejected because extension not
found.
    -- SIP/Cisco1760-09a77410 is making progress passing it to SIP/207-09a75e70
    -- SIP/Cisco1760-09a77410 answered SIP/207-09a75e70
    -- Native bridging SIP/207-09a75e70 and SIP/Cisco1760-09a77410
localhost*CLI>

Second Call out the asterisk console looks like
this-----------------------------------------------------:
    -- Executing [92952210 at internal:1] Dial("SIP/222-09ab3588",
"SIP/Cisco1760/2952210") in new stack
    -- Called Cisco1760/2952210
[Apr 22 16:08:58] NOTICE[3450]: chan_sip.c:14489 handle_request_invite: Call
from '222' to extension '2952210' rejected because extension not
found.
    -- Got SIP response 486 "Busy here" back from 172.17.2.1
    -- SIP/Cisco1760-09ab7cf8 is busy
  == Everyone is busy/congested at this time (1:1/0/0)
    -- Executing [92952210 at internal:2]
Congestion("SIP/222-09ab3588", "") in new stack
  == Spawn extension (internal, 92952210, 2) exited non-zero on
'SIP/222-09ab3588'
localhost*CLI>


--------------sip.conf ---------
[general]
bindaddr=0.0.0.0

[Cisco1760]
context=incoming_calls
type=friend
host=172.17.2.1
dtmfmode=rfc2833
disallow=all
allow=ulaw
insecure=very


----------extensions.conf------------
[globals]
OUTBOUNDTRUNK=SIP/Cisco1760


[outbound-local]
exten => _9NXXXXXX,1,Dial(${OUTBOUNDTRUNK}/${EXTEN:1})
exten => _9NXXXXXX,n,Congestion()
exten => _9NXXXXXX,n,Hangup()

-----------Cisco 1760 config ----------
dial-peer voice 100 pots  (This line that is set to preference 2 does not work)
 huntstop
 preference 2
 destination-pattern .T
 port 0/0
 forward-digits all
!
dial-peer voice 2212 pots    (This line that is set to Preference 1 is the one
that works)
 huntstop
 preference 1
 destination-pattern .T
 port 0/1
 forward-digits all

Thanks,
Jimmy

Jimmy wrote:

Second Call out the asterisk console looks like
this-----------------------------------------------------:
    -- Executing [92952210 at internal:1] Dial("SIP/222-09ab3588",
"SIP/Cisco1760/2952210") in new stack
    -- Called Cisco1760/2952210
[Apr 22 16:08:58] NOTICE[3450]: chan_sip.c:14489 handle_request_invite: Call
from '222' to extension '2952210' rejected because extension not
found.
    -- Got SIP response 486 "Busy here" back from 172.17.2.1
    -- SIP/Cisco1760-09ab7cf8 is busy
  == Everyone is busy/congested at this time (1:1/0/0)
    -- Executing [92952210 at internal:2]
Congestion("SIP/222-09ab3588", "") in new stack
  == Spawn extension (internal, 92952210, 2) exited non-zero on
'SIP/222-09ab3588'
localhost*CLI>


--------------sip.conf ---------
[general]
bindaddr=0.0.0.0

[Cisco1760]
context=incoming_calls
type=friend
host=172.17.2.1
dtmfmode=rfc2833
disallow=all
allow=ulaw
insecure=very


----------extensions.conf------------
[globals]
OUTBOUNDTRUNK=SIP/Cisco1760


[outbound-local]
exten => _9NXXXXXX,1,Dial(${OUTBOUNDTRUNK}/${EXTEN:1})
exten => _9NXXXXXX,n,Congestion()
exten => _9NXXXXXX,n,Hangup()

-----------Cisco 1760 config ----------
dial-peer voice 100 pots  (This line that is set to preference 2 does not work)
 huntstop
 preference 2
 destination-pattern .T
 port 0/0
 forward-digits all
!
dial-peer voice 2212 pots    (This line that is set to Preference 1 is the one
that works)
 huntstop
 preference 1
 destination-pattern .T
 port 0/1
 forward-digits all


------------------------------------------------
You do not want to use huntstop on the dialpeers in this situation.
The huntstop option tells the call routing function in the router to
stop search for a call route if it encounters a failure.

Call number 2 hits dialpeer 1, finds it busy and the huntstop causes
the processing to stop.

Dan

>-----Original Message-----
>From: asterisk-users-bounces at lists.digium.com
>[mailto:asterisk-users-bounces at lists.digium.com]On Behalf Of Tony
>Mountifield
>Sent: Wednesday, May 20, 2009 06:26 AM
>To: asterisk-users at lists.digium.com
>Subject: Re: [asterisk-users] Step-by-Step Asterisk and MeetMe Help
>
>
>In article 
><E77AB304D41C084090D498682873252FC1B5FD at
nts-10.ca.hmhengineers.com>,
>Jimmy Ezell <jezell at hmhca.com> wrote:
>> 
>> Sounds like the workaround for 4.7 is to add this symlink 
>that you mention.  What directory
>> does the symlink need to be in?  What should it look like?  
>Where should it point to?
>
>No, you should never need to add that symbolic link. I have done many
>builds of zaptel on CentOS 4.x and never needed it.
>
>What I think is more likely is that having done an initial install of
>CentOS, you then did a yum update which pulled in a newer 
>kernel. But you
>have not yet rebooted the system, so it is still running the original
>kernel, even though the build files are now for the newer one.
>
>Remove any extra links you added, reboot the system, and then 
>try building
>the modules again. It should go without a hitch.
>
>Cheers
>Tony
Tony,
I never did an update that I know of but I followed your instructions anyway and
it worked on my vm test machine.  It took a bit more effort on my
multi-processor machine but I got that going too.

Here are the steps I took:
single processor machine
# rm /usr/src/linux-2.4   (removed the symbolic link)
# rpm -e kernel-devel     (removed the kernel-devel module)   
# yum update kernel*      (updated the kernel)
# init 6                  (rebooted the machine to load the updated kernel)
# yum install -y kernel-devel (installed kernel-devel for the updated kernel)
(compiled zaptel and it looked good)
# init 6   (rebooted again and this time I saw ztdummy get loaded!!!)

multi-processor machine  ( I had to remember to specify smp for the kernel)
# rm /usr/src/linux-2.4   (removed the symbolic link)
# rpm -e kernel-devel     (removed the kernel-devel module)
# rpm -e kernel-smp-devel     (removed the kernel-devel module for smp)
# yum update kernel-smp*   (update the kernel for smp)
# init 6 				(reboot)
# yum install -y kernel-smp-devel
(compiled zaptel)
# init 6 (rebooted and ztdummy loaded !!!!)

Tried MeetMe and sure enough it is working!!!!!!

Thank you, thank you, thank you, to all who gave me input on this.

Jimmy
http://qvlweb.blogspot.com/2009/04/asterisk-pbx-install-index.html


>

On Wed, May 20, 2009 at 01:07:25PM -0700, Jimmy Ezell wrote:
> multi-processor machine  ( I had to remember to specify smp for the kernel)
I repeat: why bother with such an old system? Really?

Recall the comment from the book. That book had nothing really specific
to Centos 4. Why do you shoot yourself in the foot by installing Centos4
now?

(not to mention Zaptel)

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

>On Wed, May 20, 2009 at 01:07:25PM -0700, Jimmy Ezell wrote:
>
>> multi-processor machine  ( I had to remember to specify smp 
>for the kernel)
>
>I repeat: why bother with such an old system? Really?
>
>Recall the comment from the book. That book had nothing really specific
>to Centos 4. Why do you shoot yourself in the foot by 
>installing Centos4
>now?
>
>(not to mention Zaptel)
>
>-- 
>               Tzafrir Cohen
Tzafrir thanks for the comments.  I am not done playing with this and in the end
I may well use newer software as you suggest.

According to wikipedia CentOS 4.7 was released OCT. 2008 (7 months ago) is that
really consider that old?  I am looking to setup a phone system that I would
hope would not require any major software upgrades for many years.


Jimmy
>

[This email is either empty or too large to be displayed at this time]