I think (or thought) that the physical HOLD button was used for HOLD
(not music on hold) with polycom, and that by configuring rfc2543 for
HOLD that HOLD button would then use RFC2543 hold at the phone.
Whether is uses 0.0.0.0 or the phone's IP address I don't know,
because we almost never use the HOLD button these days. We transfer or
park calls, and while we do so, MOH is activated which is light years
beyond rfc2543. The result should be silence or a periodic BEEP with
the phone. The proxy log won't help, because it shows the IP of the
phone. If you use the HOLD button you should get silence or beep and
be able to resume the call.

RFC2543 is an ancient bastard that should have died years ago. I can
only gather you are working with cisco gear somewhere up the line, and
they are stuck in the analog world. In order to use the HOLD button on
a polycom with sipx, you do not need to use rf2543, because (unless
you are using stuff that was EOL many years ago) sipx provides MOH
(even personal MOH) for users for hold, as well as systemwide MOH and
call park MOH.

Why don't you explain what it is you are trying to do instead?

On Wed, Jun 22, 2011 at 5:22 AM, Joegen Baclor <[email protected]> wrote:
> You have configured moh in the polycom.  As I've said in another mail, 2543
> hold is cont compatible with MoH.  My bet is Polycom ignores this flag if
> MoH is set.   Tony?
>
> On 06/22/2011 05:17 PM, Kumaran wrote:
>
> Hi Tony,
>      Please check my SipXproxy.log.By default,it will unchecked in
> Devices->Phones->Sip.So enabled it to check the SDP part whether its
> reflecting  or not.But I never I find c=0.0.0.0 in SDP part after putting on
> HOLD.Its only showing IP address of the phone.
>
> Regards,
> Kumaran T
>
> Tony Graziano wrote:
>
> all.
>
> SIP>protocol
>
> useRFC2543hold         (Default: unchecked)
>
> If checked, use the obsolete c=0.0.0.0 RFC2543 technique, otherwise,
> use SDP media direction attributes (such as a=sendonly) per RFC 3264
> when initiating hold. In either case, the phone processes incoming
> hold signaling in either format.
>
> However that is simply the interaction of the hold button, and I don't
> think it substitutes the MOH uri for services within sipx, etc.
>
> On Wed, Jun 22, 2011 at 4:58 AM, Kumaran
> <[email protected]> wrote:
>
>
> Hi All,
>    What are the Polycom models supports RFC 2543 Hold?
>
> Regards,
> Kumaran T
>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
>
>
>
>
>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>
> _______________________________________________
> sipx-dev mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
>



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.326.5325

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]

Helpdesk Contract Customers:
http://support.myitdepartment.net
Blog:
http://blog.myitdepartment.net

Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to