• ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Windows update impacting certain printer icons and names. Microsoft is working on a solution.
    Click here to learn more
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
The HP Community is where owners of HP products, like you, volunteer to help each other find solutions.
Locked

‎08-21-2012 07:56 AM

HP Recommended

Hi all.

I'm struggling with this query....

We have 7 of the IP600 which are all having the same problem.
 
When we go off and dial the first number, whether it be 9 for a external line or an internal number the call connects ok, but once connected there are no DTMF's from the unit. We have other sip device's which are all using the pbx's dtmf correctly so it is a Polycom issue.
 
I have a manual which has instructions on how to change the dtmf but the area in which this is configured isn't on the web interface.
 
 
The current version it is on is :
Sip Software version 3.3.3.0069
BootROM version 4.3.1.0887

 

Any thoughts SB etc....

1 ACCEPTED SOLUTION

Accepted Solutions

‎08-21-2012 08:27 AM

HP Recommended

Hello Pete,

 

Oct 7, 2011 Question: Phone unable to send DTMF to an IVR system

Resolution: Please check => here <=

 

Your other phones may use an older Software that uses Pauyload 101 but sometime in SIP 3.2.x we changed to Payload 127

 

This change cannot be made via the Web interface.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

View solution in original post

Was this reply helpful? Yes No
17 REPLIES 17

‎08-21-2012 08:27 AM

HP Recommended

Hello Pete,

 

Oct 7, 2011 Question: Phone unable to send DTMF to an IVR system

Resolution: Please check => here <=

 

Your other phones may use an older Software that uses Pauyload 101 but sometime in SIP 3.2.x we changed to Payload 127

 

This change cannot be made via the Web interface.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Was this reply helpful? Yes No

‎08-21-2012 08:49 AM

HP Recommended

Thanks SB.

I did do a little PDF surfing & Community surfing, but was running out of time.  I knew you'd know.

For my part I'm happy & sorted.  If my caller comes back after doing all that stuff I may offer to eat my hat as I'm 100% certain you are right.

 

Regards

PT

Was this reply helpful? Yes No

‎08-21-2012 09:04 AM

HP Recommended

Hello Pete,

 

only a wireshark trace will show this if compared to another call.

 

Regards

 

Steffen

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Was this reply helpful? Yes No

‎03-14-2013 11:24 AM

HP Recommended

Hi,

 

Suffering similar problems, however setting Payload is not an option as this will impact other devices supported.

 

Can anyone advise how to set 'DTMF to SIP INFO' as a preferred option in our envirnoment?

 

Thanks,

David

Was this reply helpful? Yes No

‎03-14-2013 12:19 PM

HP Recommended

Hello David_Paris,

welcome to the Polycom Community.

I have only the same FAQ reply that I had already provided to Pete originally:

 

Oct 7, 2011 Question: Phone unable to send DTMF to an IVR system

Resolution: Please check => here <=

 

Above post if followed up contains the SIP Info Example. You may need to liaise with your SIP provider.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Was this reply helpful? Yes No

‎12-07-2013 10:00 PM

HP Recommended

Hello 

i am facesing same issue pls help 

 

polycom debug

 

1208102200|sip |0|03|<<<Packet Received
1208102200|sip |0|03| SIP/2.0 407 Proxy Authentication Required
1208102200|sip |0|03| Via: SIP/2.0/UDP 172.16.1117.28:5060;branch=z9hG4bKf3562b8342F1B626;rport=1418
1208102200|sip |0|03| From: "1111" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102200|sip |0|03| To: <sip:1111@revenuemed.voipwell.com;user=phone>;tag=be67608d3s
1208102200|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102200|sip |0|03| CSeq: 1 INVITE
1208102200|sip |0|03| Server: Brekeke SIP Server
1208102200|sip |0|03| Proxy-Authenticate: Digest realm="TEST-PC",nonce="5bcb54f16ba85c59f80a1ed3424b2cdb72ede752",algorithm=MD5
1208102200|sip |0|03| Content-Length: 0
1208102200|sip |0|03|
1208102200|sip |0|03|>>> Data Send to 216.24.244.252:5060
1208102200|sip |0|03| ACK sip:9111117@revenuemed.voipwell.com;user=phone SIP/2.0
1208102200|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bKf3562b8342F1B626
1208102200|sip |0|03| From: "11111" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102200|sip |0|03| To: <sip:911115167@revenuemed.voipwell.com;user=phone>;tag=be67608d3s
1208102200|sip |0|03| CSeq: 1 ACK
1208102200|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102200|sip |0|03| Contact: <sip:160@172.16.127.28:5060>
1208102200|sip |0|03| Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
1208102200|sip |0|03| User-Agent: PolycomSoundStationIP-SSIP_5000-UA/4.1.0.84959
1208102200|sip |0|03| Accept-Language: en
1208102200|sip |0|03| Max-Forwards: 70
1208102200|sip |0|03| Content-Length: 0
1208102200|sip |0|03|
1208102200|sip |0|03|>>> Data Send to 216.24.244.252:5060
1208102200|sip |0|03| INVITE sip:918667475167@revenuemed.voipwell.com;user=phone SIP/2.0
1208102200|sip |0|03| Via: SIP/2.0/UDP 171.16.117.28:5060;branch=z9hG4bK39febe2CA573ADD
1208102200|sip |0|03| From: "7111111" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102200|sip |0|03| To: <sip:9111117@revenuemed.voipwell.com;user=phone>
1208102200|sip |0|03| CSeq: 2 INVITE
1208102200|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102200|sip |0|03| Contact: <sip:160@172.16.127.28:5060>
1208102200|sip |0|03| Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
1208102200|sip |0|03| User-Agent: PolycomSoundStationIP-SSIP_5000-UA/4.1.0.84959
1208102200|sip |0|03| Accept-Language: en
1208102200|sip |0|03| Supported: 100rel,replaces
1208102200|sip |0|03| Allow-Events: conference,talk,hold
1208102200|sip |0|03| Proxy-Authorization: Digest username="160", realm="TEST-PC", nonce="5bcb54f16ba85c59f80a1ed3424b2cdb72ede752", uri="sip:918667475167@revenuemed.voipwell.com;user=phone", response="d69e6846278438b9aab3019e10e73941", algorithm=MD5
1208102200|sip |0|03| Max-Forwards: 70
1208102200|sip |0|03| Content-Type: application/sdp
1208102200|sip |0|03| Content-Length: 284
1208102200|sip |0|03|
1208102200|sip |0|03| v=0
1208102200|sip |0|03| o=- 1386478320 1386478320 IN IP4 172.16.127.28
1208102200|sip |0|03| s=Polycom IP Phone
1208102200|sip |0|03| c=IN IP4 172.16.127.28
1208102200|sip |0|03| t=0 0
1208102200|sip |0|03| m=audio 2234 RTP/AVP 9 0 8 18 101
1208102200|sip |0|03| a=rtpmap:9 G722/8000
1208102200|sip |0|03| a=rtpmap:0 PCMU/8000
1208102200|sip |0|03| a=rtpmap:8 PCMA/8000
1208102200|sip |0|03| a=rtpmap:18 G729/8000
1208102200|sip |0|03| a=fmtp:18 annexb=no
1208102200|sip |0|03| a=rtpmap:101 telephone-event/8000
1208102200|sip |0|03|<<<Packet Received
1208102200|sip |0|03| SIP/2.0 100 Trying
1208102200|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bK39febe2CA573ADD;rport=1418
1208102200|sip |0|03| From: "7702469797" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102200|sip |0|03| To: <sip:918667475167@revenuemed.voipwell.com;user=phone>
1208102200|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102200|sip |0|03| CSeq: 2 INVITE
1208102200|sip |0|03| Server: Brekeke SIP Server
1208102200|sip |0|03| Content-Length: 0
1208102200|sip |0|03|
1208102203|sip |0|03|<<<Packet Received
1208102203|sip |0|03| SIP/2.0 183 Session Progress
1208102203|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bK39febe2CA573ADD;rport=1418
1208102203|sip |0|03| Record-Route: <sip:216.24.244.252:5060;lr>
1208102203|sip |0|03| From: "7711111797" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102203|sip |0|03| To: <sip:911111117475167@revenuemed.voipwell.com;user=phone>;tag=b9b1605fdp
1208102203|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102203|sip |0|03| CSeq: 2 INVITE
1208102203|sip |0|03| Contact: <sip:918667475167@216.24.244.252:5060>
1208102203|sip |0|03| Require: 100rel
1208102203|sip |0|03| RSeq: 1
1208102203|sip |0|03| Content-Type: application/sdp
1208102203|sip |0|03| Content-Length: 218
1208102203|sip |0|03|
1208102203|sip |0|03| v=0
1208102203|sip |0|03| o=REVENUEMEDPRIMA$ 1443 2 IN IP4 216.24.244.252
1208102203|sip |0|03| s=-
1208102203|sip |0|03| c=IN IP4 216.24.244.252
1208102203|sip |0|03| t=0 0
1208102203|sip |0|03| m=audio 10552 RTP/AVP 0 101
1208102203|sip |0|03| a=sendrecv
1208102203|sip |0|03| a=rtpmap:0 PCMU/8000
1208102203|sip |0|03| a=ptime:20
1208102203|sip |0|03| a=rtpmap:101 telephone-event/8000
1208102203|sip |0|03| a=fmtp:101 0-16
1208102203|sip |0|03|>>> Data Send to 216.24.244.252:5060
1208102203|sip |0|03| PRACK sip:911111167@216.24.244.252:5060 SIP/2.0
1208102203|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bK62fbf91eA59B8F79
1208102203|sip |0|03| From: "71161197" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102203|sip |0|03| To: <sip:911111475167@revenuemed.voipwell.com;user=phone>;tag=b9b1605fdp
1208102203|sip |0|03| Route: <sip:216.24.244.252:5060;lr>
1208102203|sip |0|03| CSeq: 3 PRACK
1208102203|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102203|sip |0|03| Contact: <sip:160@172.16.127.28:5060>
1208102203|sip |0|03| User-Agent: PolycomSoundStationIP-SSIP_5000-UA/4.1.0.84959
1208102203|sip |0|03| Accept-Language: en
1208102203|sip |0|03| RAck: 1 2 INVITE
1208102203|sip |0|03| Proxy-Authorization: Digest username="160", realm="TEST-PC", nonce="5bcb54f16ba85c59f80a1ed3424b2cdb72ede752", uri="sip:918667475167@revenuemed.voipwell.com;user=phone", response="657488c53cdcedcd8538c5e1ff639f1c", algorithm=MD5
1208102203|sip |0|03| Max-Forwards: 70
1208102203|sip |0|03| Content-Length: 0
1208102203|sip |0|03|
1208102203|sip |0|03|<<<Packet Received
1208102203|sip |0|03| SIP/2.0 200 OK
1208102203|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bK62fbf91eA59B8F79;rport=1418
1208102203|sip |0|03| Record-Route: <sip:216.24.244.252:5060;lr>
1208102203|sip |0|03| From: "7702469797" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102203|sip |0|03| To: <sip:918667475167@revenuemed.voipwell.com;user=phone>;tag=b9b1605fdp
1208102203|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102203|sip |0|03| CSeq: 3 PRACK
1208102203|sip |0|03| Content-Length: 0
1208102203|sip |0|03|
1208102203|sip |0|03|<<<Packet Received
1208102203|sip |0|03| SIP/2.0 200 OK
1208102203|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bK39febe2CA573ADD;rport=1418
1208102203|sip |0|03| Record-Route: <sip:216.24.244.252:5060;lr>
1208102203|sip |0|03| From: "7702469797" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102203|sip |0|03| To: <sip:918667475167@revenuemed.voipwell.com;user=phone>;tag=b9b1605fdp
1208102203|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102203|sip |0|03| CSeq: 2 INVITE
1208102203|sip |0|03| Contact: <sip:918667475167@216.24.244.252:5060>
1208102203|sip |0|03| Allow: INVITE,ACK,BYE,CANCEL,INFO,MESSAGE,REFER,NOTIFY,SUBSCRIBE,UPDATE,PRACK
1208102203|sip |0|03| Content-Type: application/sdp
1208102203|sip |0|03| Content-Length: 218
1208102203|sip |0|03|
1208102203|sip |0|03| v=0
1208102203|sip |0|03| o=REVENUEMEDPRIMA$ 1443 2 IN IP4 216.24.244.252
1208102203|sip |0|03| s=-
1208102203|sip |0|03| c=IN IP4 216.24.244.252
1208102203|sip |0|03| t=0 0
1208102203|sip |0|03| m=audio 10552 RTP/AVP 0 101
1208102203|sip |0|03| a=sendrecv
1208102203|sip |0|03| a=rtpmap:0 PCMU/8000
1208102203|sip |0|03| a=ptime:20
1208102203|sip |0|03| a=rtpmap:101 telephone-event/8000
1208102203|sip |0|03| a=fmtp:101 0-16
1208102203|sip |0|03|>>> Data Send to 216.24.244.252:5060
1208102203|sip |0|03| ACK sip:918667475167@216.24.244.252:5060 SIP/2.0
1208102203|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bKea66f8c1438AA17
1208102203|sip |0|03| From: "7702469797" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102203|sip |0|03| To: <sip:918667475167@revenuemed.voipwell.com;user=phone>;tag=b9b1605fdp
1208102203|sip |0|03| Route: <sip:216.24.244.252:5060;lr>
1208102203|sip |0|03| CSeq: 2 ACK
1208102203|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102203|sip |0|03| Contact: <sip:160@172.16.127.28:5060>
1208102203|sip |0|03| Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
1208102203|sip |0|03| User-Agent: PolycomSoundStationIP-SSIP_5000-UA/4.1.0.84959
1208102203|sip |0|03| Accept-Language: en
1208102203|sip |0|03| Max-Forwards: 70
1208102203|sip |0|03| Content-Length: 0
1208102203|sip |0|03|
1208102226|sip |0|03|>>> Data Send to 216.24.244.252:5060
1208102226|sip |0|03| BYE sip:918667475167@216.24.244.252:5060 SIP/2.0
1208102226|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bK32a4cdda98C29795
1208102226|sip |0|03| From: "7702469797" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102226|sip |0|03| To: <sip:918667475167@revenuemed.voipwell.com;user=phone>;tag=b9b1605fdp
1208102226|sip |0|03| Route: <sip:216.24.244.252:5060;lr>
1208102226|sip |0|03| CSeq: 4 BYE
1208102226|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102226|sip |0|03| Contact: <sip:160@172.16.127.28:5060>
1208102226|sip |0|03| User-Agent: PolycomSoundStationIP-SSIP_5000-UA/4.1.0.84959
1208102226|sip |0|03| Accept-Language: en
1208102226|sip |0|03| Proxy-Authorization: Digest username="160", realm="TEST-PC", nonce="5bcb54f16ba85c59f80a1ed3424b2cdb72ede752", uri="sip:918667475167@revenuemed.voipwell.com;user=phone", response="d992aa12fa62da528a15de4a0b185bc3", algorithm=MD5
1208102226|sip |0|03| Max-Forwards: 70
1208102226|sip |0|03| Content-Length: 0
1208102226|sip |0|03|
1208102227|sip |0|03|<<<Packet Received
1208102227|sip |0|03| SIP/2.0 200 OK
1208102227|sip |0|03| Via: SIP/2.0/UDP 172.16.127.28:5060;branch=z9hG4bK32a4cdda98C29795;rport=1418
1208102227|sip |0|03| Record-Route: <sip:216.24.244.252:5060;lr>
1208102227|sip |0|03| From: "7702469797" <sip:160@revenuemed.voipwell.com>;tag=4A92EC25-6F719518
1208102227|sip |0|03| To: <sip:918667475167@revenuemed.voipwell.com;user=phone>;tag=b9b1605fdp
1208102227|sip |0|03| Call-ID: a2a929c1-c0959914-2183e4df@172.16.127.28
1208102227|sip |0|03| CSeq: 4 BYE
1208102227|sip |0|03| Content-Length: 0
1208102227|sip |0|03|

 

Was this reply helpful? Yes No

‎12-08-2013 04:51 AM

HP Recommended

Hello Mahesh_telemedia,

welcome to the Polycom Community.

Did you check the previous two replies I had given the other users as so far you have not stated what your individual issues is.

 

  • Petet, who originally started this post, had a Payload type issue and after receiving my reply marked the post as solution provided.

  • David, who followed up on this post, had a SIP info method query which is different to the payload type.

Both of their questions had been answered by the FAQ post I linked into my reply.

 

You posted a log from a SIP call which provides all of us with the details that you are using an SSIP5000 running UCS 4.1.0 (which is actually a LYNC release) and are using Payload type 101.

 

Could you be so kind and state what your actual issue is and maybe read the FAQ post so solve it?


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Was this reply helpful? Yes No

‎12-13-2013 06:02 AM

HP Recommended

Digital tone is not working.How to send call in Send in-band

 

Was this reply helpful? Yes No

‎12-13-2013 06:56 AM

HP Recommended

Hello Mahesh_telemedia,

 

as already mentioned did you check the older replies and the FAQ post?

 

Oct 7, 2011 Question: Phone unable to send DTMF to an IVR system or how to troubleshoot DTMF issues

Resolution: Please check => here <=

 

 

Your log shows

 a=rtpmap:101 telephone-event/8000

 Above means you are sending a Payload type of 101. 

 

The FAQ post explains how to change this and has exmaples attached.

 

Please change this to the needed payload type.

 

If you are unable to do so please work with your Polycom reseller as your support contact.

 

Best regards

 

Steffen Baier

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Was this reply helpful? Yes No
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.

Didn't find what you were looking for? Ask the community

† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.