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!

Doorphone won't ring set

Status
Not open for further replies.

nortelbrent

Programmer
Sep 21, 2011
23
CA
Hello,

I have a Logenex Teledoorbell S-series with a C404CR Controller connected to an analog line port on an IPO 500 v2 6.1 combo card.

I would like to have the doorphone ring line 704 on the 1416 sets.

The sets will ring on an analog telephone line, but they won't ring with the doorphone.

Is the voltage too low? Are there any settings that are missing?

Any help would be appreciated.

Brent
 
Unplug the controller from the IP Office, and plug a single line phone into the controller instead. Will the controller ring a single line telephone?

Did you accidentally disable turn the Ringer Function off with *#77 (2 beeps=on, 3 beepp=off)

If the controller is actually outputting ringing voltage, connect it back to the IPO and watch through system status while it is ringing. Perhaps also bridge a butt set to it so you can hear when it is ringing, and if SSA is showing it.

Don't even bother looking at the IPO programming setup until you know the controller is working properly.
 
Conroller rings the single line set.

From Monitor:

600732176mS RES: Fri 11/11/2011 14:12:17 FreeMem=71967628(2) CMMsg=4 (5) Buff=200 959 999 7463 5 Links=3838
600732176mS RES2: IP 500 V2 6.1(5) Tasks=39 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=41 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=2 SSA=0 ASC=1
 
That monitor output conatins no relevant information, that is just the opening lines when first connecting to the system. You need to catch the call as it comes in and then re-post the trace. However if the system does not detect the call it can't show anything, are you using the correct line cord, just beacause the cord works in a handset does not mean it's pinned correctly for the trunk ports (needs to be centre two pins) :)

NTE-wave-logo-for-a4-header.jpg
 
Go to the user that is created for the extension.
Add a user shortcode like this:

?D
dial direct
Extension number you want to ring it on.

Do not send it to a line appearance, there is no need to do that.


BAZINGA!

I'm not insane, my mother had me tested!
 
Then it should use a shortcode on the line.


BAZINGA!

I'm not insane, my mother had me tested!
 
It will not use line shortcodes, only IP trunks and Qsig and S-bus lines use shortcodes, it will follow incoming call route settings for the Incoming line group it is in :)

NTE-wave-logo-for-a4-header.jpg
 
I put the ?D dial direct on ext 204 (1416 set) and when the doorphone is activated the green light will come on but the set will not ring.
 
The ?D shortcode will make 204 ring the number you entered when going off hook, tlpeter was mistaken, you need to remove that code or extn 204 will not work correctly. You need to make sure the system can even see the line first, try routing a call down that line and is SSA shows "no loop current detected" you know it can't :)

NTE-wave-logo-for-a4-header.jpg
 
Indeed, i thought the doorbell was connected to an analog port for phones.


BAZINGA!

I'm not insane, my mother had me tested!
 
From monitor on an inbound analog line calling in:

603084503mS CMLineRx: v=4
CMReleaseComp
Line: type=AnalogueLine 4 Call: lid=4 id=5 in=1
BChan: slot=1 chan=4
IE CMIERespondingPartyName (228)(Type=CMNameDefault) name=B DAYNARD
IE CMIERespondingPartyNumber (230)(P:0 S:3 T:0 N:0 R:4) number=19056650154
IE CMIEDeviceDetail (231) LOCALE=enu HW=15 VER=6 class=CMDeviceAlogTrunk type=0 number=4 channel=0 rx_gain=32 tx_gain=32 ep_callid=5 ipaddr=192.168.42.1 apps=0
603084503mS CMCallEvt: 4.5.1 97 Alog Trunk:4: StateChange: END=A CMCSRingBack->CMCSCompleted
603084504mS CMTARGET: 4.5.1 97 Alog Trunk:4: CancelTimer CMTCNoAnswerTimeout
603084505mS CMLOGGING: CALL:2011/11/1114:51,00:00:00,014,19056650154,I,200,,BDAYNARD,,,0,,""n/a,0
603084505mS CD: CALL: 4.5.1 BState=Ringing Cut=1 Music=2.0 Aend="Line 4" (1.4) Bend="Main(200)" [Bedroom 2(204),Extn208(208)] (0.0) CalledNum=200 (Main) CallingNum=19056650154 (B DAYNARD) Internal=0 Time=14538 AState=Ringing
603084505mS CD: CALL: 4.5.1 Deleted
603084506mS CMTARGET: 4.5.1 -1 Alog Trunk:4: Removed HG from Callinfo
603084506mS CMCallEvt: 0.1315.0 97 ACDTep(Main): StateChange: END=??? CMCSRinging->CMCSDelete
603084507mS CMCallEvt: 0.1315.0 -1 BaseEP: DELETE CMEndpoint f568952c TOTAL NOW=4 CALL_LIST=0
603084507mS CMTARGET: 4.5.1 -1 Alog Trunk:4: ~CMTargetHandler f568780c ep f568f2a4
603084508mS CMCallEvt: 4.5.1 -1 Alog Trunk:4: StateChange: END=X CMCSCompleted->CMCSDelete
603084508mS CMCallEvt: 0.1314.0 -1 BaseEP: DELETE CMEndpoint f56ab874 TOTAL NOW=3 CALL_LIST=0
603084509mS CMExtnEvt: Bedroom 2: CALL LOST (CMCauseNormal)
603084509mS CMExtnEvt: Bedroom 2: Extn(204) Calling Party Number(19056650154) Type(CMNTypeUnknown)
603084509mS CMCallEvt: 0.1316.0 -1 Bedroom 2.0: StateChange: END=X CMCSRinging->CMCSCompleted
603084509mS CMExtnEvt: v=4 State, new=PortRecoverDelay old=Ringing,0,0,Bedroom 2
603084510mS CMExtnTx: v=204, p1=0
CMReleaseComp
Line: type=DigitalExtn 2 Call: lid=0 id=1316 in=0
Called[200] Type=Unknown (0) Reason=CMDRdirect Calling[19056650154] Type=Unknown Plan=Unknown Pres=Allowed (0)
Cause=16, Normal call clearing
Timed: 11/11/11 14:51
603084510mS CMExtnEvt: Bedroom 2: CMExtnHandler::SetCurrent( id: 1316->0 )
603084510mS CMCallEvt: 0.1316.0 -1 Bedroom 2.-1: StateChange: END=X CMCSCompleted->CMCSDelete
603084511mS CMCallEvt: 0.1316.0 -1 BaseEP: DELETE CMEndpoint f56ad128 TOTAL NOW=2 CALL_LIST=0
603084511mS CMExtnEvt: Extn208: CALL LOST (CMCauseNormal)
603084512mS CMExtnEvt: Extn208: Extn(208) Calling Party Number(19056650154) Type(CMNTypeUnknown)
603084512mS CMCallEvt: 0.1317.0 -1 Extn208.0: StateChange: END=X CMCSRinging->CMCSCompleted
603084512mS CMExtnEvt: v=2 State, new=PortRecoverDelay old=Ringing,0,0,Extn208
603084513mS CMExtnTx: v=208, p1=0
CMReleaseComp
Line: type=AnalogueExtn 18 Call: lid=0 id=2 in=0
Called[208] Type=Unknown (0) Reason=CMDRdirect Calling[19056650154] Type=Unknown Plan=Unknown Pres=Allowed (0)
BChan: slot=0 chan=8
UUI type=Local [......2Pd.] [0x01 0x01 0x00 0x00 0x01 0x02 0x32 0x50 0x64 0x00 ]
Cause=16, Normal call clearing
Timed: 11/11/11 14:51
603084513mS CMExtnEvt: Extn208: CMExtnHandler::SetCurrent( id: 1317->0 )
603084513mS CMCallEvt: 0.1317.0 -1 Extn208.-1: StateChange: END=X CMCSCompleted->CMCSDelete
603084513mS CMCallEvt: 0.1317.0 -1 BaseEP: DELETE CMEndpoint f56a567c TOTAL NOW=1 CALL_LIST=0
603084513mS CMCallEvt: END CALL:97 (f56acc88)
603084514mS CMCallEvt: 4.5.1 -1 BaseEP: DELETE CMEndpoint f568f2a4 TOTAL NOW=0 CALL_LIST=0
603084515mS CMMap: a=1.4 b=0.0 R0
603084516mS PRN: Config Write Wake Up
603084521mS CMExtnEvt: Bedroom 2: Recover Timer reason=CMTRWrapUp
603084521mS CMExtnEvt: v=4 State, new=Idle old=PortRecoverDelay,0,0,Bedroom 2
603084523mS CMExtnEvt: Extn208: Recover Timer reason=CMTRWrapUp
603084523mS CMExtnEvt: v=2 State, new=Idle old=PortRecoverDelay,0,0,Extn208
603084675mS RES: Fri 11/11/2011 14:51:30 FreeMem=72004032(3) CMMsg=4 (5) Buff=200 957 1000 7463 5 Links=3824
603084675mS RES2: IP 500 V2 6.1(5) Tasks=39 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=42 Poll=0 Ready=1 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
603085016mS PRN: Updates IO list size 0 updated list size 1
603085016mS PRN: Config Write Completed
 
Originally had it in line group 0, then changed it to line group 2, and created incoming call route 2.
 
It seems to ring the group Main.
You only have to pick it up i guess.


BAZINGA!

I'm not insane, my mother had me tested!
 
That was a normal call from a normal line.

Through the doorphone I get nothing.
 
Then it isn't detecting the line/voltage, make a shortcode of:

Shortcode - 888
Feature - Dial
Tel number - 888
Line Group - whatever that lines outgoing group id is :)

If SSA show no loop current detected in alarms, it is confirmed :)

NTE-wave-logo-for-a4-header.jpg
 
IPO not detecting line/voltage.

Shortcode not working.

Gettin' ticked!
 
The shortcode isn't working because the voltage is too low so it doesn't see the line, if "Gettin ticked" means you are annoyed, be annoyed at the doorphone you bought that can't even emulate a line properly, not at the system you feel you have been forced to learn.... that happens to be way better than the Nortel you are used to :)

NTE-wave-logo-for-a4-header.jpg
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top