Author Topic: Mitel Collaboration Advanced - Dialing out from a conference call  (Read 3595 times)

Offline lrzuniga

  • Contributer
  • *
  • Posts: 27
  • Country: ca
  • Karma: +0/-0
    • View Profile
Hi,

For some reason I can't dial out when in a conference bridge. I get the message "Sorry we couldnt complete your call"

Here's what I'm trying:

1. calling into a conference bridge as participant (not as leader)
2. pressing ## to get options
3. pressing 2 to dial out
4. dial the number with a prepended 1, 8, 9 (tried them all)
that's when I get the message "Sorry we couldnt complete your call"
If the call goes through, I understand that by pressing ** I will bring them into the conference bridge

Checked the default user settings and "Dial Out Allowed" is checked...so not sure where else to look

Any help is appreciated.

Luis


Offline lrzuniga

  • Contributer
  • *
  • Posts: 27
  • Country: ca
  • Karma: +0/-0
    • View Profile
Re: Mitel Collaboration Advanced - Dialing out from a conference call
« Reply #1 on: December 17, 2014, 02:08:26 PM »
Spoke to Mitel SE and he thinks the issue is between the MAS and PBX....translation or routing....

Either way, not sure how to check or fix.

Offline lrzuniga

  • Contributer
  • *
  • Posts: 27
  • Country: ca
  • Karma: +0/-0
    • View Profile
Re: Mitel Collaboration Advanced - Dialing out from a conference call
« Reply #2 on: December 17, 2014, 06:40:03 PM »
From the proxy logs (note, I changed some info for security/privacy the number called was not 6475551439):

Dec 17 16:49:51.087124 Sending to UDP_CH socket (192.168.8.2:5060):
INVITE sip:916475551439@192.168.8.2 SIP/2.0
Via: SIP/2.0/UDP 192.168.8.4:6064
Call-ID: 874383741@xxx
CSeq: 1 INVITE
From: user1 <sip:630@192.168.8.2>;tag=440771848
To: sip:916475551439@192.168.8.2
Contact: sip:192.168.8.4:6064
User-Agent: Mitel-MCA 5.0.0.41-1
Content-Length: 343
Content-type: application/sdp

Dec 17 16:49:51.104736 Received UDP message from socket 7 (UDP_CH 192.168.8.2:5060):
SIP/2.0 100 Trying

Via: SIP/2.0/UDP 192.168.8.4:6064 ;received=192.168.8.2:5060
Call-ID: 874383741@xxx
CSeq: 1 INVITE
From: user1 <sip:630@192.168.8.2>;tag=440771848
To: sip:916475551439@192.168.8.2;tag=0_1954851808-108783547
Content-Length: 0

Dec 17 16:49:51.260870 Received UDP message from socket 7 (UDP_CH 192.168.8.2:5060):
SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 192.168.8.4:6064 ;received=192.168.8.2:5060
Call-ID: 874383741@xxx
CSeq: 1 INVITE
From: user <sip:630@192.168.8.2>;tag=440771848
To: sip:916475551439@192.168.8.2;tag=0_1954851808-108783547
Contact: sip:192.168.8.2
Warning: 399 192.168.8.2 "29H Access Barred"
Server: Mitel-3300-ICP 12.0.1.24
Content-Length: 0

Offline ralph

  • Mitel Forums Admin
  • Hero Member
  • *****
  • Posts: 5767
  • Country: us
  • Karma: +469/-0
  • Published Author: http://amzn.to/2dcYSY5
    • View Profile
Re: Mitel Collaboration Advanced - Dialing out from a conference call
« Reply #3 on: December 17, 2014, 07:15:39 PM »
I believe the issue is going to be in you PBX.
Be sure your collaboration ports have a COR and a COS that allow it to dial out.
One way to test this is to set your own phone to use the same COS and COR as the conference ports - then make an outside call.
If that works then have someone call you from the outside and then try to transfer it back out to an outside phone.
This will help you isolate where the problem is or is not.

Ralph

Offline kbobinger75

  • New Member
  • *
  • Posts: 3
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Mitel Collaboration Advanced - Dialing out from a conference call
« Reply #4 on: May 12, 2020, 01:23:30 PM »
Did you ever find a resolution to this issue?


 

Sitemap 1 2 3 4 5 6 7 8 9 10