I have seen this on a lot of sites. it seems very random. Some upgrades and some new sites.. Not sure what to do other than remove it on each incoming call route.
Kevin Wing
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries
Anyone raised it up to Avaya? Or have they asked for traces of everything including the number plate of the car you drive to work in, so you can't be bothered
OK, but that was good news for me. We have had this raised with Avaya but we are not able to reproduce the issue = case closed.
I would like to know if anyone else has raised this with Avaya and if they know when the fix will be implemented
I know what you mean, it's like thay are saying "You are an idiot unless you provide traces that prove otherwise, and even then if we don't see the same thing your still an idiot"
Seen it happen too.
It can be very annoying if you have 300 ddi numbers in your incoming call route
ACSS - SME (IP Office)
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
Happened on a upgrade from 4.1 to 4.2. Took a bit to figure out why phone manager displays were awry. Park buttons would only show "b" instead of caller number. Finally found it in a pmtrace which led to ICR.
Had a case open on it in early OCT 2009. He said he remembered it after I solved it. Case closed.
Check in the ICR on "DialIn" or another blank incomming number. Seen it after an upgrade (think it was 4.2.X and 5.X) that they place a "b" in the "tag" on the DialIn for the RemoteManager so if you have copied/changed that it could still be there.
___________________________________________
It works! Now if only I could remember what I did...
Once i have made a config with over fifty ICR routes each with its own named TAG and after a week in use all names had been replaced with b's.
So i don't think it has to do with copying the ICR routes.
I think it is a bug in IPO related to ISDN lines were there is a parameter copied from the ISDN call data to the IPO call data, since it not happens on every call it may be international calls or abandoned calls from certain destinations.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.