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!

  • 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!

Analogue and ISDN lines are busy

Status
Not open for further replies.

luthman

IS-IT--Management
Nov 19, 2007
20
FR
I have a problem with continously busy analogue and ISDN lines coming in to the R1 no in the PBX.

I have checked the A-numbers and all that - and it looks very much ok.

The lines should not be busy - as I know that the phones is "on the hook". But no one can either call the extetion och call from the affected phone.

Could there be a problem with a board in the Lim that never hangs up or something? Is there a way of terminating any connection of this kind? Please advise me.....

Regards
Aron L
 
I recently talked to a technician that said: "restarting the program unit that is handling the generic extensions will solve the problem" - how can this be done?
And secondly - how can this be done without having to interrupt any "real" ongoing calls?

/ARON
 
restarting unit RELP will solve this indeed (altough the problem will come back) : RFPUI:UNIT=RELP,LIM=ALL;

there is no other (easy) way to solve this, so yes by restarting the unit, remote extension calls will be cut....

may I ask you what version you have running? (CADAP;)

Cheers,
Daddy

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
VERSION=CXP1010105/2/BC12SP11/R8A

An upgrade to BC13 is planned (Q1-Q2 2008) are there any advantages in the upgrade - perhaps solving issues like this??


/ARON
 
SP11 should be pretty stable on remote extensions. all bugs found after this SP (as this is the latest for BC12) should be solved in BC13 (TSW).

can you elaborate on the setup you use?

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
Yes

thank so much for quick replies!

/Aron
 
stupid question maybe:

you say you have analog lines, dou you mean you get remote extension calls through analog trunks connected to the MD110? because this is not supported!

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
there are analog lines connecting to the R1 number in the PBX through a hotline function.

/ARON
 
???
you mean analog extensions with a SPEXI towards R1 on the SAME MD110?

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
As our branches as spread all over the country with a centralized switchboard, all these different offices are equipped with a number of ordinary analog lines (PSTN). These phones are linked for outgoing traffik trough the R1 in the PBX (i am unsure if this is called SPEXI?). When lifting the handset - you are linked in to the PBX and given a dialling tone.
For incoming traffic the PBX is set up just as any other generic extension like mobile etc.

Most of the time this set up works absolutely fine - but every one in a while some extensions are to be found in the state mentioned earlier...

/ARON
 
I see, what I mean is that the R1 calls must enter through an ISDN line that is connected to the main site (where the R1 number resides)

so :

Branch office - analog trunk - PSTN Network - ISDN trunk - Main office
is allowed

Branch office - analog trunk - PSTN Network - analog trunk - Main office
is not allowed

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
You are absolutely right.

It is set up with the secont option you mentioned.

Thanks for your help!

/ARON
 
ok then, that setup is not allowed so don't look further

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
sorry. Getting tired now.... It is the first option. =)
(think i read them the "wrong" order). This set up has been working for almost two years now..

/ARON
 
He can look a little bit further -- initiate an R2 number for the call cases when calling party info is not going to be received by the muther ship.......unless the manual authentication process is deemed too complex or otherwise impractical for those users.

Technology can only compensate for so much.....


Good luck,

Dave Strang
 
one requirement for remote extensions is that the call must go via an ISDN route connected to the MD110, clip or no clip has nothing to do with it...

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
You're right for the R1 number (sorta)......I believe the R2 number will also work with DID trunks (did on my lab switch anyway), but neither will work on a regular analog TL1.

Calling party info does have a bit to do with it in that the calling number has to have a NUTRI entry for the R1 conversion.....maybe he needs to add NUTRI entries for the analog trunk ID's of the branch offices that don't seem to work when calling the R1 number.

Seems to me that if he ony has analog trunks coming in to his MD (scenario 2 as he states above)then NONE of the calls to the R1 number would be successful.

I'm starting to think that troubleshooting this has gone clear out in left field due to insufficient information regarding the specific call case in which the calling extension receives a busy signal.

If the extension is spexi'd to the R1 number, what's the possibility that "every once in a while" all outbound trunks at a particular remote site are busy when that extension went off hook?

Dave Strang


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top