[asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Hi,
after I fixed my problem with the playback() application, I now have the
next strange one.
When I dial the number of our client, located in another town, I get a
connection to the asterisk server, I can talk to my client or listen to
his mailbox.
If some in the town of this client calls him, he gets the ISDN error
"service not available".
Out office is connected to he office via vpn, and so I connected a sip
phone to his asterisk server. Now this phone is in the same town and
when I dial his external number (to make sure it is an ISDN connection),
I hear a single ring tone, then the phone is connected but I here nothing.
Here is the output of "capi debug":
-- Executing [EMAIL PROTECTED]:1] Set("SIP/user1-0827eb08",
"CALLERID(num)=7253940397") in new stack
-- Executing [EMAIL PROTECTED]:2] Dial("SIP/user1-0827eb08",
"CAPI/g1/7253940397:940388|60|tr") in new stack
-- Called g1/7253940397:940388
== ISDN5#01: Incoming call '072539403' -> '940388'
-- Executing [EMAIL PROTECTED]:1] Answer("CAPI/ISDN5#01/940388-3", "")
in new stack
== ISDN5#01: Answering for 940388
-- Executing [EMAIL PROTECTED]:2] Wait("CAPI/ISDN5#01/940388-3", "1")
in new stack
== ISDN5#01: Setting up echo canceller (PLCI=0x305, function=1,
options=4, tail=64)
== ISDN5#01: Setting up DTMF detector (PLCI=0x305, flag=1)
-- ISDN5#01: Echo canceller successfully set up (PLCI=0x305)
== ISDN5#02: Setting up echo canceller (PLCI=0x205, function=1,
options=4, tail=64)
== ISDN5#02: Setting up DTMF detector (PLCI=0x205, flag=1)
-- CAPI/ISDN5#02/940388-2 answered SIP/user1-0827eb08
-- ISDN5#02: Echo canceller successfully set up (PLCI=0x205)
-- Executing [EMAIL PROTECTED]:3] GotoIfTime("CAPI/ISDN5#01/940388-3",
"17:00-18:00|*|*|*?from-extern|940388|6") in new stack
-- Executing [EMAIL PROTECTED]:4] Dial("CAPI/ISDN5#01/940388-3",
"SIP/VERKAUF|20|tr") in new stack
-- Called VERKAUF
-- SIP/VERKAUF-082841a0 is ringing
-- SIP/VERKAUF-082841a0 is ringing
-- SIP/VERKAUF-082841a0 is ringing
== ISDN5#02: CAPI Hangingup for PLCI=0x205 in state 2
== Spawn extension (local, 940388, 2) exited non-zero on
'SIP/user1-0827eb08'
What is the difference between an isdn call starting in the same area
and a call from my office?
We are using a EICON DIVA Server 4 BRI with the current driver and an
asterisk 1.4.13.
Here is the start of the capi.conf
[General]
nationalprefix=0
internationalprefix=00
rxgain=0.8
txgain=0.8
language=de
immediate=yes
faxdetect=off
[ISDN1]
incomingmsn=*
context=from-extern
ntmode=yes
controller=1
group=1
callgroup=1
accountcode=ISDN1
echocancel=yes
echosquelch=1
echotail=64
devices=2
Thanks for any suggestions,
Stefan
--
in-put GbR - Das Linux-Systemhaus
Stefan-Michael Guenther
Geschaeftsfuehrer
Moltkestrasse 49 D-76133 Karlsruhe
Tel./Fax : +49 (0)721 / 83044 - 98/93
http://www.in-put.de
Schulungen Installationen
Beratung Support
Voice-over-IP-Loesungen
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Hi, Armin wrote: >How does your dialplan look like? If you have e.g. > exten => _.,1, >in the context for capi incoming calls, then asterisk (chan-capi) >accept these calls even if not all numbers are dialed (transmitted) >yet. > we found the reason for our problem, but not yet the solution, maybe you have an idea. When we call the the asterisk from a mobile phone, the dialed number is transfered in one block, so asterisk "sees" the whole number and everything is fine. When you use a "normal" phone, the digits you have dialed are often not transfered in one block, but one after the other. If this transfer takes too long, the isdn card/the driver/the capi doesn't get the whole number and only transfers those digits that have already been receivec. Is there a chance to tell the isdn card/the driver/the capi to wait longer? BTW: Which component (capi/driver/card) sets this timeout? Thanks for your help, Stefan -- in-put GbR - Das Linux-Systemhaus Stefan-Michael Guenther Geschaeftsfuehrer Moltkestrasse 49 D-76133 Karlsruhe Tel./Fax : +49 (0)721 / 83044 - 98/93 http://www.in-put.de Schulungen Installationen Beratung Support Voice-over-IP-Loesungen ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
On Thu, 13 Dec 2007, Stefan Guenther wrote: > Hi, > > Armin wrote: > >How does your dialplan look like? If you have e.g. > > exten => _.,1, > >in the context for capi incoming calls, then asterisk (chan-capi) > >accept these calls even if not all numbers are dialed (transmitted) >yet. > > > we found the reason for our problem, but not yet the solution, maybe you > have an idea. > > When we call the the asterisk from a mobile phone, the dialed number is > transfered in one block, so asterisk "sees" the whole number and > everything is fine. > > When you use a "normal" phone, the digits you have dialed are often not > transfered in one block, but one after the other. If this transfer takes > too long, the isdn card/the driver/the capi doesn't get the whole number > and only transfers those digits that have already been receivec. > > Is there a chance to tell the isdn card/the driver/the capi to wait longer? > BTW: Which component (capi/driver/card) sets this timeout? Again, same question. How does your dialplan look like? If you have a rule _. (which means 4 digits OR MORE), then there is a match even if other digits follow. Make sure your dialplan will accept the call only if all digits are dialed. Armin ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Hi,
Armin wrote:
>Again, same question. How does your dialplan look like?
>If you have a rule _. (which means 4 digits OR MORE), then there
>is a match even if other digits follow. Make sure your dialplan
>will accept the call only if all digits are dialed.
>
here is the relevant part:
; Abschnitt fuer das Analogfax
exten => 940325,1,ANSWER()
exten => 940325,2,WAIT(1)
exten => 940325,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
exten => 940325,4,HANGUP()
; Alle weiteren Anschluesse (SIP)
exten => _9403XX,1,ANSWER()
exten => _9403XX,2,SET(CHANNEL(language)=de))
exten => _9403XX,3,DIAL(${SIP${EXTEN:4}},30,tr)
exten => _9403XX,4,HANGUP()
That's how we started. We then had incoming calls, e.g. 94033 according
to the cdr logfile. But most of the calls come in with the correct
number e.g. 940331.
We have one caller where the transfered number is always to short.
Everytime he dials 930331, the number comes in as 94033. So I inserted
exten => 940331,1,ANSWER()
exten => 940331,2,WAIT(1)
exten => 940331,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
exten => 940331,4,HANGUP()
at the beginning of the file, but still the call came in as 94033.
Stefan
--
in-put GbR - Das Linux-Systemhaus
Stefan-Michael Guenther
Geschaeftsfuehrer
Moltkestrasse 49 D-76133 Karlsruhe
Tel./Fax : +49 (0)721 / 83044 - 98/93
http://www.in-put.de
Schulungen Installationen
Beratung Support
Voice-over-IP-Loesungen
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
On Thu, Dec 13, 2007 at 10:26:59AM -0500, Steve Totaro wrote:
> Stefan Guenther wrote:
> > exten => 940331,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
> How do your zap conf files look?
chan_capi is used in this thread.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Stefan Guenther wrote:
> Hi,
>
> Armin wrote:
> >Again, same question. How does your dialplan look like?
> >If you have a rule _. (which means 4 digits OR MORE), then there
> >is a match even if other digits follow. Make sure your dialplan
> >will accept the call only if all digits are dialed.
> >
> here is the relevant part:
>
> ; Abschnitt fuer das Analogfax
> exten => 940325,1,ANSWER()
> exten => 940325,2,WAIT(1)
> exten => 940325,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
> exten => 940325,4,HANGUP()
>
> ; Alle weiteren Anschluesse (SIP)
> exten => _9403XX,1,ANSWER()
> exten => _9403XX,2,SET(CHANNEL(language)=de))
> exten => _9403XX,3,DIAL(${SIP${EXTEN:4}},30,tr)
> exten => _9403XX,4,HANGUP()
>
> That's how we started. We then had incoming calls, e.g. 94033 according
> to the cdr logfile. But most of the calls come in with the correct
> number e.g. 940331.
> We have one caller where the transfered number is always to short.
> Everytime he dials 930331, the number comes in as 94033. So I inserted
>
> exten => 940331,1,ANSWER()
> exten => 940331,2,WAIT(1)
> exten => 940331,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
> exten => 940331,4,HANGUP()
>
> at the beginning of the file, but still the call came in as 94033.
>
> Stefan
>
>
>
How do your zap conf files look?
Thanks,
Steve Totaro
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Tzafrir Cohen wrote:
> On Thu, Dec 13, 2007 at 10:26:59AM -0500, Steve Totaro wrote:
>
>> Stefan Guenther wrote:
>>
>
>
>>> exten => 940331,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
>>>
>
>
>> How do your zap conf files look?
>>
>
> chan_capi is used in this thread.
>
>
I have never used chan_capi, just trying to help. Are there settings
such as overlapdialing such as chan_zap?
Thanks,
Steve Totaro
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
On Thu, 13 Dec 2007, Stefan Guenther wrote:
> Hi,
>
> Armin wrote:
> >Again, same question. How does your dialplan look like?
> >If you have a rule _. (which means 4 digits OR MORE), then there
> >is a match even if other digits follow. Make sure your dialplan
> >will accept the call only if all digits are dialed.
> >
> here is the relevant part:
>
> ; Abschnitt fuer das Analogfax
> exten => 940325,1,ANSWER()
> exten => 940325,2,WAIT(1)
> exten => 940325,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
> exten => 940325,4,HANGUP()
>
> ; Alle weiteren Anschluesse (SIP)
> exten => _9403XX,1,ANSWER()
> exten => _9403XX,2,SET(CHANNEL(language)=de))
> exten => _9403XX,3,DIAL(${SIP${EXTEN:4}},30,tr)
> exten => _9403XX,4,HANGUP()
>
> That's how we started. We then had incoming calls, e.g. 94033 according
> to the cdr logfile. But most of the calls come in with the correct
> number e.g. 940331.
> We have one caller where the transfered number is always to short.
> Everytime he dials 930331, the number comes in as 94033. So I inserted
>
> exten => 940331,1,ANSWER()
> exten => 940331,2,WAIT(1)
> exten => 940331,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
> exten => 940331,4,HANGUP()
>
> at the beginning of the file, but still the call came in as 94033.
That looks corrct so far, numbers with just 94033 should not be accepted,
because of no match.
What type of ISDN line do you have?
And how is chan-capi (capi.conf) configured?
BTW, why do you Answer() all calls directly?
Armin
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
On Thu, 13 Dec 2007, Stefan Guenther wrote: Hi, Armin wrote: >That looks corrct so far, numbers with just 94033 should not be >accepted, because of no match. > I then added a context to match those, too. Otherwise I would loose these calls. >What type of ISDN line do you have? > 4 BRI (Anlagenanschluß) connected to an EICON 4 BRI8M Okay, but then the setting in capi.conf isdnmode=MSN is wrong. For 'Anlagenanschluss' you need isdnmode=did >And how is chan-capi (capi.conf) configured? > [General] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 language=deA These options are no general options, these are for the port sections only: immediate=yes ;immediate=yes faxdetect=off [ISDN1] incomingmsn=* context=from-extern isdnmode=MSN controller=1 group=1 callgroup=1 accountcode=ISDN1 echocancel=yes echosquelch=1 Both of these do not make sense. Either your hardware does not provide echo-cancel and you use echosquelch (which is something I cannot recommend) or you have a DIVA with hardware echo-cancel and you set echocancel=yes. echotail=64 devices=2 [cut] ISDN3-5 like ISDN1 ISDN2 is in NT mode. >BTW, why do you Answer() all calls directly? > Hm, I was used to put an ANSWER() in front of every PLAYBACK(), BACKGROUND(), VOICEMAILMAIN() and so on. And after I while I asked myself whether it wouldn't be a good idea to put ANSWER() in front of DIAL(), too, just to be sure that asterisk has control of the call. No good idea? Could it cause an trouble? The wiki doesn't mention any disadvantages. If you want to play something to the caller (without having reversed early-B3 possibility), you need to ANSWER(). But if the caller just should hear the ringing tone, let Dial() handle this. E.g., if the extension is busy, the caller must pay for the connection because of the ANSWER(). Armin ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
On Thu, 13 Dec 2007, Steve Totaro wrote:
> Tzafrir Cohen wrote:
>> On Thu, Dec 13, 2007 at 10:26:59AM -0500, Steve Totaro wrote:
>>
>>> Stefan Guenther wrote:
>>>
>>
>>
exten => 940331,3,DIAL(CAPI/g2/${EXTEN:4},20,tr)
>>
>>
>>> How do your zap conf files look?
>>>
>>
>> chan_capi is used in this thread.
>>
>>
> I have never used chan_capi, just trying to help. Are there settings
> such as overlapdialing such as chan_zap?
As far as I know overlapdialing is for outgoing calls on ZAP only, right?
chan-capi does not have this option. If you want to give additional digits
in/after Dial(), you just use the /o option in Dial() command.
Armin
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Hi, Armin wrote: >That looks corrct so far, numbers with just 94033 should not be >accepted, because of no match. > I then added a context to match those, too. Otherwise I would loose these calls. >What type of ISDN line do you have? > 4 BRI (Anlagenanschluß) connected to an EICON 4 BRI8M >And how is chan-capi (capi.conf) configured? > [General] nationalprefix=0 internationalprefix=00 rxgain=0.8 txgain=0.8 language=de immediate=yes ;immediate=yes faxdetect=off [ISDN1] incomingmsn=* context=from-extern isdnmode=MSN controller=1 group=1 callgroup=1 accountcode=ISDN1 echocancel=yes echosquelch=1 echotail=64 devices=2 [cut] ISDN3-5 like ISDN1 ISDN2 is in NT mode. >BTW, why do you Answer() all calls directly? > Hm, I was used to put an ANSWER() in front of every PLAYBACK(), BACKGROUND(), VOICEMAILMAIN() and so on. And after I while I asked myself whether it wouldn't be a good idea to put ANSWER() in front of DIAL(), too, just to be sure that asterisk has control of the call. No good idea? Could it cause an trouble? The wiki doesn't mention any disadvantages. Stefan -- in-put GbR - Das Linux-Systemhaus Stefan-Michael Guenther Geschaeftsfuehrer Moltkestrasse 49 D-76133 Karlsruhe Tel./Fax : +49 (0)721 / 83044 - 98/93 http://www.in-put.de Schulungen Installationen Beratung Support Voice-over-IP-Loesungen ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Hi, Armin wrote: >Okay, but then the setting in capi.conf > isdnmode=MSN >is wrong. For 'Anlagenanschluss' you need > isdnmode=did > Okay , I changed that. >These options are no general options, these are for the port sections >only: > > immediate=yes > The example capi.conf says about this parameter: ;immediate=yes ;DID: immediate start of pbx with extension 's' if no ; digits were received on incoming call (no destination ; number yet) ;MSN: start pbx on CONNECT_IND and don't wait for ; SETUP/SENDING-COMPLETE. info like REDIRECTINGNUMBER ; may be lost, but this is necessary for ; drivers/pbx/telco which does not send SETUP or ; SENDING-COMPLETE. Since I still face the problem, that asterisk doesn't get all digits of a telephone number, do you think that switching from MSN to DID will have any influence on this? Because with MSN the pbx wont' find for a "SEDNING-COMPLETE"? Sounds to me as if the pbx would react on incomplete numbers, too, which is exactly me problem! Thanks for the hint on ANSWER(). Although it might keep people from calling me day & night, because they would have to pay anyway, even when the phone is busy ;-)) Stefan -- in-put GbR - Das Linux-Systemhaus Stefan-Michael Guenther Geschaeftsfuehrer Moltkestrasse 49 D-76133 Karlsruhe Tel./Fax : +49 (0)721 / 83044 - 98/93 http://www.in-put.de Schulungen Installationen Beratung Support Voice-over-IP-Loesungen ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
On Thu, 13 Dec 2007, Stefan Guenther wrote: > Hi, > > Armin wrote: > >Okay, but then the setting in capi.conf > > isdnmode=MSN > >is wrong. For 'Anlagenanschluss' you need > > isdnmode=did > > > Okay , I changed that. > > >These options are no general options, these are for the port sections > >only: > > > immediate=yes > > > The example capi.conf says about this parameter: > > ;immediate=yes ;DID: immediate start of pbx with extension 's' if no >; digits were received on incoming call (no destination >; number yet) > ;MSN: start pbx on CONNECT_IND and don't wait for >; SETUP/SENDING-COMPLETE. info like REDIRECTINGNUMBER >; may be lost, but this is necessary for >; drivers/pbx/telco which does not send SETUP or >; SENDING-COMPLETE. > > Since I still face the problem, that asterisk doesn't get all digits of > a telephone number, do you think that switching from MSN to DID will > have any influence on this? Because with MSN the pbx wont' find for a > "SEDNING-COMPLETE"? Sounds to me as if the pbx would react on incomplete > numbers, too, which is exactly me problem! If you have a DID line (Anlagenanschluss), you need to set isdnmode=did. Otherwise chan-capi will not wait for additional digits. In DID mode, chan-capi will collect all digits until a match is found in the dialplan. If a match would be possible if further digits are received, chan-capi will wait. If a match is not possible any more, the call is now ignored by chan-capi (maybe another CAPI application is interested). > Thanks for the hint on ANSWER(). Although it might keep people from > calling me day & night, because they would have to pay anyway, even when > the phone is busy ;-)) If they know that they have to pay ;-) Armin ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Does this number (you are dialing) has been ported from a different Telco?
When you dial from the other city and you get "service not available" you
may be dialing from a different Telco that either has no route aggreement
for the dialed network, or the number portability database (of Out of city
Operator) is not up to date.
Can you confirm this two things?
On Dec 5, 2007 10:05 PM, Stefan Guenther <[EMAIL PROTECTED]> wrote:
> Hi,
>
> after I fixed my problem with the playback() application, I now have the
> next strange one.
>
> When I dial the number of our client, located in another town, I get a
> connection to the asterisk server, I can talk to my client or listen to
> his mailbox.
>
> If some in the town of this client calls him, he gets the ISDN error
> "service not available".
>
> Out office is connected to he office via vpn, and so I connected a sip
> phone to his asterisk server. Now this phone is in the same town and
> when I dial his external number (to make sure it is an ISDN connection),
> I hear a single ring tone, then the phone is connected but I here
> nothing.
>
> Here is the output of "capi debug":
>
> -- Executing [EMAIL PROTECTED]:1] Set("SIP/user1-0827eb08",
> "CALLERID(num)=7253940397") in new stack
> -- Executing [EMAIL PROTECTED]:2] Dial("SIP/user1-0827eb08",
> "CAPI/g1/7253940397:940388|60|tr") in new stack
> -- Called g1/7253940397:940388
> == ISDN5#01: Incoming call '072539403' -> '940388'
> -- Executing [EMAIL PROTECTED]:1] Answer("CAPI/ISDN5#01/940388-3", "")
> in new stack
> == ISDN5#01: Answering for 940388
> -- Executing [EMAIL PROTECTED]:2] Wait("CAPI/ISDN5#01/940388-3", "1")
> in new stack
> == ISDN5#01: Setting up echo canceller (PLCI=0x305, function=1,
> options=4, tail=64)
> == ISDN5#01: Setting up DTMF detector (PLCI=0x305, flag=1)
> -- ISDN5#01: Echo canceller successfully set up (PLCI=0x305)
> == ISDN5#02: Setting up echo canceller (PLCI=0x205, function=1,
> options=4, tail=64)
> == ISDN5#02: Setting up DTMF detector (PLCI=0x205, flag=1)
> -- CAPI/ISDN5#02/940388-2 answered SIP/user1-0827eb08
> -- ISDN5#02: Echo canceller successfully set up (PLCI=0x205)
> -- Executing [EMAIL PROTECTED]:3] GotoIfTime("CAPI/ISDN5#01/940388-3",
> "17:00-18:00|*|*|*?from-extern|940388|6") in new stack
> -- Executing [EMAIL PROTECTED]:4] Dial("CAPI/ISDN5#01/940388-3",
> "SIP/VERKAUF|20|tr") in new stack
> -- Called VERKAUF
> -- SIP/VERKAUF-082841a0 is ringing
> -- SIP/VERKAUF-082841a0 is ringing
> -- SIP/VERKAUF-082841a0 is ringing
> == ISDN5#02: CAPI Hangingup for PLCI=0x205 in state 2
> == Spawn extension (local, 940388, 2) exited non-zero on
> 'SIP/user1-0827eb08'
>
> What is the difference between an isdn call starting in the same area
> and a call from my office?
>
> We are using a EICON DIVA Server 4 BRI with the current driver and an
> asterisk 1.4.13.
>
> Here is the start of the capi.conf
>
> [General]
> nationalprefix=0
> internationalprefix=00
> rxgain=0.8
> txgain=0.8
> language=de
> immediate=yes
> faxdetect=off
>
> [ISDN1]
> incomingmsn=*
> context=from-extern
> ntmode=yes
> controller=1
> group=1
> callgroup=1
> accountcode=ISDN1
> echocancel=yes
> echosquelch=1
> echotail=64
> devices=2
>
>
> Thanks for any suggestions,
>
> Stefan
> --
>
>
> in-put GbR - Das Linux-Systemhaus
> Stefan-Michael Guenther
> Geschaeftsfuehrer
> Moltkestrasse 49 D-76133 Karlsruhe
> Tel./Fax : +49 (0)721 / 83044 - 98/93
> http://www.in-put.de
>
> Schulungen Installationen
> Beratung Support
> Voice-over-IP-Loesungen
>
>
> ___
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
--
Esta mensagem (incluindo quaisquer anexos) pode conter informação
confidencial para uso exclusivo do destinatário. Se não for o destinatário
pretendido, não deverá usar, distribuir ou copiar este e-mail. Se recebeu
esta mensagem por engano, por favor informe o emissor e elimine-a
imediatamente. Obrigado.
This e-mail message is intended only for individual(s) to whom it is
addressed and may contain information that is privileged, confidential,
proprietary, or otherwise exempt from disclosure under applicable law. If
you believe you have received this message in error, please advise the
sender by return e-mail and delete it from your mailbox. Thank you.
___
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
Hi, >Does this number (you are dialing) has been ported from a different >Telco? > > When you dial from the other city and you get "service not available" >you may be dialing from a different Telco that either has no route >aggreement for the dialed network, or the number portability database >(of Out of city Operator) is not up to date. > before we switched from the old pbx to the asterisk server, these people had no problems calling our client. With some more debugging we saw what happens with these specific calls. For some reason local calls and calls from a few other cities cause trouble, because asterisk doesn't get the whole number that has been dialed. If e.g. someone from the same town dials 123456, asterisk only gets 12345 or 1234. This extension doesn't exist in the dialplan and so the call fails. And this is not a single failure, it happens every time. The telco has checked the lines and they are okay, so it might be the ISDN card (EICON) or the driver. I have made a trace log from one of these failed calls and will forward it to EICON. Meanwhile we catch all these calls with the "i" extension. Stefan -- in-put GbR - Das Linux-Systemhaus Stefan-Michael Guenther Geschaeftsfuehrer Moltkestrasse 49 D-76133 Karlsruhe Tel./Fax : +49 (0)721 / 83044 - 98/93 http://www.in-put.de Schulungen Installationen Beratung Support Voice-over-IP-Loesungen ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Strange ISDN-problem with incoming calls out of the same city
On Fri, 7 Dec 2007, Stefan Guenther wrote: > Hi, > > >Does this number (you are dialing) has been ported from a different > >Telco? > > > > When you dial from the other city and you get "service not available" > >you may be dialing from a different Telco that either has no route > >aggreement for the dialed network, or the number portability database > >(of Out of city Operator) is not up to date. > > > before we switched from the old pbx to the asterisk server, these people > had no problems calling our client. > > With some more debugging we saw what happens with these specific calls. > For some reason local calls and calls from a few other cities cause > trouble, because asterisk doesn't get the whole number that has been > dialed. If e.g. someone from the same town dials 123456, asterisk only > gets 12345 or 1234. This extension doesn't exist in the dialplan and so > the call fails. And this is not a single failure, it happens every time. > > The telco has checked the lines and they are okay, so it might be the > ISDN card (EICON) or the driver. I have made a trace log from one of > these failed calls and will forward it to EICON. > > Meanwhile we catch all these calls with the "i" extension. How does your dialplan look like? If you have e.g. exten => _.,1, in the context for capi incoming calls, then asterisk (chan-capi) accept these calls even if not all numbers are dialed (transmitted) yet. Anyway, you talk about external calls, but you set ntmode=yes which does not make sense. Also, you should set isdnmode= to whatever isdn mode you have on your line. Please have a look at the example capi.conf of chan-capi package. Some of your general settings are possible in the interface sections only. Armin ___ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
