Mark Messmore, Technical Support, University Telcom Inc.
2004-Apr-15 08:04 UTC
[Asterisk-Users] t1 won't dial outbound
I've posted this problem a couple of times before with little or no
response. Basically I have a T100P in my * box. Incoming calls are
working great. However outgoing calls are not working at all. I've
copied a previous post into this message which should have all the
necessary info. Any ideas or suggestions would be greatly appreciated.
Thanks.
Mark
########################################################################
#################
OK...I've got an * box with a T100P in it. For the most part incoming
calls are going through just fine. Outgoing calls, however, I'm having
some more trouble with. Whenever I make an outgoing call, the call
begins, however after the dialing process all I hear is dead air.
Here's the output from my * console:
-- Executing Dial("SIP/mark-2d08", "Zap/g3/2550559") in new
stack
-- Called g3/2550559
-- Hungup 'Zap/6-1'
== Spawn extension (uti-mainst, 2550559, 1) exited non-zero on
'SIP/mark-2d08'
I've checked with the switch guy...and whatever channel I'm trying to
dial out on is coming up as "blocked" on his switch. We've
compared as
many settings as we can think of and they all seem to be set the same.
I'll post the entries from my zaptel.conf and my zapata.conf in
here...if you have any ideas please send them my way...
zaptel.conf
span=1,1,0,d4,ami
e&m=1-24
fxsks=25
loadzone=us
defaultzone=us
zapata.conf
context=conference
signalling=em
switchtype=5ess
group=3
callgroup=3
pickupgroup=3
channel => 6
busydetect=yes
callerid=asreceived
callprogress=yes
callreturn=yes
callwaiting=yes
callwaitingcallerid=yes
cancallforward=yes
echocancel=yes
echocancelwhenbridged=yes
immediate=no
language=us
musiconhold=default
threewaycalling=yes
transfer=yes
usecallerid=yes
########################################################################
##########################
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20040415/ba7fe579/attachment.htm
It looks like your channel and group statements in the zapata.conf are the
problem. Notice that when it tries to dial out it does so on Zap/6-1. You
have the T-1 defined as 'Span 1,' but you are trying to send the calls
to span
6. It ain't gonna work! I don't see anywhere where you've assigned
the rest
of the channels on that T-1, either. I would recommend either grouping them
all together (that's the easiest), or at least making sure you've got
all of
the channels assigned to groups. My zapata.conf is much simpler:
signalling=pri_net
group=1
channel => 1-23
When it dials, then you will see the calls going out on Zap/1-1 or Zap/1-2,
etc.
Good luck; and have fun!
Joe
"Mark Messmore, Technical Support, University Telcom Inc."
<mark@utionline.net> wrote:
I've posted this problem a couple of times before with little or no
response. Basically I have a T100P in my * box. Incoming calls are
working great. However outgoing calls are not working at all. I've
copied a previous post into this message which should have all the
necessary info. Any ideas or suggestions would be greatly appreciated.
Thanks.
Mark
########################################################################
#################
OK...I've got an * box with a T100P in it. For the most part incoming
calls are going through just fine. Outgoing calls, however, I'm having
some more trouble with. Whenever I make an outgoing call, the call
begins, however after the dialing process all I hear is dead air.
Here's the output from my * console:
-- Executing Dial("SIP/mark-2d08", "Zap/g3/2550559") in new
stack
-- Called g3/2550559
-- Hungup 'Zap/6-1'
== Spawn extension (uti-mainst, 2550559, 1) exited non-zero on
'SIP/mark-2d08'
I've checked with the switch guy...and whatever channel I'm trying to
dial out on is coming up as "blocked" on his switch. We've
compared as
many settings as we can think of and they all seem to be set the same.
I'll post the entries from my zaptel.conf and my zapata.conf in
here...if you have any ideas please send them my way...
zaptel.conf
span=1,1,0,d4,ami
e&m=1-24
fxsks=25
loadzone=us
defaultzone=us
zapata.conf
context=conference
signalling=em
switchtype=5ess
group=3
callgroup=3
pickupgroup=3
channel => 6
busydetect=yes
callerid=asreceived
callprogress=yes
callreturn=yes
callwaiting=yes
callwaitingcallerid=yes
cancallforward=yes
echocancel=yes
echocancelwhenbridged=yes
immediate=no
language=us
musiconhold=default
threewaycalling=yes
transfer=yes
usecallerid=yes
########################################################################
##########################
_________________________________________________________
This mail sent using Secure Message Center
Put SAI Address and NASD blah blah stuff here.
I haven't tried breaking up the channels into different groups (mainly
because
I haven't had a need to), but the examples I've seen looked more like:
[channels]
signalling=em_w
switchtype=5ess
group=1
context=uti-mainst
channel => 1-3
group=2
context=sales
channel => 4-6
group=3
etc...........
In this example, the signalling and switchtype don't change (because they
are
all on the same trunk), but you can change the context in each group
definition. Anything specified ABOVE the channel statement will be applied to
those channels. So, you only need to specify the changes inbetween your
channel => statements.
As such, all of the other statements before the channel => 6 statement will
also be applied to that channel. If you specified a parameter (like
callretrun=yes or callprogress=yes) that the LEC (Carrier) didn't like, it
would not accept the call. If group 5 works correctly for outbound calls, I
would model group 3's defninitions after group 5.
Joe
"Mark Messmore, Technical Support, University Telcom Inc."
<mark@utionline.net> wrote:
Thanks for the reply.
I didn't include my entire zapata.conf...just the portion that applied
to this call (i.e. group #3)
Please correct me if I have misunderstood how this all works together.
When I see:
-- Executing Dial("SIP/mark-2d08", "Zap/g3/2550559") in new
stack
-- Called g3/2550559
-- Hungup 'Zap/6-1'
I'm interpreting that this is dialing out on Zap group 3 (which happens
to begin on channel 6). Please correct me if I'm wrong here...
I'm attaching my entire zapata.conf just to defer any confusion...and to
see if you can see anything.
Also, I'm going to take your suggestion and create another zapata.conf
which will be simplified just to see if there is a conflict somewhere in
there.
Thanks for your help!
Mark
-----Original Message-----
From: asterisk-users-admin@lists.digium.com
[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Joe Dennick
Sent: Thursday, April 15, 2004 1:46 PM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] t1 won't dial outbound
It looks like your channel and group statements in the zapata.conf are
the problem. Notice that when it tries to dial out it does so on
Zap/6-1. You have the T-1 defined as 'Span 1,' but you are trying to
send the calls to span 6. It ain't gonna work! I don't see anywhere
where you've assigned the rest of the channels on that T-1, either. I
would recommend either grouping them all together (that's the easiest),
or at least making sure you've got all of the channels assigned to
groups. My zapata.conf is much simpler:
signalling=pri_net
group=1
channel => 1-23
When it dials, then you will see the calls going out on Zap/1-1 or
Zap/1-2, etc.
Good luck; and have fun!
Joe
"Mark Messmore, Technical Support, University Telcom Inc."
<mark@utionline.net> wrote:
I've posted this problem a couple of times before with little or no
response. Basically I have a T100P in my * box. Incoming calls are
working great. However outgoing calls are not working at all. I've
copied a previous post into this message which should have all the
necessary info. Any ideas or suggestions would be greatly appreciated.
Thanks.
Mark
########################################################################
#################
OK...I've got an * box with a T100P in it. For the most part incoming
calls are going through just fine. Outgoing calls, however, I'm having
some more trouble with. Whenever I make an outgoing call, the call
begins, however after the dialing process all I hear is dead air.
Here's the output from my * console:
-- Executing Dial("SIP/mark-2d08", "Zap/g3/2550559") in
new stack
-- Called g3/2550559
-- Hungup 'Zap/6-1'
== Spawn extension (uti-mainst, 2550559, 1) exited non-zero on
'SIP/mark-2d08'
I've checked with the switch guy...and whatever channel I'm trying to
dial out on is coming up as "blocked" on his switch. We've
compared as
many settings as we can think of and they all seem to be set the same.
I'll post the entries from my zaptel.conf and my zapata.conf in
here...if you have any ideas please send them my way...
zaptel.conf
span=1,1,0,d4,ami
e&m=1-24
fxsks=25
loadzone=us
defaultzone=us
zapata.conf
context=conference
signalling=em
switchtype=5ess
group=3
callgroup=3
pickupgroup=3
channel => 6
busydetect=yes
callerid=asreceived
callprogress=yes
callreturn=yes
callwaiting=yes
callwaitingcallerid=yes
cancallforward=yes
echocancel=yes
echocancelwhenbridged=yes
immediate=no
language=us
musiconhold=default
threewaycalling=yes
transfer=yes
usecallerid=yes
########################################################################
##########################
_________________________________________________________
This mail sent using Secure Message Center
Put SAI Address and NASD blah blah stuff here.
_______________________________________________
Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
_________________________________________________________
This mail sent using Secure Message Center
Put SAI Address and NASD blah blah stuff here.