Solved Adhoc Conference calls not working

Status
Not open for further replies.

Reso

Premier Customer
Basic Certified
Joined
Nov 7, 2019
Messages
16
Reaction score
1
Server OS : Windows 10

3CX Version: 16.0.676
Phones: Grandstream 2135 and 1628 with the supported firmware.

I have an odd problem. I am trying to create ad hoc conference call (https://www.3cx.com/blog/voip-howto/create-conference-using-desk-phone/) using the above mentioned models. I can call 700 from all phones and get the voice prompt. However it doesn’t create or let me join a conference call. After a few seconds it says “Invalid Pin Number”. I don’t have a Pin set for the organizer to enter.

Here is the odd part. I can make and join conference calls on model 2135 WITHOUT phone provisioning. If I provision it says “Invalid Pin number” again. The models 1628 gets the voice prompt “Invalid Pin number” either provisioned or not. Please help.
 
Hello,

You probably have a PIN requirement. Read the article again on step 2. You will find your PIN in the management console under Settings > Conferencing > Audio

Note: We are discussing in the context of properly provisioned phones without custom templates to get the expected behavior.
 
Thats the problem. I removed the PIN requirement but its still giving me the same voice prompt. The only phone i can make the conference call is 2135. That also without provisioning. Once i provision that phone, i get the voice prompt "invalid pin number".
 
  • 3CX Version, Standard Annual 16.0.676
  • Server OS, Windows 10 pro
  • Is the 3CX Server Hosted and where? hosted on premise
  • IP Phone Make/Model/Firmware Grandstream 2135 and 1628, 1.0.9.135 and 1.0.4.132 respectively.
  • Provisioning Method: Local LAN
  • Trunk Provider or Gateway Make/Model: No trunk yet as it is in testing.
  • Has the Firewall Checker passed: I haven't checked this as I am not doing any outside calls testing yet
  • Are custom Phone Templates being used: No custom templates
Hello, above are the requested details. I am still trying different ways to do this. Will update. Thank you.
 
12/05/2019 12:40:53 PM - Endpoint Extn:108 has refreshed contact <sip:108@XXXXXXXXXXXXXXX:5060/UDP>
12/05/2019 12:40:17 PM - Stop call record for leg L:1.1[Extn:108]
12/05/2019 12:40:17 PM - Removing leg L:1.1[Extn:108]
12/05/2019 12:40:17 PM - L:1.1[Extn:108]: Terminating targets, reason: SIP ;cause=200 ;text="User hangup"
12/05/2019 12:40:17 PM - Leg L:1.1[Extn:108] is terminated: Cause: BYE from XXXXXXXXXXXXXXX:5060
12/05/2019 12:40:17 PM - Call(C:1), Extn:108 on entry: DlgInfo(1-3762/Terminated / I)
12/05/2019 12:40:17 PM - Notify dialog-info: Extn:108: sip:108@XXXXXXXXXXXXXXX:5060, Call(C:1)
12/05/2019 12:40:17 PM - L:1.1[Extn:108] got Terminated Recv Req BYE from XXXXXXXXXXXXXXX:5060 tid=779291063 Call-ID=YYYYYYYYY:

BYE sip:700@XXXXXXXXXXXXXXX:5060 SIP/2.0

Via: SIP/2.0/UDP XXXXXXXXXXXXXXX:5060;branch=z9hG4bK779291063;rport=5060

Max-Forwards: 70

Contact: <sip:108@XXXXXXXXXXXXXXX:5060>

To: <sip:700@XXXXXXXXXXXXXXX>;tag=c21fc118

From: "Hussain Rasheed" <sip:108@XXXXXXXXXXXXXXX>;tag=1257251752

Call-ID: YYYYYYYYY

CSeq: 112 BYE

Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE

Supported: replaces, path, timer

User-Agent: Grandstream GXP2135 1.0.9.135 000b82d0c324

Content-Length: 0



12/05/2019 12:40:17 PM - L:1.1[Extn:108] Sending: OnSendResp Send 200/BYE from 0.0.0.0:0 tid=779291063 Call-ID=YYYYYYYYY:

SIP/2.0 200 OK

Via: SIP/2.0/UDP XXXXXXXXXXXXXXX:5060;branch=z9hG4bK779291063;rport=5060

Contact: <sip:700@XXXXXXXXXXXXXXX:5060>

To: <sip:700@XXXXXXXXXX>;tag=c21fc118

From: "XXXXXXXXXX" <sip:108@XXXXXXXXX>;tag=1257251752

Call-ID: YYYYYYYYY

CSeq: 112 BYE

Content-Length: 0



12/05/2019 12:40:17 PM - Call(C:1), Extn:108 on exit: DlgInfo(1-3762/Terminated / I)
12/05/2019 12:40:17 PM - Call(C:1), Extn:108 on entry: DlgInfo(1-3762/Confirmed / I)
12/05/2019 12:40:17 PM - Notify dialog-info: Extn:108: sip:108@XXXXXXXXXX:5060, Call(C:1)
12/05/2019 12:39:59 PM - Leg L:1.1[Extn:108]: session is confirmed
12/05/2019 12:39:59 PM - Call(C:1), Extn:108 on entry: DlgInfo(1-3762/Confirmed / I)
12/05/2019 12:39:59 PM - Notify dialog-info: Extn:108: sip:108@XXXXXXXXXX:5060, Call(C:1)
12/05/2019 12:39:59 PM - L:1.1[Extn:108] got Confirmed Recv Req ACK from XXXXXXXXXXX:5060 tid=514077122 Call-ID=YYYYYYYYY:

ACK sip:700@XXXXXXXXXXXX:5060 SIP/2.0

Via: SIP/2.0/UDP XXXXXXXXXXXXX:5060;branch=z9hG4bK514077122;rport=5060

Max-Forwards: 70

Contact: <sip:108@XXXXXXXXXXX:5060>

To: <sip:700@XXXXXXXXXXXX>;tag=c21fc118

From: "XXXXXXXXXXXXX" <sip:108@XXXXXXXXXXX>;tag=1257251752

Call-ID: YYYYYYYYY

CSeq: 111 ACK

Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE, MESSAGE

Proxy-Authorization: Digest username="XXXXXXXXXXXXXXX", realm="3CXPhoneSystem", nonce="XXXXXXXXXXXXXXXXXX", uri="sip:700@XXXXXXXXXXXXXX", response="XXXXXXXXXXX", algorithm=MD5

Supported: replaces, path, timer

User-Agent: Grandstream GXP2135 1.0.9.135 000b82d0c324

Content-Length: 0


I enabled verbose logging and made a call to 700 and dialed a conference ID. I got the same "invalid pin number". Above is the resultant log. Please let me know if i am missing anything
 
ok. I tried to do more tests, however i couldnt this time. Provisioned or not.

Earlier I had added a extra IP address of a different subnet to the 3cx server because i was doing another test on phones of that subnet. (the phones i used to test conference were on the same subnet as the 3cx server). I removed that IP and restarted the phones (provisioned) and the server and now everything is working fine :) . Thank you all who commented.
 
I'm glad to hear it was resolved
 
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
111,934
Messages
589,822
Members
164,813
Latest member
divdigital