Recent Posts

Pages: [1] 2 3 ... 10
1
What type of outside lines do you have?  SIP, PRI or ?  If you have PRI or POTS lines, can you connect a plain jane phone or a but set to the telephone lines to see if you have dial tone and are able to make and receive a phone call?  If you are able to test the lines, it might save you from the telco charging you if the problem isn't in there lines.

Jeff
2
Unrelated to the paging system, but I think it was a nice fix, only took me a while to figure it out.  Maybe it will help someone else. 

We only have four nodes.  Most locations are at warehouses/offices associated with growing and packing apples.  One is at a golf course, with a restaurant.  I switched them from a Avaya Partner to a node on our Mitel system a while back.  They were frustrated with Google Reservations, after I switched them from the Partner to Avaya it started calling the wrong number for reservations.  The number Google started calling (via DEE) was an employees cell.  I fixed Google calling wrong number by pointing the number at the restaurant phones, bypassing the phone tree.  Not ideal.  I finally figured out Google reservations always showed the same caller ID.  So I added the number Google used to call routing table three and pointed it to the restaurant phone extensions--like how I route harassing phone callers to a very long pause/greeting/dead air in a CRA, then it hangs up.  Yes, that is whack-a-mole, but works for unsophisticated callers.  Then I was able to route the restaurant number back to the phone tree and they were happy, yea. 

Anyway, maybe this will help someone else.  Again, thanks to everyone who has helped me and thanks for the knowledge in this forum. 

Jeff
3
TE,

A million thanks for the ideas. 

What I didn't finish adding to the post is we do have 50 pair copper part of the way and 25 pair copper the remainder of the way from the node to the paging system amp location.  Distance between node and paging system is about 1,800 to 2,000 feet.  I didn't think the copper would carry sound 2,000 feet--I was thinking of line level sound, not a telephone line.  When you mentioned copper, I realized it's a telephone line/signal/sound, not line level sound.  Kind of a 'Doh" moment.  Thanks, thanks, thanks!

My work duties include telephone, paging and a an assortment of other duties.  It would be nice if I could be responsible for just telephones, so I could keep sharp in that area.  When I work in something (like paging) once a year or every other year, it's a bit tough for me.  Such is life and I will find some cheese to go with that whine... :)  In another three weeks, it will be behind me as I will be retiring.  A new challenge, and one I am mostly looking forward to.  I appreciate all the information I have learned and the help I have received on this forum. 

I (and my replacement) will connect the cables and see what the paging system sounds like from a LS on the node to the paging system.  Six to eight hundred feet of the cable is somewhat iffy, the cable is PE, but not icky pic and is run through underground conduit.  There are three other 25 pair inside type cables in the same conduit and they have had issues with cross talk. We haven't used the 25 pair PE cable in a while, so maybe (I can't remember) there is a good pair in the cable we can use.   I will post with the results, it might be early next week.

TE, thanks, thanks, thanks,

Jeff, who will be on John's Island full time soon.
4
MiVoice Office 250/Mitel 5000 / Re: Mivoice 250 Auto Attendant
« Last post by Tech Electronics on Yesterday at 02:59:40 PM »
Spztc1,

When you look at the menu options what do you show option 3 going to?

I assume based on your text that it is supposed to be a Hunt Group of some sort which the AA should be able to route to without a mailbox or extension ID.

I would try deleting the programming in option 3 and recreating it.

You may also want to try a different digit to see if the problem is a DTMF issue and not a problem with the Call Routing Announcement.

Thanks,

TE
5
Jeff,

I am going to assume you don't have copper that would allow you to connect directly to that site.

That being said it depends on whether or not you want it to be in a Page Zone or not. As you probably already know you can only put Digital/IP Phones, Trunks or Paging Interfaces in a Page Zone, basically no direct SIP devices.

Now that doesn't mean you can't use something like the Valcom V-811A or V-821A and then push that over via SIP to another Valcom Paging Device, kind of like what you want to do with option 3.

I know Valcom is a bit expensive, but you may be able to find something comparable by Viking Electronics, Bogen or Terracom. Basically, you are looking for a SIP Gateway that will allow you to use FXO/FXS/Paging Interface that would then connect to another SIP Device at the other location. This is assuming that the network is extended between the two sites in one way or another.

Thanks,

TE
6
I want to install a paging system in a location different from the node.  Paging system is about 1,800 to 2,000 feet away from node.  Paging system is a Bogen PCM, which can accept a trunk or extension/station for paging input.  Node is a HX box.

Options I am aware of are:
1. ATA using a FXO or FXS.  Doesn't look like I can add this to a page zone, however I could create a phantom, add it to the page zone and forward the phantom to the ATA, which would then connect to the page system

2. Connect a 5320 speaker to the paging system amp, wouldn't use the Bogen PCM.

3. Connect a node LS trunk to a set of ATA in peer mode, which then would connect to the page system.

4. Don't bother connecting the Bogen to a page zone, just use an ATA and program phones with that extension and//or tell people to call the ATA extension to page. 

I have seen IP paging modules by Teracomm.  Perhaps they have something that would work. 

I would guess others have dealt with this before and have better solutions than I have mentioned above or how do you handle this sort of situation.  I wish I could just add a SIP extension to a page zone. 

Thanks in advance for any ideas to stop me from pulling out more hair.  :)

Jeff

 



3. Run a long A$$ cable from the node LS to the paging system.  25 pair cable is already in place for part of run, not sure of gauge.
7
MiVoice Office 250/Mitel 5000 / Mivoice 250 Auto Attendant
« Last post by Spztc1 on Yesterday at 12:30:53 PM »
Hi

We have an auto attendant application under voice processor in our Mivoice 250.  We just recently discovered that prompt 3 is repeating even though it is set to ring to a group extension.

We call a tracking number that rings to our Direct Dial number that is pointed to the Auto Attendant extension.  The AA  picks up fine but when we are in the submenu only prompts 1 and 2 work correctly.  I have to hit prompt 3 twice before it rings and then it does not ring into the group it rings to one single extension. It seems like it is a timing issue and if we don't hit the prompt in enough time it does not route like it should but I am not sure.
I have not seen this before.
Any direction would be greatly appreciated.

Thanks
8
Turns out we can't update without software assurance, which we don't have, so updating the software isn't an option at this point. Is there anything else that might be causing this other than outdated software?
9
jrichter,

The best thing is to start at the beginning which would be one of two things.

ISDN Trunks
System > Devices and Feature Codes > CO Trunk Groups > {Trunk Group} > Day Ring-In Type

SIP Trunks
System > Devices and Feature Codes > SIP Peers > SIP Trunk Groups > {Trunk Group} > Trunk Group Configuration > Day Ring-In Type

Regardless of which one it is you need to make sure that the Day Ring-In Type is going to the Call Routing Table you want to use for Blocking. I am not going to refer to them as Day or Night as technically that is just a label you assign to the Call Routing Table.

Inside of the Table [System > Trunk-Related Information > Call Routing Tables] you need to make sure three things happen.

1. The Call Routing Key is set to Outside Party Number.
2. The Pattern that is coming in matches what the system sees.
3. The last two Patterns [E and +] sends the call to a Call Routing Table that has a Routing Key set to Trunk Number so it gets routed based on incoming DID pattern.

Hopefully that allows you to find the issue you are having. If you think all of the above is correctly configured, then we can look at what Pattern you have versus what Pattern the system sees.

Thanks,

TE
Pages: [1] 2 3 ... 10