Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Waiting For A Line

Status
Not open for further replies.
wheelma2

wheelma2

IS-IT--Management
Feb 26, 2007
123
US
I have an IP 500 V2 with (4) analog trunks. When someone is already on a call, a second call cannot be placed outbound. The users see "Waiting for a line" on display and hear an audible beep.

Below is a trace (with X's replacing digits to mask my numbers). It shows my call with the locals on Port 9 (line 5). Then someone else in the office lifted another handset and attempted to dial out. It looks like ARS got it to Line 6, bu tthen "Originator State = Clearing". This is the point at which the caller hears beep tones and sees "Waiting for a line" on display.

What is causing the originator end to clear? Why can't the IPO seize and use line 6 in this scenario? Any assistance is appreciated!


----------------------------------------------------------------------------
Slot/Module: Slot: 2
Number of Trunks: 4
Number of Administered Trunks: 4
Number of Trunks in Use: 1

Port Line Line Type Channel Call Current State Time in State Caller ID or Other Party Direction
ID Admin State Ref Dialed Digits on Call of Call
------------------------------------------------------------------------------------------------------------------------------------------------
9 Line: 5 Slot: 2 Port: 9 Loop Start CLI In Service 310 Connected 00:04:56 XXXXXXXXXXX Extn 2405, Extn2405 Outgoing

10 Line: 6 Slot: 2 Port: 10 Loop Start CLI In Service Idle 00:03:09

11 Line: 7 Slot: 2 Port: 11 Loop Start CLI In Service Idle 00:04:53

12 Line: 8 Slot: 2 Port: 12 Loop Start CLI In Service Idle 14:34:46


Trace Output - All Ports:
6/21/13 8:26:42 AM-927ms Line = 6, Seized, Call Ref = 316
6/21/13 8:26:42 AM-929ms Call Ref = 316, Originator State = Dialling, Type = User, Destination State = Seized, Type = Target List
6/21/13 8:26:42 AM-985ms Call Ref = 316, Originator State = Dialling, Type = User, Destination State = Seized, Type = Trunk
6/21/13 8:26:43 AM-485ms Line = 6, Wait for Dialtone Ended, Call Ref = 316
6/21/13 8:26:43 AM-486ms Line = 6, Dialing, Call Ref = 316, Digits =
6/21/13 8:26:44 AM-893ms Extension = 2404, Digit dialed, Digit = 9
6/21/13 8:26:44 AM-894ms Call Ref = 316, Short Code Matched = System, 9N
6/21/13 8:26:45 AM-743ms Extension = 2404, Digit dialed, Digit = 1
6/21/13 8:26:45 AM-744ms Call Ref = 316, Short Code Matched = System, 9N
6/21/13 8:26:46 AM-168ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:46 AM-168ms Call Ref = 316, Short Code Matched = System, 9N
6/21/13 8:26:47 AM-555ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:47 AM-556ms Call Ref = 316, Short Code Matched = System, 9N
6/21/13 8:26:48 AM-030ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:48 AM-031ms Call Ref = 316, Short Code Matched = System, 9N
6/21/13 8:26:50 AM-033ms Call Ref = 316, Alerting, Line = 6
6/21/13 8:26:50 AM-035ms Call Ref = 316, Originator State = Connected, Type = User, Destination State = Connected, Type = Trunk
6/21/13 8:26:50 AM-035ms Call Ref = 316, Answered, Line = 6
6/21/13 8:26:52 AM-283ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:52 AM-695ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:52 AM-996ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:53 AM-383ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:53 AM-560ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:53 AM-920ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:54 AM-258ms Extension = 2404, Digit dialed, Digit = X
6/21/13 8:26:59 AM-961ms Extension = 2404, Switchhook, Status = On
6/21/13 8:26:59 AM-962ms Call Ref = 316, Originator State = Clearing, Type = User, Destination State = Connected, Type = Trunk
6/21/13 8:26:59 AM-962ms Call Ref = 316, Disconnect from Originator End
 
Sort by date Sort by votes
Probably because the line in that port doesn't work or isn't connected properly ...at a guess :)



"No problem monkey socks
 
Upvote 0 Downvote
That's what I figured too. But all 4 lines tested clean by our local cabling vendor. In fact, during this exact scenario, he was able to clampointo the line and make a call from beyond the IPO. So it's something in the IPO that is clearing on the originating end...
 
Upvote 0 Downvote
...and if you'll notice, we're using "Line 5" to "Line 8" because I've already had them move the 4 lines from the COMBO card in slot 1 to the COMBO card in slot 2. So the lines work, and they've been re-connected to different line ports on the IPO.
 
Upvote 0 Downvote
do all the analogue lines have the same outgoing id?

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Upvote 0 Downvote
Nope, it sees the line as Idle, it just can't seize it. I would pull the plug out the system and test on the end of that, it's either pinned wrong or doesn't work, testing with a different lead doesn't prove much. Also moving the working line into that port and the non working line into port 9 and retesting will show what the fault follows :)



"No problem monkey socks
 
Upvote 0 Downvote
smokinjoe: No, they all have unique IDs. 801-808, we're using 801-804 (which had been assigned to lines 1-4 on the first COMBO). During troubleshooting, I had the locals move the lines to the second card (lines 5-8) and moved the IDs around with them.
 
Upvote 0 Downvote
Not ID's, "outgoing line group" ..it's a different field/setting :)



"No problem monkey socks
 
Upvote 0 Downvote
not line app id outgoing group id

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Upvote 0 Downvote
I had the locals move the lines to the second card (lines 5-8) and moved the IDs around with them.
Click to expand...

That's not how you do it, you may have messed up your config, post it somewhere and we can check it :)



"No problem monkey socks
 
Upvote 0 Downvote
try to renumber the lines starting at 805-808, save and reboot and see if this fixes it,amriddle is right this is most likely causing your problems

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Upvote 0 Downvote
Why didn't you move them to the other card then disable the first 4 line ports?
 
Upvote 0 Downvote
As the locals were physically moving the cards, I changed the config accordingly (at least to the best of my limited knowledge of the IPO platform)....

Before:
Line: 1 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 801
Line: 2 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 802
Line: 3 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 803
Line: 4 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 804
Line: 5 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 805
Line: 6 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 806
Line: 7 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 807
Line: 8 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 808

After:
Line: 1 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 805
Line: 2 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 806
Line: 3 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 807
Line: 4 Incoming ID: 1 Outgoing ID: 1 Line Appearance ID: 808
Line: 5 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 801
Line: 6 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 802
Line: 7 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 803
Line: 8 Incoming ID: 0 Outgoing ID: 0 Line Appearance ID: 804

 
Upvote 0 Downvote
As for it possibly being a pinout issue... I can tie up all 4 lines simultaneously with inbound calls. I doubt I'd have a copper issue going out that doesn't also exist coming in....
 
Upvote 0 Downvote
overthebars: That's EXACTLY what I've done. I moved the lines from the first COMBO to the second COMBO. They still have the problem (simultaneous outbound only).
 
Upvote 0 Downvote
smokinjoe: I changed Incoming and Outgoing IDs also. See my reply above witt "Before" and "After" details of the physical and logical line relocations.
 
Upvote 0 Downvote
Incoming working and not outbound means a config issue(you didn't say incoming was working before) rather than us ask every possible setting and feature that can effect/cause this it's easier to post your config :)



"No problem monkey socks
 
Upvote 0 Downvote
Unfortunatley I cannot access file sharing sites like dropbox via our corporate proxy. I'll try to find a way to get it to you and post a link as soon as I can find a solution. Thanks for all the help everyone!
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

Arun Neelambaran
  • Locked
  • Question
Call waiting notification
Replies
3
Views
171
William C290
William C290
Mani66
  • Locked
  • Question
No voice transmission after waiting on hold
Replies
5
Views
492
Mani66
Mani66
rsv23
  • Locked
  • Question
SIP Line configuration for STC
Replies
6
Views
216
derfloh
derfloh
JiriPol
  • Locked
  • Question
Avaya IPO500 - analog line distance
Replies
6
Views
217
budbyrd
budbyrd
M
  • Locked
  • Question
R11 Moved from PRI to SIP Trunks, How to Change the Line Group for '9N' Default User Short Code? 1
Replies
2
Views
548
Mzw2emvhmCzxyZTnn
M

Part and Inventory Search

Sponsor

Back
Top