Search results for query: *

this is an ip routing problem. ensure that the medpros on each end know their default gateways, and that they're able to reach the far-end router and far-end medpro.

do you have Session Manager? you can employ an adaption to do just what you're describing. I'm trying to think of a way to use variables, but I don't know of any way to capture the called number.

hey, mr. customer. here's an idea: either accept the fact that you're running 15-yr-old hardware and software, and put up with minor annoyances, or UPGRADE to a modern system that has these capabilities built in. i know this isn't helpful, but sheesh.

are you using location-based ARS? this should be looking at the "all" table for routing -- do a list ars ana if there are no entries, that's probably your issue. another useful command is li ars rou 1800xxxxxxx also, check the cor of the session manager trunk group. make sure the frl is...

are you running sp3? the core for this customer has not been patched yet, so just wondering if it's still buggy with the latest code.

Hi 1Jumbo... I am finding the exact same condition on a site I just turned up. Did you ever find a resolution to this?

sounds like this is something i should know how to do... ...but don't. is there an easy tutorial on how to do this? i was going to remove the mailbox and re-input it, but reloading the fedb sounds promising - and less drastic.

Hello all, I have a subscriber whose messages are hanging around as deleted - never being removed from the message store. Running SP5/003. anybody seen this?

to my recollection, there's a daughter board on the power supply that supplies ringing voltage for the 012s. maybe that went bad? try a new power supply?

personally, i agree. you don't get much added functionality, if any, but way more problems. they come in handy as a switch/phone when all you have is one CatV drop to a desk, or for remote offices where you don't want to install a gateway. other than that, the real sweet spot of IP telephony...

sorry, no. just what's in the ol' noggin. the docs probably have a walk through on UDP somewhere.

use the uniform dialing table. works a bit like ars analysis. input the dialed string (extension number), and append an aar code (222, 100, whatever makes sense for your network). go to the aar analysis table and send that dialed string (now beginning with the aforementioned aar code) to a...

that's the first thing that occurred to me, as well. check that the remote IPO knows its default gateway. then check to see if firewalls are blocking any UDP ports.

funny. that's kinda what i figured. we're at 550 now, with another four sites to add. guess its time to upgrade! what a shame! as an aside - since we're talking practicalities - the documentation specifies that an SCN should be hub and spoke. has anyone successfully accomplished a mesh...

they are on the same subnet, and i've brought that to the attention of my boss. only my third week on the job - oh, how these boxes can initiate a newbie! BTW, we isolated it to one user's laptop. we segregated her off to her own private network today, and guess what? no problems! still...

i know i read that somewhere. guess i overlooked the 500 users thing. is this a realistic cap, or is this just one of the arbitrary numbers that avaya throws out? what symptoms will begin to show for an overtaxed SCN? will the less powerful boxes - for instance the 403 in question - be more...

ummmmm... so what happens if the SCN > 500 users?

Excellent. Thanks so much - I finally have an explanation that makes sense!

Much thanks, bro. That only goes for users, right? Lines and Hunt Groups don't fall into the unique category, right? Maybe this is a stupid question, but does that include the NoUser and RemoteManager Users? Should they be NoUserA, NoUserB, etc.? Not to argue with you, but there is a direct...

I'm submitting this problem to you again... It seems that the Callback messages are just the IPO's way of complaining about delay. After further investigation, these messages are generated when the IPO is putting out a BLF broadcast to port 50799. We've replace the 403, the VCM, changed the...