 | |
| |||||||||||||||
| |||||||||||||||
| Mitel Ask Questions and Find Answers on Mitel Systems: |
 |
| | LinkBack | Thread Tools | Display Modes |
| | |
| |||||||||||||||
| |||||||||||||||
| Mitel Ask Questions and Find Answers on Mitel Systems: |
|
| | LinkBack | Thread Tools | Display Modes |
 06-30-2009 | #1 (permalink) | ||||||||
| Junior Member 
Rep Power: 0  Country:  | Conference call issue As I write this, I'm working with one of my field tech and I'm in queue for Mitel Tech support. But here's what happens: users cannot conference more than 1 outside call. Inside calls work fines, 1 trunk and one ext is fine but not 2 or more trunks. Checked COS for both phones and trunks: Brokers call is off, conference call is on, public net acces is on. Check Sys Ops. : 8 CO trunks, 8 parties, 8 Max trunks. Interconnect checking is off. If you call from prime line of a phone, put it on hold and call from a second line you can then ADD HELD effectivily creating the conference I couldn't create by pressing the conference key. Bizzar to me. 5530 set. I'll update this as soon as I figure it out. Dry Aquaman. | ||||||||
 |   |
| 06-30-2009 | #2 (permalink) | ||||||||
| Junior Member
Rep Power: 0 Country: | Found the problem. Had to go to second level support. In the PRI protocol assignment Replace External CLID: "Replace External CLID:" had to be set to true. Problem was that when hitting the xfer button, CLID showed the CLID of the transferred caller. Carrier rejected the call. Dry Aquaman | ||||||||
| | |
| 06-30-2009 | #3 (permalink) | ||||||||
| Moderator   acejavelin is a high-tech, heavy metal redneck!
Location: Southeastern Minnesota Rep Power: 2 Gender:  Country: | Be aware most carriers can allow this to work but usually don't by default. The carrier rejects the call because they see the CLID of the original call as not being a valid billing number on the PRI, therefore invalid and the call is rejected. They can usually set the PRI to allow these calls, and if the CLID is invalid, they substitute the main telephone number for billing purposes thus allowing the call and the appropriate CLID to be displayed. Run into this all the time with Mobile Extension sending out the original caller's CLID information on a PRI. BTW, what's a 5530 set???  (Just kidding, I am sure its a typo) __________________ Telephony users cannot gain anything without first giving something in return. To obtain a useful feature, a feature of equal value must be lost. This is Telephony’s First Law of Equivalent Exchange. Last edited by acejavelin; 06-30-2009 at 02:18 PM. | ||||||||
| | |
| 06-30-2009 | #4 (permalink) | ||||||||
| Junior Member
Rep Power: 0 Country: | Yeah. I actually guessed the carrier part of the call rejection for the same reasons you stated - Mobility. (also seen it on a Nortel) I just didn't know how to fix it. This was one of our Telrad customers. Our install group upgraded them last week to a 3300 but that little bit of info hasn't filtered down to us yet. We sent a Telrad tech out and he ends up calling me for assist. This tech just learned how to spell Mitel. (- Could have been worse I suppose -) So now I'm trying to walk him through everything that needs to be checked. Dang I wish we had our AWC up and working. Dry Aquaman. BTW: a 5530 is a 5330 + an additional 200 just becuase I like it. | ||||||||
| | |
|
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
 Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Disable call transfer and Call Conference | sam | Inter-Tel | 1 | 06-10-2009 03:30 PM |
| conference call | nemohot | MD 110 SUPPORT | 4 | 01-07-2009 09:47 AM |
| conference call | mikelo | Cisco | 1 | 03-02-2007 09:30 PM |
| Conference call issue | jhammond | Mitel | 6 | 08-26-2004 05:12 AM |
| Conference issue | MrClean61 | Meridian Systems | 4 | 04-05-2004 04:51 PM |
Linear Mode
