Search results for query: *

I'm all ears if you find some sort of fix for this issue. Prior to working around it, I tried just about everything I could with the analog trunks and the IPO configuration for my case. AKAIK it's not fixable via the IP Office.

Not that this is a good suggestion, but you can disable caller ID which will solve the issue. This problem is a) prevalent, b) annoying and c) yet to be fixed.

Hey Hal - Long time no talk (remember me from my 1A2 to partner install?) There are two solutions to this (none are desirable): 1. Do my workaround as documented here: http://www.waldrondigital.com/2011/05/19/crackle-and-buzzing-on-call-pickup-with-ip-office-analog-trunks-verizon-fios-fixed/...

Is the overflow list blank for your hunt group? It sounds silly, but have you checked your inbound call routes to make sure they are going to YOUR group instead of Main? Also time profiles can affect this too in your routes.

I AM the IT guy (my primary expertise) so I manage both their network AND Avaya system (they are friends and client). At war with myself I suppose!

I also mention that SSA still reports quality issues at the client in the previous post, but they say everything is working great now. Ugh x 2

Funny you mention the BS factor of SSA. I had a client on 5.0 (18) with tons of QoS/park issues that were real (remote IP phones). After the upgrade to 5.0 (23) the QoS issues went away, totally. They contacted an Avaya certified rep to get that gem of information as I was adamant about this...

This is why you are a genius Andy! Cheers mate.

I did some screenshots a while back. http://www.tek-tips.com/viewthread.cfm?qid=1578641&page=25

I don't get it. When I switch out out IPO (5.0(26)) SCN codec to g.711 over our MPLS QoS controlled Paetec circuit I get SSA alerts about packet loss. When I switch this to g.729 this never happens... ever. The calls sound fine with the fatty g.711 codec, nobody complains, so my question is...

@TTtommy - the CID is presented by this point. Is there a non-workaround fix you have in mind? Obviously better than my hack.

Sorry that should have read "NOT just hunt groups". Ugh... long day

I believe it's looking for an Outlook profile. I'd go SMTP server (if you have one) as it's way more foolproof. If you are sending to a single domain, you can always use your MX address in there. For instance, if all the alert/vm recips are at xyzcorp.com, use the incoming mail MX record for...

@bluemr2 - You can also use this workaround for extensions, but just hunt groups... Check out the blog article I wrote which spells it out in one place.

@bluemr2 - No caller ID works just fine and we are using embedded VM at this client. @klubar - No caller ID is a deal breaker for this client. Turning off caller ID or changing the lines to Loop start did fix the issue.

Also noted and documented here: http://www.waldrondigital.com/2011/05/19/crackle-and-buzzing-on-call-pickup-with-ip-office-analog-trunks-verizon-fios-fixed/

I will add that this only occupies a voicemail port for about .5 second before moving on to their primary hunt group... man I'm on a roll today!

Yes it's the CID causing issues for sure... Loop start solves it...

I HAVE A WORKAROUND!!!! Hunt Group = ENABLE ANNOUNCEMENTS (but record no announcement) Wait before announcement = 0 Post announcement tone RINGING No second or repeat. ---- This way the damn system picks the call up before the person can hear the crackling!

Of course I'd like to NOT have the client spend more money on any more modules, i.e. PRI interface, and hell I have no idea if Verizon can hand FIOS off on a PRI/BRI anyway... we are locked into a contract. Well if there's any analog configuration items that may affect this, I'm all ears...