Posted: Sat Oct 28, 2006 6:48 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Hello,
I need to connect one diva server 4bri to a portuguese BRI interface.
The operator (PT) said that this bri is in point-to-multipoint mode
(S0). Previously one PBX has connected to that interface.
The asterisk and diva drivers are working ok but i cannot communicate
to outside via this bri. Xlite gives me the message: "call failed:
declined".
Anyone have experience with this setup?
What are the main parameters for bri card configuration?
D-channel protocol: ETSI-DSS1 or other?
Interface mode: NT or TE?
Direct Inward Dialing (DID): Yes ou no? (MSN ou DID?)
Thanks by any kind of help!
Best regards,
PS.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Sun Oct 29, 2006 9:26 am Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Pedro Silva ha scritto:
Quote:
Hello,
I need to connect one diva server 4bri to a portuguese BRI interface.
The operator (PT) said that this bri is in point-to-multipoint mode
(S0). Previously one PBX has connected to that interface.
The asterisk and diva drivers are working ok but i cannot communicate
to outside via this bri. Xlite gives me the message: "call failed:
declined".
Anyone have experience with this setup?
What are the main parameters for bri card configuration?
D-channel protocol: ETSI-DSS1 or other?
Interface mode: NT or TE?
Direct Inward Dialing (DID): Yes ou no? (MSN ou DID?)
Thanks by any kind of help!
Best regards,
PS.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
ETSI-DSS1 should work just fine. The interface mode is surely
TE.
The DID/MSN should not affect outgoing calls, I generally leave DID
off unless the telco company has that service active.
If you're using the diva server for linux package from eicon
(divas4linux, currently rel. 8.2), you should find a very
simple utility named "telsampl" under /usr/lib/eicon/divas
which you can run besides asterisk, to test outgoing calls.
You should run it with this command line: "telsampl -c x"
where x is the bri port you wish to test (1..4)
then at the prompt type "c" and enter a pstn number, e.g.
your mobile phone, then you can watch the log onscreen.
If the outgoing call works, then your isdn setup is correct,
and the problem is in asterisk. The message from xlite is not
meaningful, as it could occur on many situations.
You should watch the debug output on asterisk console.
Posted: Sun Oct 29, 2006 12:26 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Thanks Alberto!
I tested with telsampl like you said (with various configurations for
de diva) and this not works...:(
The trace is:
Enter destination address: 273xxxxxx
<--Conn_Req(273xxxxxx)
Connect_Con-->
[29]:Disc_Ind-->
<--Disc_Res
**********Call cleared***********
Any idea for the possible problem?
Thanks and best regards,
PS.
2006/10/29, Alberto Pastore <alberto@msoft-italia.com>:
Quote:
Pedro Silva ha scritto:
> Hello,
>
> I need to connect one diva server 4bri to a portuguese BRI interface.
> The operator (PT) said that this bri is in point-to-multipoint mode
> (S0). Previously one PBX has connected to that interface.
> The asterisk and diva drivers are working ok but i cannot communicate
> to outside via this bri. Xlite gives me the message: "call failed:
> declined".
> Anyone have experience with this setup?
> What are the main parameters for bri card configuration?
> D-channel protocol: ETSI-DSS1 or other?
> Interface mode: NT or TE?
> Direct Inward Dialing (DID): Yes ou no? (MSN ou DID?)
>
> Thanks by any kind of help!
> Best regards,
> PS.
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
I'm not sure about Portuguese operators standard, but I bet
ETSI-DSS1 should work just fine. The interface mode is surely
TE.
The DID/MSN should not affect outgoing calls, I generally leave DID
off unless the telco company has that service active.
If you're using the diva server for linux package from eicon
(divas4linux, currently rel. 8.2), you should find a very
simple utility named "telsampl" under /usr/lib/eicon/divas
which you can run besides asterisk, to test outgoing calls.
You should run it with this command line: "telsampl -c x"
where x is the bri port you wish to test (1..4)
then at the prompt type "c" and enter a pstn number, e.g.
your mobile phone, then you can watch the log onscreen.
If the outgoing call works, then your isdn setup is correct,
and the problem is in asterisk. The message from xlite is not
meaningful, as it could occur on many situations.
You should watch the debug output on asterisk console.
I tested with telsampl like you said (with various configurations for
de diva) and this not works...:(
The trace is:
Enter destination address: 273xxxxxx
<--Conn_Req(273xxxxxx)
Connect_Con-->
[29]:Disc_Ind-->
<--Disc_Res
**********Call cleared***********
Any idea for the possible problem?
Thanks and best regards,
PS.
Pedro Silva ha scritto:
> Hello,
>
> I need to connect one diva server 4bri to a portuguese BRI interface.
> The operator (PT) said that this bri is in point-to-multipoint mode
> (S0). Previously one PBX has connected to that interface.
> The asterisk and diva drivers are working ok but i cannot communicate
> to outside via this bri. Xlite gives me the message: "call failed:
> declined".
> Anyone have experience with this setup?
> What are the main parameters for bri card configuration?
> D-channel protocol: ETSI-DSS1 or other?
> Interface mode: NT or TE?
> Direct Inward Dialing (DID): Yes ou no? (MSN ou DID?)
>
> Thanks by any kind of help!
> Best regards,
> PS.
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
I'm not sure about Portuguese operators standard, but I bet
ETSI-DSS1 should work just fine. The interface mode is surely
TE.
The DID/MSN should not affect outgoing calls, I generally leave DID
off unless the telco company has that service active.
If you're using the diva server for linux package from eicon
(divas4linux, currently rel. 8.2), you should find a very
simple utility named "telsampl" under /usr/lib/eicon/divas
which you can run besides asterisk, to test outgoing calls.
You should run it with this command line: "telsampl -c x"
where x is the bri port you wish to test (1..4)
then at the prompt type "c" and enter a pstn number, e.g.
your mobile phone, then you can watch the log onscreen.
If the outgoing call works, then your isdn setup is correct,
and the problem is in asterisk. The message from xlite is not
meaningful, as it could occur on many situations.
You should watch the debug output on asterisk console.
Posted: Sun Oct 29, 2006 4:18 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Marco Mouta ha scritto:
Quote:
pls post your misdn.conf as well as extensions.conf
May be i can help.
Sou Português:)
On 10/29/06, *Pedro Silva* < pedromsilva1@gmail.com
<mailto:pedromsilva1@gmail.com>> wrote:
Thanks Alberto!
I tested with telsampl like you said (with various configurations for
de diva) and this not works...:(
The trace is:
Enter destination address: 273xxxxxx
<--Conn_Req(273xxxxxx)
Connect_Con-->
[29]:Disc_Ind-->
<--Disc_Res
**********Call cleared***********
Any idea for the possible problem?
Thanks and best regards,
PS.
I think Pedro is not using mISDN, he's using chan_capi, but
his problem arises before asterisk is involved.
Anyway, to get more info, try to open a second shell
and run /usr/lib/eicon/divas/xlog
then on the first shell redo the telsampl test, then
post the output of xlog off the list to my address
(alberto at msoft-italia.com)
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Sun Oct 29, 2006 4:41 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Olá Marco! :)
2006/10/29, Marco Mouta <marco.mouta@gmail.com>:
Quote:
pls post your misdn.conf as well as extensions.conf
The asterisk version that i used with trixbox dont't have
misdn.conf... I used capi.conf.
For now, i dont care about asterisk, because with the divas utility
telsampl i know that the problem is between diva card and BRI access.
So i need to solve first this problem and only after that im care with
asterisk... :)
Obrigado desde já pela disponibilidade de ajuda!
PS.
Quote:
May be i can help.
Sou Português:)
On 10/29/06, Pedro Silva < pedromsilva1@gmail.com> wrote:
> Thanks Alberto!
>
> I tested with telsampl like you said (with various configurations for
> de diva) and this not works...:(
> The trace is:
> Enter destination address: 273xxxxxx
> <--Conn_Req(273xxxxxx)
> Connect_Con-->
> [29]:Disc_Ind-->
> <--Disc_Res
> **********Call cleared***********
>
> Any idea for the possible problem?
> Thanks and best regards,
> PS.
>
> 2006/10/29, Alberto Pastore <alberto@msoft-italia.com>:
> > Pedro Silva ha scritto:
> > > Hello,
> > >
> > > I need to connect one diva server 4bri to a portuguese BRI interface.
> > > The operator (PT) said that this bri is in point-to-multipoint mode
> > > (S0). Previously one PBX has connected to that interface.
> > > The asterisk and diva drivers are working ok but i cannot communicate
> > > to outside via this bri. Xlite gives me the message: "call failed:
> > > declined".
> > > Anyone have experience with this setup?
> > > What are the main parameters for bri card configuration?
> > > D-channel protocol: ETSI-DSS1 or other?
> > > Interface mode: NT or TE?
> > > Direct Inward Dialing (DID): Yes ou no? (MSN ou DID?)
> > >
> > > Thanks by any kind of help!
> > > Best regards,
> > > PS.
> > > _______________________________________________
> > > --Bandwidth and Colocation provided by Easynews.com --
> > >
> > > asterisk-users mailing list
> > > To UNSUBSCRIBE or update options visit:
> > >
http://lists.digium.com/mailman/listinfo/asterisk-users
> > I'm not sure about Portuguese operators standard, but I bet
> > ETSI-DSS1 should work just fine. The interface mode is surely
> > TE.
> > The DID/MSN should not affect outgoing calls, I generally leave DID
> > off unless the telco company has that service active.
> >
> > If you're using the diva server for linux package from eicon
> > (divas4linux, currently rel. 8.2), you should find a very
> > simple utility named "telsampl" under /usr/lib/eicon/divas
> > which you can run besides asterisk, to test outgoing calls.
> >
> > You should run it with this command line: "telsampl -c x"
> > where x is the bri port you wish to test (1..4)
> > then at the prompt type "c" and enter a pstn number, e.g.
> > your mobile phone, then you can watch the log onscreen.
> >
> > If the outgoing call works, then your isdn setup is correct,
> > and the problem is in asterisk. The message from xlite is not
> > meaningful, as it could occur on many situations.
> > You should watch the debug output on asterisk console.
> >
> > That helped me a lot.
> >
> > Alberto.
> >
> >
> > --
> > --
> > Alberto Pastore
> > B-Press Srl - Gruppo MSoft
> > P.IVA 01697420030
> > P.le Lombardia, 4 - 28100 Novara - Italy
> > Tel. 0321-499508
> > Fax 0321-492974
> > http://www.msoft.it
> >
> > _______________________________________________
> > --Bandwidth and Colocation provided by Easynews.com --
> >
> > asterisk-users mailing list
> > To UNSUBSCRIBE or update options visit:
> >
http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>
http://lists.digium.com/mailman/listinfo/asterisk-users
>
--
Com os melhores cumprimentos,
Marco Mouta
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
Posted: Sun Oct 29, 2006 5:02 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Hello again Alberto!
Quote:
Anyway, to get more info, try to open a second shell
and run /usr/lib/eicon/divas/xlog
then on the first shell redo the telsampl test, then
post the output of xlog off the list to my address
(alberto at msoft-italia.com)
This is the xlog output:
4:1736:074 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
4:1736:074 - alloc cr in use =4
4:1736:076 - free cr in use =3
4:1736:077 - DELETEID ok: deleted Id:6 freeIds=eb
4:1736:078 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
4:1736:078 - alloc cr in use =4
4:1736:080 - free cr in use =3
4:1736:080 - DELETEID ok: deleted Id:6 freeIds=eb
4:1736:081 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
4:1736:081 - alloc cr in use =4
4:1736:083 - [1,0] dsp_assign 0016, 0, 2048
4:1736:083 - [1,0] CAI[00] 16 00 00 00 00 08
4:1736:084 - [1,0] Download 532 requested
4:1736:084 - MORE
4:1736:085 - SIG-X(029) 08 01 36 05 A1 04 03 80 90 A3 18 01 83 1E
02 80 83 70 0A 80 39 36 33 30 34 35 37 32 33
Q.931 CR36 SETUP
Sending complete
Bearer Capability 80 90 a3
Channel Id 83
Progress Indicator 80 83
Called Party Number 80 '963045723'
4:1736:085 - SIG-S 0->1 e:885
4:1736:087 - ACTIVATION_REQ
4:1744:147 - L1_DOWN
4:1744:150 - SIG-EVENT FFFF 08
4:1744:150 - SIG-EVENT FFFF 08
4:1744:150 - EVENT: Call failed in State 'Call initiated'
Link disconnected, Layer-1 error (cable or NT)
4:1744:150 - SIG-S 1->0 e:ffff
4:1744:151 - [1,0] dsp_release
4:1744:155 - free cr in use =3
4:1744:156 - DELETEID ok: deleted Id:6 freeIds=eb
I disconnect the rj45 cable from alcatel pbx and connect that to the
diva card (with alcatel pbx i can make calls normally). The green led
of the diva card is activated when i connect the cable. So i dont
understand why the message " Link disconnected, Layer-1 error (cable
or NT)"...
This debug is th same if the cable is connected to the NT or not.
Any ideas...? Thanks!
PS.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Sun Oct 29, 2006 7:20 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Finally this works!!! :)
Tanks to Alberto and Marco by your help!
The problems are:
- the cable was connected to the wong card port... :(
- the card config needs to be: ETSI; TE; Point-to-Point (I thought
that was point-to-multipoint).
Best regards,
PS.
2006/10/29, Pedro Silva <pedromsilva1@gmail.com>:
Quote:
Hello again Alberto!
> Anyway, to get more info, try to open a second shell
> and run /usr/lib/eicon/divas/xlog
> then on the first shell redo the telsampl test, then
> post the output of xlog off the list to my address
> (alberto at msoft-italia.com)
This is the xlog output:
4:1736:074 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
4:1736:074 - alloc cr in use =4
4:1736:076 - free cr in use =3
4:1736:077 - DELETEID ok: deleted Id:6 freeIds=eb
4:1736:078 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
4:1736:078 - alloc cr in use =4
4:1736:080 - free cr in use =3
4:1736:080 - DELETEID ok: deleted Id:6 freeIds=eb
4:1736:081 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
4:1736:081 - alloc cr in use =4
4:1736:083 - [1,0] dsp_assign 0016, 0, 2048
4:1736:083 - [1,0] CAI[00] 16 00 00 00 00 08
4:1736:084 - [1,0] Download 532 requested
4:1736:084 - MORE
4:1736:085 - SIG-X(029) 08 01 36 05 A1 04 03 80 90 A3 18 01 83 1E
02 80 83 70 0A 80 39 36 33 30 34 35 37 32 33
Q.931 CR36 SETUP
Sending complete
Bearer Capability 80 90 a3
Channel Id 83
Progress Indicator 80 83
Called Party Number 80 '963045723'
4:1736:085 - SIG-S 0->1 e:885
4:1736:087 - ACTIVATION_REQ
4:1744:147 - L1_DOWN
4:1744:150 - SIG-EVENT FFFF 08
4:1744:150 - SIG-EVENT FFFF 08
4:1744:150 - EVENT: Call failed in State 'Call initiated'
Link disconnected, Layer-1 error (cable or NT)
4:1744:150 - SIG-S 1->0 e:ffff
4:1744:151 - [1,0] dsp_release
4:1744:155 - free cr in use =3
4:1744:156 - DELETEID ok: deleted Id:6 freeIds=eb
I disconnect the rj45 cable from alcatel pbx and connect that to the
diva card (with alcatel pbx i can make calls normally). The green led
of the diva card is activated when i connect the cable. So i dont
understand why the message " Link disconnected, Layer-1 error (cable
or NT)"...
This debug is th same if the cable is connected to the NT or not.
Any ideas...? Thanks!
PS.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Tue Oct 31, 2006 12:39 am Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Hello,
One problem is solved and another appears... :(
I cannot receive incoming calls on trixbox. I defined one incoming
route (any DID/any CID) and forwading these calls to a SIP extension.
With capi and sip debug in "asterisk -r" console i dont detect any
incoming activity...
In xlog console i have the following debug:
0:1898:127 - SIG-R(034) 08 01 0D 05 A1 04 03 80 90 A3 18 01 81 6C 0B
00 83 39 36 33 30 34 35 37 32 33 70 02 81 30 7D 02 91 81
Q.931 CR0d SETUP
Sending complete
Bearer Capability 80 90 a3
Channel Id 81
Calling Party Number 00 83 '963045723'
Called Party Number 81 '0'
HLC 91 81
0:1898:127 - SIG-S 0->6 e:805
0:1898:130 - CREATEID ok: context:1f assigned Id:3 freeIds=ec
0:1898:130 - alloc cr in use =4
0:1898:133 - SIG-X(008) 08 01 8D 45 08 02 80 95
Q.931 CR8d DISC
Cause 80 95 'Call rejected'
0:1898:133 - SIG-x(008) 08 01 8D 5A 08 02 80 D8
Q.931 CR8d REL_COM
Cause 80 d8 'Incompatible destination'
0:1898:133 - SIG-S 6->0 e:8c5
0:1898:134 - D-X(012) 00 01 14 16 08 01 8D 5A 08 02 80 D8
0:1898:135 - free cr in use =3
0:1898:135 - DELETEID ok: deleted Id:4 freeIds=ec
0:1898:155 - D-R(004) 00 01 01 16
So the problem appears to be "Incompatible destination"... but is
problem in asterisk or is before asterisk, on diva card...?
Tanks by any possible help!
Best regards,
PS.
2006/10/29, Pedro Silva <pedromsilva1@gmail.com>:
Quote:
Finally this works!!! :)
Tanks to Alberto and Marco by your help!
The problems are:
- the cable was connected to the wong card port... :(
- the card config needs to be: ETSI; TE; Point-to-Point (I thought
that was point-to-multipoint).
Best regards,
PS.
2006/10/29, Pedro Silva <pedromsilva1@gmail.com>:
> Hello again Alberto!
>
> > Anyway, to get more info, try to open a second shell
> > and run /usr/lib/eicon/divas/xlog
> > then on the first shell redo the telsampl test, then
> > post the output of xlog off the list to my address
> > (alberto at msoft-italia.com)
>
> This is the xlog output:
> 4:1736:074 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> 4:1736:074 - alloc cr in use =4
> 4:1736:076 - free cr in use =3
> 4:1736:077 - DELETEID ok: deleted Id:6 freeIds=eb
> 4:1736:078 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> 4:1736:078 - alloc cr in use =4
> 4:1736:080 - free cr in use =3
> 4:1736:080 - DELETEID ok: deleted Id:6 freeIds=eb
> 4:1736:081 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> 4:1736:081 - alloc cr in use =4
> 4:1736:083 - [1,0] dsp_assign 0016, 0, 2048
> 4:1736:083 - [1,0] CAI[00] 16 00 00 00 00 08
> 4:1736:084 - [1,0] Download 532 requested
> 4:1736:084 - MORE
> 4:1736:085 - SIG-X(029) 08 01 36 05 A1 04 03 80 90 A3 18 01 83 1E
> 02 80 83 70 0A 80 39 36 33 30 34 35 37 32 33
> Q.931 CR36 SETUP
> Sending complete
> Bearer Capability 80 90 a3
> Channel Id 83
> Progress Indicator 80 83
> Called Party Number 80 '963045723'
> 4:1736:085 - SIG-S 0->1 e:885
> 4:1736:087 - ACTIVATION_REQ
> 4:1744:147 - L1_DOWN
> 4:1744:150 - SIG-EVENT FFFF 08
>
> 4:1744:150 - SIG-EVENT FFFF 08
>
> 4:1744:150 - EVENT: Call failed in State 'Call initiated'
> Link disconnected, Layer-1 error (cable or NT)
> 4:1744:150 - SIG-S 1->0 e:ffff
> 4:1744:151 - [1,0] dsp_release
> 4:1744:155 - free cr in use =3
> 4:1744:156 - DELETEID ok: deleted Id:6 freeIds=eb
>
> I disconnect the rj45 cable from alcatel pbx and connect that to the
> diva card (with alcatel pbx i can make calls normally). The green led
> of the diva card is activated when i connect the cable. So i dont
> understand why the message " Link disconnected, Layer-1 error (cable
> or NT)"...
> This debug is th same if the cable is connected to the NT or not.
> Any ideas...? Thanks!
> PS.
>
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Tue Oct 31, 2006 12:07 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
On Tue, 31 Oct 2006, Pedro Silva wrote:
Quote:
Hello,
One problem is solved and another appears... :(
I cannot receive incoming calls on trixbox. I defined one incoming
route (any DID/any CID) and forwading these calls to a SIP extension.
With capi and sip debug in "asterisk -r" console i dont detect any
incoming activity...
Did you use
set verbose 5
capi debug
?
If not, you should see anything there. But if you don't see activity with
this verbose level too, this call is not signaled through capi. In that case
you should create traces with
divactrl ditrace
(or the trace wizard) to get capi activity too.
So the problem appears to be "Incompatible destination"... but is
problem in asterisk or is before asterisk, on diva card...?
Tanks by any possible help!
Best regards,
PS.
2006/10/29, Pedro Silva <pedromsilva1@gmail.com>:
> Finally this works!!! :)
> Tanks to Alberto and Marco by your help!
> The problems are:
> - the cable was connected to the wong card port... :(
> - the card config needs to be: ETSI; TE; Point-to-Point (I thought
> that was point-to-multipoint).
>
> Best regards,
> PS.
>
> 2006/10/29, Pedro Silva <pedromsilva1@gmail.com>:
> > Hello again Alberto!
> >
> > > Anyway, to get more info, try to open a second shell
> > > and run /usr/lib/eicon/divas/xlog
> > > then on the first shell redo the telsampl test, then
> > > post the output of xlog off the list to my address
> > > (alberto at msoft-italia.com)
> >
> > This is the xlog output:
> > 4:1736:074 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> > 4:1736:074 - alloc cr in use =4
> > 4:1736:076 - free cr in use =3
> > 4:1736:077 - DELETEID ok: deleted Id:6 freeIds=eb
> > 4:1736:078 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> > 4:1736:078 - alloc cr in use =4
> > 4:1736:080 - free cr in use =3
> > 4:1736:080 - DELETEID ok: deleted Id:6 freeIds=eb
> > 4:1736:081 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> > 4:1736:081 - alloc cr in use =4
> > 4:1736:083 - [1,0] dsp_assign 0016, 0, 2048
> > 4:1736:083 - [1,0] CAI[00] 16 00 00 00 00 08
> > 4:1736:084 - [1,0] Download 532 requested
> > 4:1736:084 - MORE
> > 4:1736:085 - SIG-X(029) 08 01 36 05 A1 04 03 80 90 A3 18 01 83
> > 1E
> > 02 80 83 70 0A 80 39 36 33 30 34 35 37 32 33
> > Q.931 CR36 SETUP
> > Sending complete
> > Bearer Capability 80 90 a3
> > Channel Id 83
> > Progress Indicator 80 83
> > Called Party Number 80 '963045723'
> > 4:1736:085 - SIG-S 0->1 e:885
> > 4:1736:087 - ACTIVATION_REQ
> > 4:1744:147 - L1_DOWN
> > 4:1744:150 - SIG-EVENT FFFF 08
> >
> > 4:1744:150 - SIG-EVENT FFFF 08
> >
> > 4:1744:150 - EVENT: Call failed in State 'Call initiated'
> > Link disconnected, Layer-1 error (cable or NT)
> > 4:1744:150 - SIG-S 1->0 e:ffff
> > 4:1744:151 - [1,0] dsp_release
> > 4:1744:155 - free cr in use =3
> > 4:1744:156 - DELETEID ok: deleted Id:6 freeIds=eb
> >
> > I disconnect the rj45 cable from alcatel pbx and connect that to the
> > diva card (with alcatel pbx i can make calls normally). The green
> > led
> > of the diva card is activated when i connect the cable. So i dont
> > understand why the message " Link disconnected, Layer-1 error (cable
> > or NT)"...
> > This debug is th same if the cable is connected to the NT or not.
> > Any ideas...? Thanks!
> > PS.
> >
>
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Tue Oct 31, 2006 12:18 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Hi Pedro,
pls post your capi.conf! I'm not used with CAPI, but should have something like:
[interfaces]
incomingmsn=* ; Here you match MSNs arriving from telco, for debug
let it ' * '
controller=1
softdtmf=1
accountcode=
context=demo ;Set this to ext-did that should be the context
TRIXBOX will handle
By the way, Trybox probably has an extensions_custom.conf
On 10/31/06, Armin Schindler <armin@melware.de> wrote:
Quote:
On Tue, 31 Oct 2006, Pedro Silva wrote:
> Hello,
>
> One problem is solved and another appears... :(
> I cannot receive incoming calls on trixbox. I defined one incoming
> route (any DID/any CID) and forwading these calls to a SIP extension.
> With capi and sip debug in "asterisk -r" console i dont detect any
> incoming activity...
Did you use
set verbose 5
capi debug
?
If not, you should see anything there. But if you don't see activity with
this verbose level too, this call is not signaled through capi. In that case
you should create traces with
divactrl ditrace
(or the trace wizard) to get capi activity too.
Armin
> In xlog console i have the following debug:
> 0:1898:127 - SIG-R(034) 08 01 0D 05 A1 04 03 80 90 A3 18 01 81 6C 0B
> 00 83 39 36 33 30 34 35 37 32 33 70 02 81 30 7D 02 91 81
> Q.931 CR0d SETUP
> Sending complete
> Bearer Capability 80 90 a3
> Channel Id 81
> Calling Party Number 00 83 '963045723'
> Called Party Number 81 '0'
> HLC 91 81
> 0:1898:127 - SIG-S 0->6 e:805
> 0:1898:130 - CREATEID ok: context:1f assigned Id:3 freeIds=ec
> 0:1898:130 - alloc cr in use =4
> 0:1898:133 - SIG-X(008) 08 01 8D 45 08 02 80 95
> Q.931 CR8d DISC
> Cause 80 95 'Call rejected'
> 0:1898:133 - SIG-x(008) 08 01 8D 5A 08 02 80 D8
> Q.931 CR8d REL_COM
> Cause 80 d8 'Incompatible destination'
> 0:1898:133 - SIG-S 6->0 e:8c5
> 0:1898:134 - D-X(012) 00 01 14 16 08 01 8D 5A 08 02 80 D8
> 0:1898:135 - free cr in use =3
> 0:1898:135 - DELETEID ok: deleted Id:4 freeIds=ec
> 0:1898:155 - D-R(004) 00 01 01 16
>
> So the problem appears to be "Incompatible destination"... but is
> problem in asterisk or is before asterisk, on diva card...?
>
> Tanks by any possible help!
> Best regards,
> PS.
>
> 2006/10/29, Pedro Silva <pedromsilva1@gmail.com>:
> > Finally this works!!! :)
> > Tanks to Alberto and Marco by your help!
> > The problems are:
> > - the cable was connected to the wong card port... :(
> > - the card config needs to be: ETSI; TE; Point-to-Point (I thought
> > that was point-to-multipoint).
> >
> > Best regards,
> > PS.
> >
> > 2006/10/29, Pedro Silva <pedromsilva1@gmail.com>:
> > > Hello again Alberto!
> > >
> > > > Anyway, to get more info, try to open a second shell
> > > > and run /usr/lib/eicon/divas/xlog
> > > > then on the first shell redo the telsampl test, then
> > > > post the output of xlog off the list to my address
> > > > (alberto at msoft-italia.com)
> > >
> > > This is the xlog output:
> > > 4:1736:074 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> > > 4:1736:074 - alloc cr in use =4
> > > 4:1736:076 - free cr in use =3
> > > 4:1736:077 - DELETEID ok: deleted Id:6 freeIds=eb
> > > 4:1736:078 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> > > 4:1736:078 - alloc cr in use =4
> > > 4:1736:080 - free cr in use =3
> > > 4:1736:080 - DELETEID ok: deleted Id:6 freeIds=eb
> > > 4:1736:081 - CREATEID ok: context:1f assigned Id:6 freeIds=eb
> > > 4:1736:081 - alloc cr in use =4
> > > 4:1736:083 - [1,0] dsp_assign 0016, 0, 2048
> > > 4:1736:083 - [1,0] CAI[00] 16 00 00 00 00 08
> > > 4:1736:084 - [1,0] Download 532 requested
> > > 4:1736:084 - MORE
> > > 4:1736:085 - SIG-X(029) 08 01 36 05 A1 04 03 80 90 A3 18 01 83
> > > 1E
> > > 02 80 83 70 0A 80 39 36 33 30 34 35 37 32 33
> > > Q.931 CR36 SETUP
> > > Sending complete
> > > Bearer Capability 80 90 a3
> > > Channel Id 83
> > > Progress Indicator 80 83
> > > Called Party Number 80 '963045723'
> > > 4:1736:085 - SIG-S 0->1 e:885
> > > 4:1736:087 - ACTIVATION_REQ
> > > 4:1744:147 - L1_DOWN
> > > 4:1744:150 - SIG-EVENT FFFF 08
> > >
> > > 4:1744:150 - SIG-EVENT FFFF 08
> > >
> > > 4:1744:150 - EVENT: Call failed in State 'Call initiated'
> > > Link disconnected, Layer-1 error (cable or NT)
> > > 4:1744:150 - SIG-S 1->0 e:ffff
> > > 4:1744:151 - [1,0] dsp_release
> > > 4:1744:155 - free cr in use =3
> > > 4:1744:156 - DELETEID ok: deleted Id:6 freeIds=eb
> > >
> > > I disconnect the rj45 cable from alcatel pbx and connect that to the
> > > diva card (with alcatel pbx i can make calls normally). The green
> > > led
> > > of the diva card is activated when i connect the cable. So i dont
> > > understand why the message " Link disconnected, Layer-1 error (cable
> > > or NT)"...
> > > This debug is th same if the cable is connected to the NT or not.
> > > Any ideas...? Thanks!
> > > PS.
> > >
> >
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
> http://lists.digium.com/mailman/listinfo/asterisk-users
>
>
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Wed Nov 01, 2006 8:50 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
Hello,
The problem was wrong contexts defined like Marco said, and is solved.
Now, i have another problem...of course :)
On incoming calls, i only can receive calls if i define a line like
the following, in extensions.conf:
exten => _.,n,Dial(SIP/500,30,tr) (all incoming calls are redirected
to extension 500).
The problem is that i have some DDI's assigned by my telco (xxx302500
to xxx302509) and i need to route each DDI to diferent internal
extension.
If i define someting like "exten => _XXXXXXXX0,n,Dial..." (for DDI
xxx302500) the call is not answered by asterisk. I think that asterisk
cannot identify the destination DDI of the incoming call...is this
normal?
This is the capi debug of one incoming call:
-- ISDN1#02: info element CALLED PARTY NUMBER
> ISDN1#02: INFO_IND DID digits not used in this state.
INFO_IND ID=001 #0x1977 LEN=0015
Controller/PLCI/NCCI = 0x401
InfoNumber = 0xa1
InfoElement = default
-- ISDN1#02: DISCONNECT_IND on incoming without pbx, doing hangup.
> CAPI/ISDN1/0-15: set channel task to 1
== ISDN1#02: CAPI Hangingup for PLCI=0x401 in state 4
== ISDN1#02: Interface cleanup PLCI=0x401
> CAPI devicestate requested for ISDN1/0
Anyone can give me ideas about this problem?
Thanks in advance!
Best regards,
PS.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Posted: Wed Nov 01, 2006 11:30 pm Post subject: [asterisk-users] Diva server 4bri and Portuguese BRI
On Wed, 1 Nov 2006, Pedro Silva wrote:
Quote:
Hello,
The problem was wrong contexts defined like Marco said, and is solved.
Now, i have another problem...of course :)
On incoming calls, i only can receive calls if i define a line like
the following, in extensions.conf:
exten => _.,n,Dial(SIP/500,30,tr) (all incoming calls are redirected
to extension 500).
The problem is that i have some DDI's assigned by my telco (xxx302500
to xxx302509) and i need to route each DDI to diferent internal
extension.
If i define someting like "exten => _XXXXXXXX0,n,Dial..." (for DDI
xxx302500) the call is not answered by asterisk. I think that asterisk
cannot identify the destination DDI of the incoming call...is this
normal?
As you can see in the log below, the called number is just '0':
Quote:
CalledPartyNumber = <81>0
It seems DDI 0 of your line was called. So just do
exten => 0,n,Dial...
-- ISDN1#02: info element CALLED PARTY NUMBER
> ISDN1#02: INFO_IND DID digits not used in this state.
INFO_IND ID=001 #0x1977 LEN=0015
Controller/PLCI/NCCI = 0x401
InfoNumber = 0xa1
InfoElement = default
-- ISDN1#02: DISCONNECT_IND on incoming without pbx, doing hangup.
> CAPI/ISDN1/0-15: set channel task to 1
== ISDN1#02: CAPI Hangingup for PLCI=0x401 in state 4
== ISDN1#02: Interface cleanup PLCI=0x401
> CAPI devicestate requested for ISDN1/0
Anyone can give me ideas about this problem?
Thanks in advance!
Best regards,
PS.
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
You cannot post new topics in this forum You cannot 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