Recent content by isrm

Hi All, I have a MiVO 250 (6.2 SP1) and a custom SIP application that needs to call the local users and also needs to call PSTN numbers. The SIP application is connected to the system using SIP trunks and I have no problem calling the local extensions or the local extensions calling the...

@kwbmitel - only comment is you no longer have a uniform dialing plan and it may require ARS changes in the cluster for RDN routing unless your using unknown number of digits to follow.

KwbMitel is correct, hunt groups will work. O course you have to manage multiple number this way. Another way would be to add more multi-line appearances of the number to the device, down side of this method is the queue depth is limited to the number of keys programmed. Upside, only one...

@kwbMitel, sorry missed the rel 6.0. Highly recommend upgrade though, simplifies the provisioning!

@brewski6666, Configure the DID's in the DID to terminate on the user (your current speedcall will work too, but the DID table is a much nicer implementation in my opinion . As kwbmitel says, make sure the campon is enabled. Configure the call coverage announcements for the desired RAD...

Check the recall timers on system B, sounds like it is recalling to nupoint before cfna timer expires on system C. The recall timer will be running on system B, as this is where the transfer is being performed

Think I will raise a ticket then, this is vital to make DID's useful.

@kwb - not messing with you, I tested it on my switch

@kwb, your right the help file states: "Enter a unique 1- to 26- digit Destination Number (internal Directory Number or any other termination point) to which the DID Number will be redirected. Valid digits are: 0-9, *, and #.". But this is incorrect the destination does not need to be unique...

kwbMitel, The docs might say you can't assign it, but the software lets you assign multiple DID's to the same destination.

Have you looked into the new DID table? seems like it would handle what you are looking to do.

Only one I am aware of(because I used it) is the Ascom wireless devices.

In the SIP Device Caps - Signalling and Header Manipulation - Allow Display Updates - set to yes. From the help: "Select Yes to allow the system to update SIP phone displays with connected party name and number information during transfers, conferences, and call forwarding scenarios." This may...

Define a System speedcall 6424 with the actual digits being your extension number. It will work for both internal and external callers (ring central).

Do a wireshark trace, if you see MCD sending a 180 to the Mediatrix then the problem is with Mediatrix, Also, check MOL for the config guide, believe you are looking for doc: 08-5159-00011