[chan-capi-users] Primux ISDN PRI adapter - Analog call in
Giancarlo Galvagno
g.galvagno at gts.it
Tue Aug 18 13:47:17 CEST 2009
Armin
I still need your help
Two configuration, same version of Asterisk and same settings.+
1) machine with Eicon Diva, debug of capi
[Aug 18 13:42:32] VERBOSE[2762] logger.c: CONNECT_IND ID=002
#0xe268 LEN=0051
Controller/PLCI/NCCI = 0xc01
CIPValue = 0x4
CalledPartyNumber = <a1>173230224
CallingPartyNumber = <21 83>173262697
CalledPartySubaddress = default
CallingPartySubaddress = default
BC = <90 90 a3>
LLC = default
HLC = default
AdditionalInfo
BChannelinformation = default
Keypadfacility = default
Useruserdata = default
2) machine with Primux ISDN , debug of capi
CAPI: ApplId=0x0002 Command=0x02 SubCommand=0x82 MsgNum=0x801b
NCCI=0x00000101
CONNECT_IND ID=002 #0x801b LEN=0054
Controller/PLCI/NCCI = 0x101
CIPValue = 0x4
CalledPartyNumber = <a1>1732302
CallingPartyNumber = <21 83>173262697
CalledPartySubaddress = default
CallingPartySubaddress = default
BC = <90 90 a3>
LLC = default
HLC = defaul
Both the calls made from an analog phone, same number ( of course )
0173230224
As you can see, in the second case the number is truncated
This is why I believe the problem resides on the adapter configuration, not
in asterisk
Have you got any suggestion ?
----- Original Message -----
From: "Armin Schindler" <armin at melware.de>
To: "chan-capi users" <chan-capi-users at lists.melware.net>
Sent: Tuesday, August 18, 2009 9:44 AM
Subject: Re: [chan-capi-users] Primux ISDN PRI adapter - Analog call in
> Hello,
>
> On Tue, 18 Aug 2009, Giancarlo Galvagno wrote:
>> Armin,
>> thank you for your prompt reply
>> I believe this is not true: as you can see from this log, obtained with
>> the
>> Primux Trace utility
>>
>> ---------------------------------------- cut here
>>
>>
>>
>> Info number 800F
>> Info element 00
>> 473.16.41.256 Len=12 Appl=2 Num=B3AD v INFO_RESP
>> Controller/PLCI 00000101
>> 473.16.41.256 Len=15 Appl=2 Num=B3AE ^ CONNECT_ACT_IND
> ......
>
> no, I cannot see anthing in that trace regarding why the
> call is accepted. The trace just shows that the call is now active, but
> not
> why and when it was accepted.
> You should have a look at the asterisk verbose log with
> set verbose 5
> capi debug
> while receiving that call.
>
> Armin
>
>
>>> Hi,
>>>
>>> On Tue, 18 Aug 2009, Giancarlo Galvagno wrote:
>>>> I have a big problem with a Primux ISDN PRI adapter, Trixbox 1.4.
>>>> The adapter works fine for dialing out.
>>>> Also, it works fine for dialing in if I call from an ISDN line or a
>>>> cellphone
>>>> But when I dial from an analog phone, ( by example 0184716302 )Asterisk
>>>> receives only 0184716, not the last three digits: in this case, from
>>>> the
>>>> Asterisk side the IVR catch the call and I cannot reach my extension
>>>> 302
>>>> I have several times contacted the manufacturer of the Primux Card (
>>>> Gerdes ) but they did not find any suggestion.
>>>> Has someone in the past had the same problem ?
>>>
>>> that's not a problem of the card, but of the dialplan of Trixbox. The
>>> default dialplan seems to 'accept' any call from ISDN trunk. This means
>>> that
>>> even if digits follow, there was already a match in the dialplan and
>>> other
>>> digits are ignored. So you need to change the dialplan of Trixbox from
>>> e.g.
>>> exten => _X.,1,...
>>> to
>>> exten => _018471XXXX,1,...
>>>
>>> Armin
>>>
>>> _______________________________________________
>>> Chan-capi-users mailing list
>>> Chan-capi-users at lists.melware.net
>>> http://lists.melware.net/mailman/listinfo/chan-capi-users
>>>
>>
>>
>> _______________________________________________
>> Chan-capi-users mailing list
>> Chan-capi-users at lists.melware.net
>> http://lists.melware.net/mailman/listinfo/chan-capi-users
>>
> _______________________________________________
> Chan-capi-users mailing list
> Chan-capi-users at lists.melware.net
> http://lists.melware.net/mailman/listinfo/chan-capi-users
>
More information about the Chan-capi-users
mailing list