Search results for query: *

Have you checked the number of trunks assigned to the trunk group vs the trunks and voiceports on the switch admin screen. The port calculator can help to come up with the numbers on this. Perhaps you don't have the numbers matching, and that is why the call goes to dead air.

Also a note, the call type for 1809 calls should be fnpa not intl. I block these calls all the time, with the ars ana showing 1809, 11, 11, route pattern (deny) and fnpa this call will not pass from this ars location. good luck

I am looking for specs on what Avaya is sending when the call type in a route pattern is hnpa versus locl. When changing a customer over from one PRI service to Bell in Canada my S8300's are not able to make local calls using hnpa as they were before. More important the alrt feature for crisis...

I can't find any specific info on the power up procedure when adding on an additional em200.Does the g430 need to be powered down in order to see the new em200? thanks

The firmaware on the G430 needs to be at least 29.24.4. It will fix this issue with "no boards" in the em200.

Thread690-1337228 was responded to by Donbott with reference out of the book. I am experiencing the exact problem "event 11" and need to find the book he is talking about. Please respond with info .

FYI Thanks for your help. There was no more accurate match in the master ars, although that is where the switch is getting the (wrong)route from. We fixed it with a new service pack 14682 and some creative programming. Thanks again.

I did check the route tables and from location 7 (the originating NR) the route would be P2, if the call is being routed from the destination NR the route would be p32. Both of these route patterns should pass the call. On our trace of the TAC it is using p32 which has a FRL that should pass...

The NR where the call originates, the VDN has a FRL of 0, the VDN that is trying to send the call out has a FRL of 2. We tried changing the FRL of the VDNs - no change. All route patterns look okay. Anything else to suggest??

I have a switch with mulitple partitions. In vectoring my call is routed from one NR to another and when the vector step tries to send the call to a third party I get a denial event 1343"need higher FRL". VDN COR at all locations are higher that the route chosen. Need help!!