I have a problem with denial event 1166. Below is some history and list traces.
2803 can call the outbound number successfully.
2888 cannot dial the outbound number,
Several phones are unable to dial a particular number but most phones can. We have tried changing COR's, Route Patterns, outbound trunks, phones, FRL's, route patterns, hardware, etc. We removed station 2888 and rebuilt it, we duplicated station 2888 from 2803, no joy. Bridged appearances of 2888 on station 2803 does not work. I am beginning to believe there may be an underlying database problem in the Communications Manager. CM 6.2. Any help would be appreciated.
Below are some list traces; This first trace shows a successfull call from station 2803.
09:25:41 TRACE STARTED 03/28/2013 CM Release String cold-00.1.510.1-19528
09:25:44 active station 2803 cid 0xf9c
09:25:44 G711MU ssff ps:20
rgn:21 [10.76.36.12]:31268
rgn:21 [10.11.98.15]:2108
VOIP data from: [10.11.98.15]:2108
09:25:55 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:25:55 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
09:25:57 dial 918566633888 routeREFIX|FNPA|ARS
09:25:57 term trunk-group 201 cid 0xf9c
09:25:57 dial 918566633888 routeREFIX|FNPA|ARS
09:25:57 route-pattern 201 preference 1 location 2 cid 0xf9c
09:25:57 seize trunk-group 201 member 4 cid 0xf9c
09:25:57 Setup digits 18566633888
09:25:57 Calling Number & Name 4048882803 NO-CPName
09:25:57 Proceed trunk-group 201 member 4 cid 0xf9c
09:25:58 Alert trunk-group 201 member 4 cid 0xf9c
09:25:58 active trunk-group 201 member 4 cid 0xf9c
09:26:02 idle station 2803 cid 0xf9c
The second trace shows an unsuccessfull call from station 2888.
09:29:42 TRACE STARTED 03/28/2013 CM Release String cold-00.1.510.1-19528
09:29:56 active station 2888 cid 0x10a9
09:29:56 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.17]:2066
09:30:02 dial 918566633888 routeREFIX|FNPA|ARS
09:30:02 term trunk-group 201 cid 0x10a9
09:30:02 dial 918566633888 routeREFIX|FNPA|ARS
09:30:02 route-pattern 201 preference 1 location 2 cid 0x10a9
09:30:02 seize trunk-group 201 member 19 cid 0x10a9
09:30:02 Setup digits 18566633888
09:30:02 Calling Number & Name 4048882888 NO-CPName
09:30:02 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.15]:2104
09:30:02 Proceed trunk-group 201 member 19 cid 0x10a9
09:30:03 denial event 1166: Unassigned number D1=0x9d75 D2=0x390101
09:30:03 idle trunk-group 201 member 19 cid 0x10a9
09:30:05 idle station 2888 cid 0x10a9
09:30:07 active station 2888 cid 0x10bb
09:30:07 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.17]:2072
09:30:08 idle station 2888 cid 0x10bb
This is a 3rd list trace from 2888 to the same NPA/NXX and it was successful.
09:31:13 TRACE STARTED 03/28/2013 CM Release String cold-00.1.510.1-19528
09:31:22 active station 2888 cid 0x1105
09:31:22 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.17]:2056
09:31:29 dial 918566634853 routeREFIX|FNPA|ARS
09:31:29 term trunk-group 201 cid 0x1105
09:31:29 dial 918566634853 routeREFIX|FNPA|ARS
09:31:29 route-pattern 201 preference 1 location 2 cid 0x1105
09:31:29 seize trunk-group 201 member 21 cid 0x1105
09:31:29 Setup digits 18566634853
09:31:29 Calling Number & Name 4048882888 NO-CPName
09:31:29 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.15]:2066
09:31:29 Proceed trunk-group 201 member 21 cid 0x1105
09:31:30 Alert trunk-group 201 member 21 cid 0x1105
VOIP data from: [10.11.98.15]:2066
09:31:32 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:0 Avg:0
09:31:32 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.11.98.15]:2066
09:31:42 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:31:42 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.11.98.15]:2066
09:31:52 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:31:52 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.11.98.15]:2066
09:32:02 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:32:02 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
09:32:03 idle station 2888 cid 0x1105
2803 can call the outbound number successfully.
2888 cannot dial the outbound number,
Several phones are unable to dial a particular number but most phones can. We have tried changing COR's, Route Patterns, outbound trunks, phones, FRL's, route patterns, hardware, etc. We removed station 2888 and rebuilt it, we duplicated station 2888 from 2803, no joy. Bridged appearances of 2888 on station 2803 does not work. I am beginning to believe there may be an underlying database problem in the Communications Manager. CM 6.2. Any help would be appreciated.
Below are some list traces; This first trace shows a successfull call from station 2803.
09:25:41 TRACE STARTED 03/28/2013 CM Release String cold-00.1.510.1-19528
09:25:44 active station 2803 cid 0xf9c
09:25:44 G711MU ssff ps:20
rgn:21 [10.76.36.12]:31268
rgn:21 [10.11.98.15]:2108
VOIP data from: [10.11.98.15]:2108
09:25:55 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:25:55 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
09:25:57 dial 918566633888 routeREFIX|FNPA|ARS
09:25:57 term trunk-group 201 cid 0xf9c
09:25:57 dial 918566633888 routeREFIX|FNPA|ARS
09:25:57 route-pattern 201 preference 1 location 2 cid 0xf9c
09:25:57 seize trunk-group 201 member 4 cid 0xf9c
09:25:57 Setup digits 18566633888
09:25:57 Calling Number & Name 4048882803 NO-CPName
09:25:57 Proceed trunk-group 201 member 4 cid 0xf9c
09:25:58 Alert trunk-group 201 member 4 cid 0xf9c
09:25:58 active trunk-group 201 member 4 cid 0xf9c
09:26:02 idle station 2803 cid 0xf9c
The second trace shows an unsuccessfull call from station 2888.
09:29:42 TRACE STARTED 03/28/2013 CM Release String cold-00.1.510.1-19528
09:29:56 active station 2888 cid 0x10a9
09:29:56 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.17]:2066
09:30:02 dial 918566633888 routeREFIX|FNPA|ARS
09:30:02 term trunk-group 201 cid 0x10a9
09:30:02 dial 918566633888 routeREFIX|FNPA|ARS
09:30:02 route-pattern 201 preference 1 location 2 cid 0x10a9
09:30:02 seize trunk-group 201 member 19 cid 0x10a9
09:30:02 Setup digits 18566633888
09:30:02 Calling Number & Name 4048882888 NO-CPName
09:30:02 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.15]:2104
09:30:02 Proceed trunk-group 201 member 19 cid 0x10a9
09:30:03 denial event 1166: Unassigned number D1=0x9d75 D2=0x390101
09:30:03 idle trunk-group 201 member 19 cid 0x10a9
09:30:05 idle station 2888 cid 0x10a9
09:30:07 active station 2888 cid 0x10bb
09:30:07 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.17]:2072
09:30:08 idle station 2888 cid 0x10bb
This is a 3rd list trace from 2888 to the same NPA/NXX and it was successful.
09:31:13 TRACE STARTED 03/28/2013 CM Release String cold-00.1.510.1-19528
09:31:22 active station 2888 cid 0x1105
09:31:22 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.17]:2056
09:31:29 dial 918566634853 routeREFIX|FNPA|ARS
09:31:29 term trunk-group 201 cid 0x1105
09:31:29 dial 918566634853 routeREFIX|FNPA|ARS
09:31:29 route-pattern 201 preference 1 location 2 cid 0x1105
09:31:29 seize trunk-group 201 member 21 cid 0x1105
09:31:29 Setup digits 18566634853
09:31:29 Calling Number & Name 4048882888 NO-CPName
09:31:29 G711MU ssff ps:20
rgn:21 [10.76.36.30]:35652
rgn:21 [10.11.98.15]:2066
09:31:29 Proceed trunk-group 201 member 21 cid 0x1105
09:31:30 Alert trunk-group 201 member 21 cid 0x1105
VOIP data from: [10.11.98.15]:2066
09:31:32 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:0 Avg:0
09:31:32 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.11.98.15]:2066
09:31:42 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:31:42 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.11.98.15]:2066
09:31:52 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:31:52 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
VOIP data from: [10.11.98.15]:2066
09:32:02 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
09:32:02 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
09:32:03 idle station 2888 cid 0x1105