RBT problem in 8001G SIP phone

Post Reply
kapil_4596
Member
Posts: 11
Joined: 30 Dec 2008 00:00

RBT problem in 8001G SIP phone

Post by kapil_4596 »

We had installed 8001G with OXO connect. when 8001G user dials internal or external outgoing call, if the called party is busy, then in 8001 SIP phone still hearing RBT. There is no call waiting tone, busy tone which tones provided by service provider , but still there is RBT as like phone is ringing ( but actually phone is busy ).
Please suggest what can I do for this.
User avatar
alex
Senior Member
Posts: 1457
Joined: 06 Jul 2004 07:27
Contact:

Re: RBT problem in 8001G SIP phone

Post by alex »

Check SIP traces first.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
kapil_4596
Member
Posts: 11
Joined: 30 Dec 2008 00:00

Re: RBT problem in 8001G SIP phone

Post by kapil_4596 »

ISDN Traces


0x05 SETUP Ref: O,14
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 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 80 36 31 32 36 36 30 34 34 35 38
Number type: National number
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Presentation: presentation allowed
Screening: user-provided, not screened
Number: 6126604458
ie 0x70 Called party number: 81 39 32 35 36 31 32 32 36 30 33
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Number: 9256122603
ie 0x7D High layer compatibility: 91 81
ISDN3_00228 05/04 14:01:01 RX d_channel: 49 (S:00 T:000) payload: (14) 08 02 80 0E 02 18 03 A9 83 81 1E 02 82 88
0x02 CALL_PROCEEDING Ref: D,14
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
ie 0x1E Progress indicator: 82 88
Coding: CCITT standardized
Location: Public network serving the local user
Progress: In-band information or appropriate pattern now available
SAN_00232 at line 4286 "dnuma.c"
on 05.04 at 14:01:01 (703673323)
info : 0000 000B 0000 0000 0000 0000 0000 0000
ISDN3_00235 05/04 14:01:01 TX d_channel: 49 (S:00 T:000) payload: (49) 08 02 00 0F 05 A1 04 03 80 90 A3 18 01 A3 1E 02 85 83 6C 0C 21 80 36 31 32 36 36 30 34 34 30 34 70 0B 81 39 30 30 36 33 34 35 36 33 35 7D 02 91 81
0x05 SETUP Ref: O,15
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 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 80 36 31 32 36 36 30 34 34 30 34
Number type: National number
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Presentation: presentation allowed
Screening: user-provided, not screened
Number: 6126604404
ie 0x70 Called party number: 81 39 30 30 36 33 34 35 36 33 35
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Number: 9006345635
ie 0x7D High layer compatibility: 91 81
ISDN3_00236 05/04 14:01:01 RX d_channel: 49 (S:00 T:000) payload: (14) 08 02 80 0F 02 18 03 A9 83 84 1E 02 82 88
0x02 CALL_PROCEEDING Ref: D,15
ie 0x18 Channel identification: A9 83 84
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: 0x04
ie 0x1E Progress indicator: 82 88
Coding: CCITT standardized
Location: Public network serving the local user
Progress: In-band information or appropriate pattern now available
ISDN3_00241 05/04 14:01:03 RX d_channel: 49 (S:00 T:000) payload: (9) 08 02 80 0F 01 1E 02 80 88
0x01 ALERTING Ref: D,15
ie 0x1E Progress indicator: 80 88
Coding: CCITT standardized
Location: User
Progress: In-band information or appropriate pattern now available
ISDN3_00243 05/04 14:01:03 RX d_channel: 49 (S:00 T:000) payload: (9) 08 02 80 0E 01 1E 02 80 88
kapil_4596
Member
Posts: 11
Joined: 30 Dec 2008 00:00

Re: RBT problem in 8001G SIP phone

Post by kapil_4596 »

Please suggest the solution as in this trace 8001 user EDN 458 dialed an external caller 9256122603
User avatar
cavagnaro
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 7014
Joined: 14 Sep 2005 19:45
Location: Brasil, Porto Alegre
Contact:

Re: RBT problem in 8001G SIP phone

Post by cavagnaro »

alex told you to check sip traces first and you post ISDN ones? why?
Ignorance is not the problem, the problem is the one who doesn't want to learn

OTUC/ICS ACFE/ACSE R3.0/4.0/5.0/6.0
Certified Genesys CIV 8.5
Certified Genesys Troubleshooting 8.5
Certified Genesys BEP 8.x
Genesys Developer
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3806
Joined: 23 Sep 2004 06:47

Re: RBT problem in 8001G SIP phone

Post by vad »

Ok. In ISDN trace - you have ALERTING. Calling user hear RBT.
Ask provider - send DISCONNECT USER BUSY - in such case.
kapil_4596
Member
Posts: 11
Joined: 30 Dec 2008 00:00

Re: RBT problem in 8001G SIP phone

Post by kapil_4596 »

Thanks VAD,

I asked service provider to send DISCONNECT USER BUSY , but they are not able to do the same.

Is there any other option in our oxo to solve the problem
vad
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 3806
Joined: 23 Sep 2004 06:47

Re: RBT problem in 8001G SIP phone

Post by vad »

May be exist option - hear in-band information (with ALLERTING we have Progress Id.).
kapil_4596
Member
Posts: 11
Joined: 30 Dec 2008 00:00

Re: RBT problem in 8001G SIP phone

Post by kapil_4596 »

Thanks Vad


can we do anything in OMC for this
Post Reply

Return to “H323 / IP / Pimphony”