06-08-2009 01:53 PM - edited 03-21-2019 01:11 AM
We are Having E1 line connected to UC 500.
Whenever a user tries to call someone and the called party sends a BUSY tone , the disconnection Time takes 5 to 10 sec, i have modified voice port to disconnect within 0 secs but still the issue is not resolved.
Debug shows the call is Disconnected , But the phone still rings up to 10 secs
Please post your valuable suggestions regarding this issue.
06-08-2009 02:05 PM
To make sure I understand the problem correctly...
User places a call. User gets ringback.
Debugs show that the call is busy. Call disconnects on the PRI side.
User phone still gets ringback for a few more seconds.
Is that correct? Does the user ever get busy tone? Is this an FXS phone?
06-08-2009 02:10 PM
Yes Steven what you said is correct.
The phones we use are the following.
7941 -G , 7945G etc .
No phones are connected to FXS ports.
06-09-2009 06:54 AM
Does the user ever get busy tone? Does the call disappear from the phone before the busy tone?
06-10-2009 12:20 AM
Yes, for example, caller A calls Caller B.
Caller B sends a busy Tone immediately , Caller A will get the Busy Tone from the B after 10 secs.
The disconnection time in voice port is set to 0. Still it takes Time.
Now Our Telco says that I can change the frequency and cadance, i have done it for FXO ports in one of our previous Installation , is it possible to change this In E1.
06-10-2009 07:32 AM
Frequency and cadence shouldn't matter on a PRI. You get a message that says busy. It isn't like an FXO where notifications are with tones.
Let me look into this a bit to see if I can find something.
06-10-2009 10:43 PM
Hi Suraj,
Yes, for example, caller A calls Caller B.
Caller B sends a busy Tone immediately , Caller A will get the Busy Tone from the B after 10 secs.
WOW i havent seen this problem before on a PRI circuit.
Suraj, i dont suppose you have a full debug message of this taking place do you?
Can you post them to look at, it would be interesting to see this happening live to see what is taking place.
Cheers,
David.
06-11-2009 05:26 AM
I am with David. This is very weird. More information is needed here to determine exactly what's happening.
Thanks,
Marcos
06-11-2009 08:53 AM
Hi all
Thanks for your valuable comments
Check the debug output
Jun 11 19:16:02: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 098
Jun 11 19:16:02: ISDN Se0/3/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Called num 0507840168
Jun 11 19:16:02: ISDN Se0/3/0:15 Q921: User TX -> INFO sapi=0 tei=0, ns=116 nr=109
Jun 11 19:16:02: ISDN Se0/3/0:15 Q931: SETUP pd = 8 callref = 0x046E
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9839F
Exclusive, Channel 31
Progress Ind i = 0x8183 - Origination address is non-ISDN
Calling Party Number i = 0x0180, '098'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '0507840168'
Plan:ISDN, Type:Unknown
Jun 11 19:16:02: ISDN Se0/3/0:15 Q921: User RX <- RR sapi=0 tei=0 nr=117
Jun 11 19:16:02: ISDN Se0/3/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=109 nr=117
Jun 11 19:16:02: ISDN Se0/3/0:15 Q931: CALL_PROC pd = 8 callref = 0x846E
Channel ID i = 0xA9839F
Exclusive, Channel 31
Jun 11 19:16:02: ISDN Se0/3/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=110
Jun 11 19:16:05: ISDN Se0/3/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=110 nr=117
Jun 11 19:16:05: ISDN Se0/3/0:15 Q931: ALERTING pd = 8 callref = 0x846E
Jun 11 19:16:05: ISDN Se0/3/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=111
Jun 11 19:16:15: ISDN Se0/3/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=111 nr=117
Jun 11 19:16:15: ISDN Se0/3/0:15 Q931: DISCONNECT pd = 8 callref = 0x846E
Cause i = 0x8091 - User busy
Progress Ind i = 0x8288 - In-band info or appropriate now available
Jun 11 19:16:15: ISDN Se0/3/0:15 Q921: User TX -> RR sapi=0 tei=0 nr=112
Jun 11 19:16:15: ISDN Se0/3/0:15 Q931: call_disc: PI received in disconnect; Postpone sending RELEASE for callid 0x83EF
Jun 11 19:16:25: ISDN Se0/3/0:15 Q921: User TX -> RRp sapi=0 tei=0 nr=112
Jun 11 19:16:25: ISDN Se0/3/0:15 Q921: User RX <- RRp sapi=0 tei=0 nr=117
Jun 11 19:16:25: ISDN Se0/3/0:15 Q921: User TX -> RRf sapi=0 tei=0 nr=112
Jun 11 19:16:25: ISDN Se0/3/0:15 Q921: User RX <- RRf sapi=0 tei=0 nr=117
Jun 11 19:16:35: ISDN Se0/3/0:15 Q921: User TX -> RRp sapi=0 tei=0 nr=112
Jun 11 19:16:35: ISDN Se0/3/0:15 Q921: User RX <- RRf sapi=0 tei=0 nr=117
Jun 11 19:16:45: ISDN Se0/3/0:15 Q921: User RX <- INFO sapi=0 tei=0, ns=112 nr=117
Jun 11 19:16:45: ISDN Se0/3/0:15 Q931: RELEASE pd = 8 callref = 0x846E
Cause i = 0x8091 - User busy
06-11-2009 09:22 AM
I see what's happening now. This is for an outbound call. For some reason I thought you were talking about inbound. Anyway, you are getting a DISCONNECT with indication to play inband audio (Progress Indicator = 8"), so the ISDN T306 time is kicking in. You can tweak this under the D channel, or you can eliminate PI completely with some other commands. I'd rather tweak the timer. The D channel is your Serial 0/3/0:15 interface, and this timer should be listed under the "isdn timer" command.
From the documentation:
The T306 timer is designed for routers that are configured as an ISDN network-side switch. When a router sends out a disconnect message with a progress indicator of 8, it disconnects the call after waiting for the specified number of milliseconds (ms) while the in-band announcement or error tone is playing. Be sure to set the timer long enough for the announcement to be heard or the tone to be recognized. This command is used only for disconnect messages with a progress indicator of 8; otherwise, the T305 timer is used. The default and no forms of this command have the same result: the timer waits for the default number of ms before disconnecting the call.
Let us know,
Marcos
06-11-2009 10:55 AM
I have tried to reduce the time in int serial 0/3/0:15.
ISDN T306 to 400 milliseconds
Disconnection timer remains the same takes 10 secs
06-11-2009 11:15 AM
Can you try this global command:
voice call disc-pi-off
Let me know,
Marcos
06-11-2009 11:26 AM
Thanks Marcos
The issue is solved.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide