On 11/21/2012 10:53 AM, gincantalupo wrote:
Alex,
I had already tried it....reloading chan_dahdi.so module is enough...I
saw Asterisk was behaving differently after reload. To tell the truth,
setting pridialplan=unknown causes Asterisk to stop reading following
channels configuration...it says pridialplan is already unknown so it
stops evaluating chan_dahdi.conf file.... useless to say that all n+1
channels do not work. Maybe it is a bug but with that parameter set in
that way I cannot dial.
I'm sure Asterisk is dialling the right number:
[2012-11-21 09:05:29] VERBOSE[8314] logger.c: > [70 0b a1 33 34 39 3x 3x
3x 3x 3x 3x 34]
[2012-11-21 09:05:29] VERBOSE[8314] logger.c: > Called Number (len=13) [
Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan
(E.164/E.163) (1) '3497078884' ]
[2012-11-21 09:05:29] VERBOSE[8314] logger.c: q931.c:3134 q931_setup:
call 32781 on channel 6 enters state 1 (Call Initiated)
[2012-11-21 09:05:29] VERBOSE[8314] logger.c: -- Called 6/349xxxxxx4
I'm starting to think it is a telco problem... in case I'd change some
parameter like pridialplan or similar, shouldn't I just see a leading 0
in the frame like this:
[70 0b a1 *30* 33 34 39 3x 3x 3x 3x 3x 3x 34] added by Asterisk/DAHDI??
I've used this page as reference about frame fields:
http://www.acacia-net.com/wwwcla/protocol/q931_ie.htm
Thank you.
Giorgio Incantalupo
On 11/20/2012 05:23 PM, Alex Kauffmann wrote:
On 11/20/2012 8:03 AM, gincantalupo wrote:
Hi Leandro,
I'm sure nobody has added something... tried prilocaldialplan and
pridialplan but nothing changed.
Question: if pridialplan or prilocaldialplan would work, should I see
the 0 inside PRI frame with intense debug or it is hidden?
Yes...the technician did it...there is only one cable.
Maybe it is the socket circuitry that has something wrong but I do not
know ho to check.
Asap I'll be on site I'll do more testing.
Thank you
Giorgio
On 11/20/2012 01:13 PM, Leandro Dardini wrote:
That is a real mistery! I like a lots these cases when all seems not
working despite all being correctly configured, but you know first or
later you'll find the answer.
From your website, it seems you are selling/renting PBX based on
asterisk, so you can be sure nobody has messed with the asterisk or
dahdi source code adding a zero... I am sure you have already tried
with a brand new server.
Have you checked the pridialplan and prilocaldialplan setting?
If I was in your shoes, I'll get another server, with a PRI configured
as master and hook it at your PBX to really check if the zero is sent.
Does the technician try to make phone calls from the same network
cable you are using?
Leandro
2012/11/20 gincantalupo <gincantal...@fgasoftware.com
<mailto:gincantal...@fgasoftware.com>>
Hi Leandro,
thanks for your answer.
I already have tried those parameters but without any positive
result.
The telco technician has tried the line with its machine and it
worked...remote telco technicians say they get a leading zero...
I'm thinking there is something strange in the middle that adds
the zero but do not know what it is.
Strange is the fact that you can call some numbers with or without
the prefix zero...
Moreover we had no problem with the previous telco (fastweb).
So we can only call PTSN numbers....not mobile phones.
Giorgio
On 11/20/2012 11:12 AM, Leandro Dardini wrote:
2012/11/20 gincantalupo <gincantal...@fgasoftware.com
<mailto:gincantal...@fgasoftware.com>>
Hi all,
I have problems dialling out because my new telco (the
previous gave no problems) tells me my PBX adds a leading 0
and that's why I cannot dial out (but I can receive calls).
I make a small extensions.conf as a test:
exten => 666,1,Dial(DAHDI/g1/339xxxxxx)
but cannot dial out
Curious thing is that
exten => 666,1,Dial(DAHDI/g1/0233xxxxxx)
and
exten => 666,1,Dial(DAHDI/g1/233xxxxxx)
call the same number!!!
Line in use is a PRI.
My Asterisk version is 1.4.26.2
dahdi version: 2.2.0.2
wanpipe-3.4.6
I checked with intense pri debug and see no 0 inside
frames....
How can I really be SURE Asterisk is not adding some leading
zero?
Thank you.
Giorgio.
I have never heard of a way to automatically add digits when
using PRI, however can you check your chan_dahdi.conf about the
following lines:
internationalprefix =
nationalprefix =
localprefix =
If presents, try messing with them. If you are using the PRI in
Italy, every provider has PRI configured in its own way, some
time even the same provider is configuring PRI lines in multiple
times, but often the problems are on receiving the calls (like
calls with and without the area code, with or without the leading
zero, etc. etc.)
Leandro
--
The prilocaldialplan parameter is for inbound so you would have seen
no changes. Did you try:
pridialplan=unknown
Did you restart dahdi and asterisk after the changes?
Alex
--
Giorgio,
It looks like your pridialplan is net to national. You can see that in
the line from your log that reads:
"[2012-11-21 09:05:29] VERBOSE[8314] logger.c: > Called Number (len=13)
[Ext: 1 TON: National Number (2) NPI: ISDN/Telephony Numbering Plan
(E.164/E.163) (1) '3497078884' ]"
If I remember correctly, it should read "TON: Unknown Number Type" if
pridialplan was set to unknown. Unless this has changed, reloading
chan_dahdi will NOT reconfigure Signalling, PRI, and SS7 parameters.
You have to restart Asterisk.
Alex
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
