Posted: Wed Jan 30, 2008 7:00 am Post subject: [Bristuff-users] Outbound dialing problem
Hi Everyone,
I have deployed BRIStuff (1.2.26-BRIstuffed-0.3.0-PRE-1y-p) on a CentOS5
server with a Cologne based HFC card. I am able to receive calls
without a problem, but when making a call I get the following below. I
have had the telco (NTT in Japan) check the ISDN line and confirm that
it is functioning and an engineer came and made/received calls on the
line. I have searched for as much information as possible but nothing
seems specific to this problem. I have added the "pridialplan=unknown"
option in zapata.conf, the national & international prefix's are correct
and I am using bri_cpe_ptmp for signaling.
I would be very grateful for any suggestions or assistance to solve the
problem.
Thank you in advance,
David
-- Executing Set("SIP/1002-09cd9350", "CALLERID(num)=xxxx") in new
stack
-- Executing Dial("SIP/1002-09cd9350", "Zap/g1/yyyy||70,TW") in new
stack
1 -- Making new call for cr 131
-- Requested transfer capability: 0x00 - SPEECH
1 > Protocol Discriminator: Q.931 (8) len=40
1 > Call Ref: len= 1 (reference 3/0x3) (Originator)
1 > Message type: SETUP (5)
1 > [04 03 80 90 a3]
1 > Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer
capability: Speech (0)
1 > Ext: 1 Trans mode/rate: 64kbps,
circuit-mode (16)
1 > Ext: 1 User information layer 1: A-Law
(35)
1 > [18 01 81]
1 > Channel ID (len= 3) [ Ext: 1 IntID: Implicit, Other Spare: 0,
Preferred Dchan: 0
1 > ChanSel: B1 channel
1 ]
1 > [6c 0c 21 81 30 39 32 32 38 32 31 35 33 35]
1 > Calling Number (len=14) [ Ext: 0 TON: National Number (2) NPI:
ISDN/Telephony Numbering Plan (E.164/E.163) (1)
1 > Presentation: Presentation permitted, user
number passed network screening (1) 'xxxx' ]
1 > [70 0c 80 30 39 30 39 36 34 35 34 35 36 36]
1 > Called Number (len=14) [ Ext: 1 TON: Unknown Number Type (0) NPI:
Unknown Number Plan (0) 'yyyy' ]
-- Called g1/yyyy
1 < Protocol Discriminator: Q.931 (8) len=10
1 < Call Ref: len= 1 (reference 131/0x83) (Terminator)
1 < Message type: RELEASE COMPLETE (90)
1 < [08 04 82 b9 b9 a3]
1 < Cause (len= 6) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the local user (2)
1 < Ext: 1 Cause: Bearer capability not authorized
(57), class = Service or Option not Available (3) ]
1 < Cause data 1: b9 (185)
1 < Cause data 2: a3 (163)
1 -- Processing IE 8 (cs0, Cause)
-- Channel 0/1, span 1 got hangup, cause 57
-- Channel 0/1, span 1 received AOC-E charging 0 units
1 NEW_HANGUP DEBUG: Calling q931_hangup, ourstate Null, peerstate Null
1 NEW_HANGUP DEBUG: Destroying the call, ourstate Null, peerstate Null
-- Hungup 'Zap/1-1'
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing Hangup("SIP/1002-09cd9350", "") in new stack
== Spawn extension (internal, yyyy, 3) exited non-zero on
'SIP/1002-09cd9350'
_______________________________________________
Bristuff-users mailing list
Bristuff-users@lists.three-dimensional.net http://lists.three-dimensional.net/mailman/listinfo/bristuff-users
Posted: Wed Jan 30, 2008 8:03 am Post subject: [Bristuff-users] Outbound dialing problem
On Wed, 2008-01-30 at 17:55 +1100, Redmond, David R wrote:
Quote:
Hi Everyone,
I have deployed BRIStuff (1.2.26-BRIstuffed-0.3.0-PRE-1y-p) on a CentOS5
server with a Cologne based HFC card. I am able to receive calls
without a problem, but when making a call I get the following below. I
have had the telco (NTT in Japan) check the ISDN line and confirm that
it is functioning and an engineer came and made/received calls on the
line.
[...]
1 > Message type: SETUP (5)
1 > [04 03 80 90 a3]
1 > Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer
capability: Speech (0)
1 > Ext: 1 Trans mode/rate: 64kbps,
circuit-mode (16)
1 > Ext: 1 User information layer 1: A-Law
(35)
As far as I know, Japan uses G.711 u-law, not A-law. Which seems to fit
the answer of your telco:
Quote:
1 < Message type: RELEASE COMPLETE (90)
1 < [08 04 82 b9 b9 a3]
1 < Cause (len= 6) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the local user (2)
1 < Ext: 1 Cause: Bearer capability not authorized
(57), class = Service or Option not Available (3) ]
Also that incoming calls do work points in that direction (because the
G.711 law is taken from the incoming SETUP).
To fix this, try to set the b-channels to u-law in /etc/zaptel.conf:
bchan=1,2
mulaw=1,2
dchan=3
Not sure if this helps, it might be necessary to change the default law
in the zaphfc/zaphfc.c source.
Posted: Wed Jan 30, 2008 8:45 am Post subject: [Bristuff-users] Outbound dialing problem
Hi Michael,
Thanks for the quick reply. Changing the /etc/zaptel.conf has allowed
me to dial a number from the Asterisk console. I will be in the office
tomorrow to confirm how the dialing behaves from a handset.
Thanks very much!
Cheers,
David
-----Original Message-----
From: Michael Neuhauser [mailto:mike@firmix.at]
Sent: Wednesday, 30 January 2008 6:03 PM
To: Redmond, David R
Cc: bristuff-users@lists.three-dimensional.net
Subject: Re: [Bristuff-users] Outbound dialing problem
On Wed, 2008-01-30 at 17:55 +1100, Redmond, David R wrote:
Quote:
Hi Everyone,
I have deployed BRIStuff (1.2.26-BRIstuffed-0.3.0-PRE-1y-p) on a
CentOS5
Quote:
server with a Cologne based HFC card. I am able to receive calls
without a problem, but when making a call I get the following below.
I
Quote:
have had the telco (NTT in Japan) check the ISDN line and confirm that
it is functioning and an engineer came and made/received calls on the
line.
[...]
1 > Message type: SETUP (5)
1 > [04 03 80 90 a3]
1 > Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer
capability: Speech (0)
1 > Ext: 1 Trans mode/rate: 64kbps,
circuit-mode (16)
1 > Ext: 1 User information layer 1:
A-Law
Quote:
(35)
As far as I know, Japan uses G.711 u-law, not A-law. Which seems to fit
the answer of your telco:
Quote:
1 < Message type: RELEASE COMPLETE (90)
1 < [08 04 82 b9 b9 a3]
1 < Cause (len= 6) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the local user (2)
1 < Ext: 1 Cause: Bearer capability not authorized
(57), class = Service or Option not Available (3) ]
Also that incoming calls do work points in that direction (because the
G.711 law is taken from the incoming SETUP).
To fix this, try to set the b-channels to u-law in /etc/zaptel.conf:
bchan=1,2
mulaw=1,2
dchan=3
Not sure if this helps, it might be necessary to change the default law
in the zaphfc/zaphfc.c source.
Thanks for the quick reply. Changing the /etc/zaptel.conf has allowed
me to dial a number from the Asterisk console. I will be in the office
tomorrow to confirm how the dialing behaves from a handset.
Thanks very much!
Cheers,
David
-----Original Message-----
From: Michael Neuhauser [mailto:mike@firmix.at]
Sent: Wednesday, 30 January 2008 6:03 PM
To: Redmond, David R
Cc: bristuff-users@lists.three-dimensional.net
Subject: Re: [Bristuff-users] Outbound dialing problem
On Wed, 2008-01-30 at 17:55 +1100, Redmond, David R wrote:
Quote:
Hi Everyone,
I have deployed BRIStuff (1.2.26-BRIstuffed-0.3.0-PRE-1y-p) on a
CentOS5
Quote:
server with a Cologne based HFC card. I am able to receive calls
without a problem, but when making a call I get the following below.
I
Quote:
have had the telco (NTT in Japan) check the ISDN line and confirm that
it is functioning and an engineer came and made/received calls on the
line.
[...]
1 > Message type: SETUP (5)
1 > [04 03 80 90 a3]
1 > Bearer Capability (len= 5) [ Ext: 1 Q.931 Std: 0 Info transfer
capability: Speech (0)
1 > Ext: 1 Trans mode/rate: 64kbps,
circuit-mode (16)
1 > Ext: 1 User information layer 1:
A-Law
Quote:
(35)
As far as I know, Japan uses G.711 u-law, not A-law. Which seems to fit
the answer of your telco:
Quote:
1 < Message type: RELEASE COMPLETE (90)
1 < [08 04 82 b9 b9 a3]
1 < Cause (len= 6) [ Ext: 1 Coding: CCITT (ITU) standard (0) 0: 0
Location: Public network serving the local user (2)
1 < Ext: 1 Cause: Bearer capability not authorized
(57), class = Service or Option not Available (3) ]
Also that incoming calls do work points in that direction (because the
G.711 law is taken from the incoming SETUP).
To fix this, try to set the b-channels to u-law in /etc/zaptel.conf:
bchan=1,2
mulaw=1,2
dchan=3
Not sure if this helps, it might be necessary to change the default law
in the zaphfc/zaphfc.c source.
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
