[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Network Conference feature
Author Message
Sur Offline
Junior Member
**

Posts: 9
Joined: Aug 2017
Reputation: 0
Post: #1
Network Conference feature
Hi All,

We use "Network Conference" feature and our "Conference URI" is "conference@sipserver". When user presses Conf button there are INVITE from initator's phone to "conference@sipserver" and 2 REFERs with "Refer-To: sip:sipserver:5060".
My question is: is that OK with REFER, why not "Refer-To: sip:conference@sipserver:5060"?
08-21-2017 06:09 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Johnson_Yealink Offline
Administrator
*******

Posts: 65
Joined: Apr 2017
Reputation: 0
Post: #2
RE: Network Conference feature
Dear Customer,

This is Johnson from Yealink technical support team.Nice to work with you.
For this issue, can you tell me how do you execute network conference?
On the one way:
1.You setting a DSS key as conference, and value as conference@sipserver.
2.Press this DSS key start network conference.

SIP info:
INVITE sip:conf@10.2.1.98:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.10.71:5060;branch=z9hG4bK2917570814
From: "6009" <sip:6009@10.2.1.98:5060>;tag=4014128300
To: <sip:conf@10.2.1.98:5060>
Call-ID: 1_3294377885@10.2.10.71
CSeq: 1 INVITE
Contact: <sip:6009@10.2.10.71:5060>
Content-Type: application/sdp
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T46S 66.81.0.110
Allow-Events: talk,hold,conference,refer,check-sync
Supported: replaces
Content-Length: 302


On the other way:
1.You setting conference type and conference URI via web interface,
path is Account--Advance.
2.A call B
3.A Press conference soft key, B become hold.
4.A call C, C answer this call.
5.A press conference soft key to start conference.

SIP info:
b~REFER sip:6008@10.2.1.98:5060 SIP/2.0
Via: SIP/2.0/UDP 10.2.10.71:5060;branch=z9hG4bK2290756628
From: "6009" <sip:6009@10.2.1.98:5060>;tag=2205038829
To: <sip:6008@10.2.1.98:5060>;tag=as693bc368
Call-ID: 1_2907206645@10.2.10.71
CSeq: 3 REFER
Contact: <sip:6009@10.2.10.71:5060>
Authorization: Digest username="6009", realm="asterisk", nonce="61daa26d", uri="sip:6008@10.2.1.98:5060", response="d9598836b961818fc4b800edc7e5e03b", algorithm=MD5
Max-Forwards: 70
User-Agent: Yealink SIP-T46S 66.81.0.110
Refer-To: <sip:conf@10.2.1.98:5060>
Event: refer
Referred-By: "6009" <sip:6009@10.2.1.98:5060>
Content-Length: 0


I have trying test two ways network conference.
Both two ways SIP info format are conference@sipsvr as below.

Therefore, I advise you send the trace file for us.


BR
Johnon
08-24-2017 10:13 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Sur Offline
Junior Member
**

Posts: 9
Joined: Aug 2017
Reputation: 0
Post: #3
RE: Network Conference feature
Thanks for your reply!

We use second scenario(set conference type and conference URI via web interface and use soft key Conf during call).

It looks very strange for me because I've checked trouble on the same model and with the same fimware as Yours.


SIP info:
REFER sip:10.99.33.26:5060 SIP/2.0
Via: SIP/2.0/UDP 10.199.143.166:5060;branch=z9hG4bK398902729
From: <sip:001565F2E5A1@10.99.33.26>;tag=3983360809
To: <sip:0981842@10.99.33.26>;tag=310cf996-bbc6-40e4-b5a5-73f0c7362e7e
Call-ID: 0_531687440@10.199.143.166
CSeq: 4 REFER
Contact: <sip:001565F2E5A1@10.199.143.166:5060>
Authorization: Digest username="001565F2E5A1", realm="asterisk", nonce="1503573644/05242da91312d904eec0734d654ac004", uri="sip:10.99.33.26:5060", response="2b7f9fef87b301225e5dad0e6ed2465f", algorithm=MD5, cnonce="0a4f113b", opaque="67a041382aed59a6", qop=auth, nc=00000003
Max-Forwards: 70
User-Agent: Yealink SIP-T46S 66.81.0.110
Refer-To: <sip:10.99.33.26:5060>
Event: refer
Referred-By: <sip:001565F2E5A1@10.99.33.26:5060>
Content-Length: 0

I made "Reset to factory" on Yealink T19 E2 with firmware 53.81.0.110, changed only account, SIPserver, Conference Type and Conference URI, and I have the same behavior as I've described.
(This post was last modified: 08-24-2017 02:28 PM by Sur.)
08-24-2017 11:41 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Johnson_Yealink Offline
Administrator
*******

Posts: 65
Joined: Apr 2017
Reputation: 0
Post: #4
RE: Network Conference feature
Dear Customer,

For this issue,I will double check some information with you.
1.Server IP address :10.99.33.26 ?
2.This network conference is working ?
3.Can you tell me your network conference URI ?
4.All the phones have setting conference type and conference URI ?
5.This issue is always can reproduce?
6.Would you please provide trace file/config.bin/level 6 log for us?
Please refer to below FAQ.
http://support.yealink.com/faq/faqInfo?id=313

If you can provide below issue data, will push this issue to fixed.

BR
Johnson
08-25-2017 01:23 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Sur Offline
Junior Member
**

Posts: 9
Joined: Aug 2017
Reputation: 0
Post: #5
RE: Network Conference feature
Hi Johnson

1.Server IP address is 10.99.33.26.
2.Yes, it's working fine.
3.Conference URI is conference@10.99.33.26.
4.On two phones yes, but third phone is softphone.
5.Yes, shure.
6.See attachment


Attached File(s)
.txt  00156593b4d1-sys.txt (Size: 379.17 KB / Downloads: 4)
(This post was last modified: 08-25-2017 02:43 PM by Sur.)
08-25-2017 06:07 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Johnson_Yealink Offline
Administrator
*******

Posts: 65
Joined: Apr 2017
Reputation: 0
Post: #6
RE: Network Conference feature
Dear Customer,

According to the log, I can see two "Refer-To: <sip:10.99.33.26:5060>" SIP info.
Call-ID: 0_2599662701@10.199.140.233
I think this is a transfer action,don't network conference action.
You can see network conference action at Call-ID: 0_3926528422@10.199.140.233.

For more information, please search Call-ID on the log.

Beside, this network conference call can work fine.
I think maybe you don't pay attention to the network conference SIP info.

BR
Johnson
08-28-2017 05:02 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Sur Offline
Junior Member
**

Posts: 9
Joined: Aug 2017
Reputation: 0
Post: #7
RE: Network Conference feature
Hi!

No, it isn't transfer action.

In the scenario:

1.You setting conference type and conference URI via web interface,
path is Account--Advance.
2.A call B
3.A Press conference soft key, B become hold.
4.A call C, C answer this call.
5.A press conference soft key to start conference.

After step 5 phone A sends INVITE to conference's URI (0_3926528422@10.199.140.233) and 2 REFERs
(Call-ID: 0_68574174@10.199.140.233 for call from A to B and Call-ID: 0_2599662701@10.199.140.233 for call from A to C) to move them to conference but the the URI is wrong.

In the example that you have sent before the URI is right - conf@10.2.1.98.
08-28-2017 07:11 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Johnson_Yealink Offline
Administrator
*******

Posts: 65
Joined: Apr 2017
Reputation: 0
Post: #8
RE: Network Conference feature
Dear Customer,

I think we don't need to focus this issue.
Because the correct network conference action as below:
1.Setting a DSS key as conference, and value as conference@sipserver.
2.Press this DSS key start network conference.

BR
Johnson
09-14-2017 07:26 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Sur Offline
Junior Member
**

Posts: 9
Joined: Aug 2017
Reputation: 0
Post: #9
RE: Network Conference feature
Hi Johnson

This feature is very useful for T19 phones without keys.
You mean that the network conference feature is broken and won't be fixed?
09-19-2017 11:11 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Sur Offline
Junior Member
**

Posts: 9
Joined: Aug 2017
Reputation: 0
Post: #10
RE: Network Conference feature
Hi Johnson

I've tried to organize conference by DSS key - URI in REFER message is also wrong.
09-20-2017 03:33 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  V84 feature blf.enhanced brourk 4 2,039 10-04-2019 12:32 AM
Last Post: Oregon
  CP960 with SFB protect Basic and Feature settings geislinger 2 1,497 08-12-2019 01:15 PM
Last Post: geislinger
  Network Conference on Shared Line JasonTricom 0 946 04-16-2019 09:06 PM
Last Post: JasonTricom
  Which RFC describes as-feature-event event package ? oliv 3 3,338 01-16-2019 04:45 PM
Last Post: jolouis
  How to disable the Dial-Upon-Lift feature Jeremy17 1 2,654 12-11-2017 01:33 AM
Last Post: Evan_Yealink
  T29G Conference Button Becomes Inactive gyegavian 3 4,502 06-22-2017 07:45 AM
Last Post: Jensen_Yealink
  T46G and conference microphones DomBlom 1 3,686 09-19-2016 02:32 PM
Last Post: Karl_Yealink
  T38 Wont Connect To New Network zachtate 2 4,148 05-09-2016 09:18 AM
Last Post: zachtate
  Autoanswer on click to dial feature Walter 8 15,418 05-04-2016 05:42 AM
Last Post: jmoore
  How can I capture the network traffic of the phone remotely? celtic66 1 3,315 04-27-2016 05:58 PM
Last Post: Karl_Yealink

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication