Yes,Joegen your right

Joegen Baclor wrote:
> In the Enabled one the following is true?
>
> SRT Enabled:   True
> Offer SRTP:   True
> Require SRTP:  False
>
> There are three params.  Just trying to make sure we are in sync.
>
> On 06/16/2011 05:08 PM, Kumaran wrote:
>>
>>  Yes.200 is SRTP enabled phone and 201 is STRP disabled phone..So if 
>> I call  either way there will no SRTP part.If I call 100 from 200 
>> means SRTP part will be present..
>>
>> Joegen Baclor wrote:
>>> So you are saying Offer SRTP doesn not mean what it says?  Phones do 
>>> not offer SRTP with this set?
>>>
>>> On 06/16/2011 04:57 PM, Kumaran wrote:
>>>> Hi Joegen,
>>>>      Just now found out,if Require SRTP is disabled,Both the 
>>>> scenario is
>>>> working but the call will not contain SRTP part...either way from 
>>>> 200 or 201
>>>>
>>>> Regards,
>>>> Kumaran T
>>>>
>>>>
>>>> Joegen Baclor wrote:
>>>>> If you set on Offer SRTP and not Require SRTP, does scenario 1 and 
>>>>> 3 work?
>>>>>
>>>>> On 06/16/2011 02:23 PM, Kumaran wrote:
>>>>>> Hi All,
>>>>>>       I'm testing SRTP for 4.4 in the 13th June build.George had
>>>>>> attached a new Polycom file " phone.xml and phone.properties in Jira
>>>>>> (XX-9675)<http://track.sipfoundry.org/browse/XX-9675>which I have
>>>>>> replaced these files in /etc/sipxpbx/polycom..After replacing I
>>>>>> enabled the following option Enable SRTP
>>>>>> Offer SRTP
>>>>>> Require SRTP
>>>>>> AES_CM_128_HMAC_SHA1_32 for phones to enable SRTP function..Then
>>>>>> after enabling STRP in one phone  I'm finding 2 different
>>>>>> scenario(1&3)....
>>>>>>
>>>>>> Scenario:
>>>>>>   2 users 200 and 201
>>>>>> 200=Polycom 550 =0004f21ed193
>>>>>> 201=Polycom 550= 0004f21ebe81
>>>>>> I tested in following Order.So I if any trying maintain the same 
>>>>>> order
>>>>>>   Scenario:1         1.200 user -Polycom 550 -SRTP Enabled
>>>>>>       2.201 user -Polycom 550 -No SRTP Enabled
>>>>>>       3.Call 201 from 200 --Call is going to user 201.SRTP is 
>>>>>> working
>>>>>> Fine...Lock symbol is present in both the phone and
>>>>>> AES_CM_128_HMAC_SHA1_32 line is present in the SDP part
>>>>>>       4.Call 200 from 201----Call going to IVR(Owner of the EXT 
>>>>>> 200 is
>>>>>> not available)
>>>>>>   Scenario:2
>>>>>>       1.200 user -Polycom 550-SRTP Enabled
>>>>>>       2.201 user -Polycom 550-SRTP Enabled
>>>>>>       3.Call 201 from 200 --Call is going to user 201.SRTP is 
>>>>>> working
>>>>>> Fine...Lock symbol is present in both the phone and
>>>>>> AES_CM_128_HMAC_SHA1_32 line is present in the SDP part
>>>>>>       4.Call 200 from 201--Call is going to user 200.SRTP is working
>>>>>> Fine...Lock symbol is present in both the phone and
>>>>>> AES_CM_128_HMAC_SHA1_32 line is present in the SDP part
>>>>>>   Scenario:3
>>>>>>       1.200 user -Polycom 550 -SRTP Enabled
>>>>>>       2.201 user -Polycom 550 -No SRTP Enabled
>>>>>>       3.Call either way from 200 to 201 or 201 to 200 ---Call is 
>>>>>> going
>>>>>> to IVR.
>>>>>>
>>>>>> I had attached MAC-sipx-sip.cfg for above three scenario.There is
>>>>>> difference in MAC-sipx-sip.cfg for first and third scenario for 201
>>>>>> user phone(which having same setting for both the scenario)in SRTP
>>>>>> part.The same behavior is seen to other user also if we try in above
>>>>>> order...
>>>>>>
>>>>>> Regards,
>>>>>> Venkateshwaran 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/
>>>>
>>
>>

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to