[chan-capi-users] Primux ISDN PRI adapter - Analog call in
Giancarlo Galvagno
g.galvagno at gts.it
Tue Aug 18 17:32:52 CEST 2009
After diggin a bit on google, I solved the problem
I modified extension_custom.conf adding the following lines
[from-isdn]
exten => _184714,1,Wait(3)
exten => _184714,2,Dial(SIP/${CHANNEL:20:3})
include=>from-pstn
Thanks a lot, bye
----- 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 2:28 PM
Subject: Re: [chan-capi-users] Primux ISDN PRI adapter - Analog call in
> On Tue, 18 Aug 2009, Giancarlo Galvagno wrote:
>> Sorry to ask again: I don't know what means
>> " You should try to use a dialplan which is not accepting a call with
>> incomplete destination number."
>> Colud you please explain how to do it ?
>
> See emails before:
>>> e.g.
>>> exten => _X.,1,...
>>> to
>>> exten => _018471XXXX,1,...
>
> and http://www.voip-info.org/wiki/view/Asterisk+Extension+Matching
>
> Armin
>
>> ----- 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 2:18 PM
>> Subject: Re: [chan-capi-users] Primux ISDN PRI adapter - Analog call in
>>
>>
>>> Hi,
>>>
>>> the log seems to be incomplete. I cannot see any 'answer', but the card
>>> shows that the call is answered. Maybe this is the reason for the card
>>> not
>>> to send remaining digits.
>>> You should try to use a dialplan which is not accepting a call with
>>> incomplete destination number.
>>>
>>> Armin
>>>
>>> On Tue, 18 Aug 2009, Giancarlo Galvagno wrote:
>>>> Armin
>>>> these are the lines subsequent
>>>>
>>>> BProtocol
>>>> B1protocol = 0x1
>>>> B2protocol = 0x1
>>>> B3protocol = 0x0
>>>> B1configuration = default
>>>> B2configuration = default
>>>> B3configuration = default
>>>> GlobalConfiguration = default
>>>> ConnectedNumber = <01 80>1732302
>>>> ConnectedSubaddress = default
>>>> LLC = default
>>>> AdditionalInfo
>>>> BChannelinformation = default
>>>> Keypadfacility = default
>>>> Useruserdata = default
>>>> Facilitydataarray = default
>>>> SendingComplete = default
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CAPI: ApplId=0x0002
>>>> Command=0x08
>>>> SubCommand=0x82 MsgNum=0x8211 NCCI=0x00000101
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: INFO_IND
>>>> ID=002
>>>> #0x8211 LEN=0016
>>>> Controller/PLCI/NCCI = 0x101
>>>> InfoNumber = 0x4004
>>>> InfoElement = <00>
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3152] logger.c: -- Executing
>>>> [s at from-trunk:3]
>>>> Wait("CAPI/ISDN1#30/1732302-3", "2") in new stack
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: INFO_RESP
>>>> ID=002
>>>> #0x8211 LEN=0012
>>>> Controller/PLCI/NCCI = 0x101
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: -- ISDN1#30: unhandled
>>>> INFO_IND 0x4004 (PLCI=0x101)
>>>> [Aug 18 14:06:45] VERBOSE[3082] logger.c: > chan_capi
>>>> devicestate
>>>> requested for ISDN1#30/1732302-3 is 'In use'
>>>> [Aug 18 14:06:45] VERBOSE[3082] logger.c: > chan_capi
>>>> devicestate
>>>> requested for ISDN1#30/1732302 is 'In use'
>>>> [Aug 18 14:06:45] VERBOSE[3082] logger.c: > chan_capi
>>>> devicestate
>>>> requested for ISDN1#30/1732302-3 is 'In use'
>>>> [Aug 18 14:06:45] VERBOSE[3082] logger.c: > chan_capi
>>>> devicestate
>>>> requested for ISDN1#30/1732302 is 'In use'
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CAPI: ApplId=0x0002
>>>> Command=0x08
>>>> SubCommand=0x82 MsgNum=0x8212 NCCI=0x00000101
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: INFO_IND
>>>> ID=002
>>>> #0x8212 LEN=0015
>>>> Controller/PLCI/NCCI = 0x101
>>>> InfoNumber = 0x800f
>>>> InfoElement = default
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: INFO_RESP
>>>> ID=002
>>>> #0x8212 LEN=0012
>>>> Controller/PLCI/NCCI = 0x101
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: -- ISDN1#30: info element
>>>> CONNECT ACK
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CAPI: ApplId=0x0002
>>>> Command=0x03
>>>> SubCommand=0x82 MsgNum=0x8213 NCCI=0x00000101
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CONNECT_ACTIVE_IND
>>>> ID=002
>>>> #0x8213 LEN=0015
>>>> Controller/PLCI/NCCI = 0x101
>>>> ConnectedNumber = default
>>>> ConnectedSubaddress = default
>>>> LLC = default
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CONNECT_ACTIVE_RESP
>>>> ID=002
>>>> #0x8213 LEN=0012
>>>> Controller/PLCI/NCCI = 0x101
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CAPI: ApplId=0x0002
>>>> Command=0x82
>>>> SubCommand=0x82 MsgNum=0x8214 NCCI=0x00010101
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CONNECT_B3_IND
>>>> ID=002
>>>> #0x8214 LEN=0013
>>>> Controller/PLCI/NCCI = 0x10101
>>>> NCPI = default
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CONNECT_B3_RESP
>>>> ID=002
>>>> #0x8214 LEN=0015
>>>> Controller/PLCI/NCCI = 0x10101
>>>> Reject = 0x0
>>>> NCPI = default
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CAPI: ApplId=0x0002
>>>> Command=0x83
>>>> SubCommand=0x82 MsgNum=0x8215 NCCI=0x00010101
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CONNECT_B3_ACTIVE_IND
>>>> ID=002
>>>> #0x8215 LEN=0013
>>>> Controller/PLCI/NCCI = 0x10101
>>>> NCPI = default
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: CONNECT_B3_ACTIVE_RESP
>>>> ID=002
>>>> #0x8215 LEN=0012
>>>> Controller/PLCI/NCCI = 0x10101
>>>>
>>>>
>>>> I see a couple of INFO_IND, but seems are in Hex
>>>>
>>>> [Aug 18 14:06:45] VERBOSE[3085] logger.c: INFO_IND
>>>> ID=002
>>>> #0x8211 LEN=0016
>>>> Controller/PLCI/NCCI = 0x101
>>>> InfoNumber = 0x4004
>>>> InfoElement = <00>
>>>>
>>>>
>>>> Do you know what they means ?
>>>>
>>>>
>>>> ----- 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 1:53 PM
>>>> Subject: Re: [chan-capi-users] Primux ISDN PRI adapter - Analog call in
>>>>
>>>>
>>>>> On Tue, 18 Aug 2009, Giancarlo Galvagno wrote:
>>>>>> 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 ?
>>>>>
>>>>> No, still the same. I don't think the number with the Primux is
>>>>> truncated.
>>>>> You should do the full debug log to see if the remaining digits really
>>>>> are
>>>>> not provided by e.g. INFO_IND messages afterwards.
>>>>> The reason for the full number with diva card may be because this card
>>>>> is
>>>>> configured to collect all numbers before presenting them to CAPI
>>>>> interface,
>>>>> which would not be the default case.
>>>>>
>>>>> If the Primux card really doesn't show remaining digits afterwards,
>>>>> then
>>>>> you
>>>>> should contact the vendor (the capi interface and driver is closed
>>>>> source
>>>>> here).
>>>>>
>>>>> Armin
>>>>>
>>>>>> ----- 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
>>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>
>>> _______________________________________________
>>> 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