OXO - ISND PRI communication problem while forwarding.

Post Reply
tincho.rn

OXO - ISND PRI communication problem while forwarding.

Post by tincho.rn »

Scenario:
OXO with one access ISDN PRI. Extension 1001 is forward to an external number, using ARS. When extension 1002 calls extension 1001 with have the following trace with an unsuccessful call.

ISDN3_00033 29/08 11:00:25 TX d_channel: 75 (S:00 T:000) payload: (41) 08 02 00 48 05 A1 04 03 80 90 A3 18 01 A3 6C 06 01 80 39 37 33 35 70 0A 81 31 35 36 37 33 30 36 34 39 7D 02 91 81 7E 01 04
0x05 SETUP Ref: O,72
ie 0xA1 Sending complete
ie 0x04 Bearer capability: 80 90 A3
Coding: CCITT standardized
Information transfer capability: Speech
Transfer mode: Circuit mode
Transfer rate: 64 Kbit/s
User info layer 1: G.711 A-law
ie 0x18 Channel identification: A3
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: any channel
ie 0x6C Calling party number: 01 80 39 37 33 35
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Presentation: presentation allowed
Screening: user-provided, not screened
Number: 9735
ie 0x70 Called party number: 81 31 35 36 37 33 30 36 34 39
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Number: 156730649
ie 0x7D High layer compatibility: 91 81
ie 0x7E User-user: 04

ISDN3_00034 29/08 11:00:26 RX d_channel: 75 (S:00 T:000) payload: (10) 08 02 80 48 02 18 03 A1 83 83
0x02 CALL_PROCEEDING Ref: D,72
ie 0x18 Channel identification: A1 83 83
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: B1 channel
Coding: CCITT standardized
Channel type: B-channel units
Channel number: 0x03

ISDN3_00035 29/08 11:00:26 TX d_channel: 75 (S:00 T:000) payload: (12) 08 02 00 48 7D 08 02 81 E4 14 01 01
0x7D STATUS Ref: O,72
ie 0x08 Cause: 81 E4
Coding: CCITT standardized
Location: Private network serving the local user
Class: 3
Value: Unknown information element cont.
ie 0x14 Call state: 01

ISDN3_00038 29/08 11:00:30 TX d_channel: 75 (S:00 T:000) payload: (41) 08 02 00 48 05 A1 04 03 80 90 A3 18 01 A3 6C 06 01 80 39 37 33 35 70 0A 81 31 35 36 37 33 30 36 34 39 7D 02 91 81 7E 01 04
0x05 SETUP Ref: O,72
ie 0xA1 Sending complete
ie 0x04 Bearer capability: 80 90 A3
Coding: CCITT standardized
Information transfer capability: Speech
Transfer mode: Circuit mode
Transfer rate: 64 Kbit/s
User info layer 1: G.711 A-law
ie 0x18 Channel identification: A3
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: any channel
ie 0x6C Calling party number: 01 80 39 37 33 35
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Presentation: presentation allowed
Screening: user-provided, not screened
Number: 9735
ie 0x70 Called party number: 81 31 35 36 37 33 30 36 34 39
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Number: 156730649
ie 0x7D High layer compatibility: 91 81
ie 0x7E User-user: 04

ISDN3_00042 29/08 11:00:34 TX d_channel: 75 (S:00 T:000) payload: (9) 08 02 00 48 5A 08 02 81 E6
0x5A RELEASE_COMP Ref: O,72
ie 0x08 Cause: 81 E6
Coding: CCITT standardized
Location: Private network serving the local user
Class: 3
Value: Recovery on time expiry
SAN_00043 at line 43269 "cesc_displ"
on 29.08 at 11:00:34 (34381159)
info : 0000 0031 FFFF FFF9 FFFF FFFF 0000 0000


If extension 1001 call to the external number, the communication is successful. Here a trace of this type of communication:

ISDN3_00137 29/08 10:42:01 TX d_channel: 75 (S:00 T:000) payload: (36) 08 02 00 38 05 04 03 90 90 A3 18 01 A3 1E 02 85 83 6C 05 21 83 38 30 30 70 0A 81 31 35 34 31 36 34 36 33 38
0x05 SETUP Ref: O,56
ie 0x04 Bearer capability: 90 90 A3
Coding: CCITT standardized
Information transfer capability: 3.1 kHz audio
Transfer mode: Circuit mode
Transfer rate: 64 Kbit/s
User info layer 1: G.711 A-law
ie 0x18 Channel identification: A3
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: any channel
ie 0x1E Progress indicator: 85 83
Coding: CCITT standardized
Location: Private network serving the remote user
Progress: Origination address is non-ISDN
ie 0x6C Calling party number: 21 83 38 30 30
Number type: National number
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Presentation: presentation allowed
Screening: network provided
Number: 800
ie 0x70 Called party number: 81 31 35 34 31 36 34 36 33 38
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Number: 154164638

ISDN3_00138 29/08 10:42:01 RX d_channel: 75 (S:00 T:000) payload: (10) 08 02 80 38 0D 18 03 A9 83 81
0x0D SETUP_ACK Ref: D,56
ie 0x18 Channel identification: A9 83 81
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Exclusive
D-channel identified: Yes
Information channel selection: B1 channel
Coding: CCITT standardized
Channel type: B-channel units
Channel number: 0x01

ISDN3_00143 29/08 10:42:05 RX d_channel: 75 (S:00 T:000) payload: (10) 08 02 80 38 02 18 03 A1 83 81
0x02 CALL_PROCEEDING Ref: D,56
ie 0x18 Channel identification: A1 83 81
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: B1 channel
Coding: CCITT standardized
Channel type: B-channel units
Channel number: 0x01
SAN_00144 at line 8128 "depub_aels"
on 29.08 at 10:42:05 (33273467)
info : 0000 7305 0000 000D FFFF FFF9 FFFF FFFF


ISDN3_00151 29/08 10:42:12 RX d_channel: 75 (S:00 T:000) payload: (10) 08 02 80 38 01 18 03 A1 83 81
0x01 ALERTING Ref: D,56
ie 0x18 Channel identification: A1 83 81
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: B1 channel
Coding: CCITT standardized
Channel type: B-channel units
Channel number: 0x01
SAN_00152 at line 8128 "depub_aels"
on 29.08 at 10:42:12 (33280277)
info : 0000 7305 0000 000D FFFF FFF9 FFFF FFFF

ISDN3_00157 29/08 10:42:18 RX d_channel: 75 (S:00 T:000) payload: (10) 08 02 80 38 07 18 03 A1 83 81
0x07 CONNECT Ref: D,56
ie 0x18 Channel identification: A1 83 81
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: B1 channel
Coding: CCITT standardized
Channel type: B-channel units
Channel number: 0x01
SAN_00198 at line 2828 "cbarr.c"
on 29.08 at 10:43:04 (33331767)
info : 0000 0000 FFFF FFF9 FFFF FFFF 0000 012A
SAN_00199 at line 2829 "cbarr.c"
on 29.08 at 10:43:04 (33331770)
info : 0000 0000 FFFF FFF9 FFFF FFFF 0000 0130
SAN_00200 at line 2830 "cbarr.c"
on 29.08 at 10:43:04 (33331774)
info : 0000 0000 FFFF FFF9 FFFF FFFF 0000 00AA

ISDN3_00202 29/08 10:43:08 RX d_channel: 75 (S:00 T:000) payload: (9) 08 02 80 38 45 08 02 80 90
0x45 DISCONNECT Ref: D,56
ie 0x08 Cause: 80 90
Coding: CCITT standardized
Location: User
Class: Normal event
Value: Normal release

ISDN3_00203 29/08 10:43:08 TX d_channel: 75 (S:00 T:000) payload: (9) 08 02 00 38 4D 08 02 81 9F
0x4D RELEASE Ref: O,56
ie 0x08 Cause: 81 9F
Coding: CCITT standardized
Location: Private network serving the local user
Class: Normal event
Value: Normal, not specified

ISDN3_00204 29/08 10:43:08 RX d_channel: 75 (S:00 T:000) payload: (5) 08 02 80 38 5A
0x5A RELEASE_COMP Ref: D,56


You will find some differences, SETUP are different (one is in overlapping and the other in block mode). Then, can some explain this behavior. Normal call with SETUP with sending complete, works OK.
Any ideas?. Thanks in advance. Regards.
User avatar
tot3nkopf
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 4058
Joined: 02 Feb 2006 10:41
Location: Germany & Romania
Contact:

Re: OXO - ISND PRI communication problem while forwarding.

Post by tot3nkopf »

If you forward using trunk group seazure instead of ARS does it work?

In feature design external diversion mode parameter is joining?
tincho.rn

Re: OXO - ISND PRI communication problem while forwarding.

Post by tincho.rn »

Hi tot3nkopf, it seems that in OXO if you use trunk group seizure or ARS, during forwarding the system makes a SETUP with Sending Complete. I would like to test forwarding without sending complete, but I don't know how. However my customer wants to use ARS always.
I will check External Diversion mode.
Thanks. Regards.
tincho.rn

Re: OXO - ISND PRI communication problem while forwarding.

Post by tincho.rn »

Hi. External Diversion mode is in joining. any other idea?. regards.
dmode

Re: OXO - ISND PRI communication problem while forwarding.

Post by dmode »

Tick the join incoming & outgoing option on your voice mail ports.
Post Reply

Return to “MAIN”