Getting dead air

[Jeremiah8]

We have an IP Office 406 V2 running the 4.0 software. I know this is just GA not Maint. Release, but I was wondering if anyone else was having this problem.

We have 7 analog phone lines. What I'm seeing is that when 6 lines are in use, on calls or queued up, when a 7th person calls in, it rings several times for them then goes to dead air. Usually the caller hangs up.

I have traced it to one of the analog ports. When I run the Monitor program I get the following lines:
(I've removed the caller ID and caller number from the log)

CALL:2007/03/1411:51,00:06:56,005,##########,I,300,,<Lastname>,<First Name>,,,1,,""n/a,0

Here's the long version

164573431mS ERR: TFTP Write:: Too many retries (from 192.168.0.38, 49603) file=nasystem
164573882mS RES: Wed 14/3/2007 11:58:46 FreeMem=42654096(462) CMMsg=7 (7) Buff=100 587 489 1092 2 Links=8437
164576810mS CMCallEvt: 409.12.1 1163 Alog Trunk:409: StateChange: END=A CMCSConnected->CMCSCompleted
164576817mS CMLOGGING: CALL:2007/03/1411:51,00:06:56,005,##########,I,300,,<Lastname>,<First Name>,,,1,,""n/a,0
164576830mS CMCallEvt: 0.9628.0 1163 ACDTep(PDX Tech): StateChange: END=??? CMCSRinging->CMCSDelete
164576831mS CMCallEvt: 0.9628.0 -1 BaseEP: DELETE CMEndpoint fe887e08 TOTAL NOW=1223 CALL_LIST=5
164576832mS CMCallEvt: 409.12.1 -1 Alog Trunk:409: StateChange: END=X CMCSCompleted->CMCSDelete
164576834mS CMCallEvt: 0.9667.0 -1 BaseEP: DELETE CMEndpoint fe88508c TOTAL NOW=1222 CALL_LIST=5
164576841mS CMCallEvt: 0.9653.0 -1 Extn201.0: StateChange: END=X CMCSRinging->CMCSCompleted
164576842mS CMCallEvt: 0.9653.0 -1 Extn201.-1: StateChange: END=X CMCSCompleted->CMCSDelete
164576844mS CMCallEvt: 0.9653.0 -1 BaseEP: DELETE CMEndpoint feb4b2a4 TOTAL NOW=1221 CALL_LIST=5
164576844mS CMCallEvt: END CALL:1163
164576852mS CMCallEvt: 409.12.1 -1 BaseEP: DELETE CMEndpoint fe8c71ac TOTAL NOW=1220 CALL_LIST=5
164583122mS CMCallEvt: 0.9668.0 1165 MHigbie.0: StateChange: END=T CMCSRinging->CMCSConnReq
164583123mS CMCallEvt: 0.9665.0 1165 TargetingEP: RequestEnd 0.9668.0 1165 MHigbie.0
164583124mS CMLOGGING: CALL:2007/03/1411:02,00:54:52,000,,O,,,,,,0,,""n/a,0
164583127mS CMCallEvt: 0.9098.0 1098 ACDTep(PDX Tech:SYNC:2): StateChange: END=??? CMCSIdle->CMCSDelete
164583128mS CMCallEvt: 0.9098.0 -1 BaseEP: DELETE CMEndpoint fe929910 TOTAL NOW=1219 CALL_LIST=4
164583129mS CMCallEvt: 0.9666.0 -1 BaseEP: DELETE CMEndpoint fe889e34 TOTAL NOW=1218 CALL_LIST=4
164583130mS CMCallEvt: END CALL:1098
164583139mS CMCallEvt: 0.9096.0 -1 BaseEP: DELETE CMEndpoint fe95a950 TOTAL NOW=1217 CALL_LIST=4
164583141mS CMCallEvt: 0.9656.0 1165 ACDTep(PDX Tech): StateChange: END=??? CMCSRinging->CMCSDelete
164583143mS CMCallEvt: 0.9656.0 -1 BaseEP: DELETE CMEndpoint fe897634 TOTAL NOW=1216 CALL_LIST=4
164583144mS CMCallEvt: 0.9665.0 -1 BaseEP: DELETE CMEndpoint fe932468 TOTAL NOW=1215 CALL_LIST=4
164583147mS CMCallEvt: 0.9668.0 1165 MHigbie.0: StateChange: END=B CMCSConnReq->CMCSConnected
164583381mS RES: Wed 14/3/2007 11:58:56 FreeMem=42708640(511) CMMsg=7 (7) Buff=100 584 484 1089 2 Links=8461
164583810mS H323Evt: Recv: RegistrationRequest c0a800f8; Endpoints registered: 4; Endpoints in registration: 0
164584964mS PRN: Config Write Wake Up
164585464mS PRN: IO List Size 1
164585464mS PRN: Sending Config out to feb4bcc8 started
164585465mS PRN: Start WriteConfig at fed793c8 savemode 0 writetype 2

 

[aarenot]

could have been the programming of the line port. Upgrades can sometimes "change" things even though they are not supposed to.

If everything worked like in the book, or was even in the book I might not have a job.

 

[Jeremiah8]

Shine52,
No busy signal. Here's a breakdown of the setup:

Line 1 & 2 go to the sales hunt group. No problems there.

Line 3-9 go into the support hunt group. Line 409 (for some reason the system calls it 409 rather than 9, it is the 7th physical phone line for the support group) is the problem child.

I set lines 410-416 to "out of service". What I did today was change line 410 to "Loop start ICLID" and changed the ICR to route the calls to the support hunt group. Now we don't get the dead air each time.

J.

 

[aarenot]

You could try reprogramming then settings on the old line 7 port to match the new port you plugged it into which is working properly.

If under warranty, I would get it looked at if reprogramming it does not fix it.

If not, just leave it on the new port, you have plenty extra not in use.

Makle sure to remember in lines to change the old one to out of service, and i would change it's incoming, and outgoing groups number to an unused one as well.