Send discussion mailing list submissions to
discussion sipforum.org
To subscribe or unsubscribe via the World Wide Web, visit
http:
//sipforum.org/mailman/listinfo/discussion
or, via email, send a message with subject or body 'help'
to
discussion-requestsipforum.org
You can reach the person managing the list at
discussion-ownersipforum.org
When replying, please edit your Subject line so it is more
specific
than "Re: Contents of discussion digest..."
Today's Topics:
1. please include me in discussion list (Anand Upadye)
2. Re: A question on SIP Registration Interval (Andrew
Yu)
3. Re: A question on SIP Registration Interval (Andrew
Yu)
4. audio packet loss (toothhe)
5. Query about IP Security (Yogesh Agrawal)
------------------------------------------------------------
----------
Message: 1
Date: Thu, 14 Jun 2007 10:21:46 +0530
From: "Anand Upadye" <anand.upadyegmail.com>
Subject: [SIPForum-discussion] please include me in
discussion list
To: discussionsipforum.org
Message-ID:
<fb8d7df0706132151v310b40cci5c6dd8eb7de7ff37mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
HI,
I am Anand Upadye working at Kodiak Networks, I am very much
interested in
these discussions pleae include me.
thanks
Anand.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/p
ipermail/discussion/attachments/20070614/30273181/attachment
-0001.html
------------------------------
Message: 2
Date: Thu, 14 Jun 2007 14:22:57 +0800
From: Andrew Yu <andrewasiatel.com.sg>
Subject: Re: [SIPForum-discussion] A question on SIP
Registration
Interval
To: Onur Cinar <onur.cinargmail.com>, vijay
sukrishnaan nair
<vijay_sukrishnaannairyahoo.com>
Cc: discussionsipforum.org
Message-ID: <4670DEC1.90604asiatel.com.sg>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Vijay & Onur,
My appreciation for your kind response.
Dear Members,
Actually, I'm facing a problem where the sbc reduces the
requested
expiration interval by 1sec until the UA expiration interval
reaches 1
and deregister itself at expiration interval at 0. The
problem surfaced
after a software upgrade was done on the sbc, the vendor
insist that
there was nothing wrong and the UA should re-register itself
based on
the configured re-register expiration interval of the UA. Am
I
misunderstanding something? The weirdest thing is that this
does not
affect linksys devices like PAP2. They just re-register
itself at its
own pre-configured value.
My appreciation if any nextone & cisco/linksys trained
engineers could
response to my questions. The sbc is from nextone. Thanks
alot!
User Datagram Protocol, Src Port: 5698 (5698), Dst Port:
5060 (5060)
Session Initiation Protocol
Request-Line: REGISTER sip:sip.abc.com SIP/2.0
Method: REGISTER
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
10.0.0.130:5698;branch=z9hG4bK0a0000825698-1470;rport
From: sip:12345678sip.abc.com;tag=0A0000821642-805261B80
To: sip:12345678sip.abc.com
Call-ID: 1805261b82954a000082
CSeq: 72 REGISTER
User-Agent: SIP-6328-2Re-v8.0.3-12345678/v2.0
Enabled
Contact: "12345678"<sip:1234567810.0.0.130:5698>
Expires: 2
Max-Forwards: 70
Content-Length: 0
User Datagram Protocol, Src Port: 5060 (5060), Dst Port:
5698 (5698)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP
10.0.0.130:5698;received=210.24.99.168;branch=z9hG4bK0a00008
25698-1470;rport
From: <sip:12345678sip.abc.com>;tag=0A0000821642-805261B80
To: <sip:12345678sip.abc.com>
Call-ID: 1805261b82954a000082
CSeq: 72 REGISTER
Expires: 1
Contact: "12345678" <sip:6826769110.0.0.130:5698>
Content-Length: 0
--
Cheers,
Asiatel Singapore Pte Ltd
Andrew Yu
19 Jalan Kilang Barat
#06-01, Acetech Centre
Singapore 159361
Tel: +65 6271 8233
Fax: +65 6274 4266
vijay sukrishnaan nair wrote:
> Hi,
>
> If you get expire time as 30 seconds from registrar it
means that
> after 30 seconds you will loose registration. So you
must send
> reregister request within 30 seconds. Yes the UA should
reset the
> expire time depend upon the response. Please discard
this reply if i
> am wrong.
>
Onur Cinar wrote:
>
> Hi Andrew,
>
> Yes, that is the case, your UA should obey the
registrar's decision.
> Based on your example, the registrar will keep your
registration for
> 30 seconds, and then it will clean it from its
database. So for
> example, if your UA receives an INVITE at 45 seconds
then the calling
> party will get a 404 although your UA is still running.
So you should
> register in every 30 seconds instead of 60.
>
> Based on my experience, in your UA, make sure to
register a little
> earlier than 30 seconds. I'm mostly registering 5-10
seconds earlier
> to make sure that my registration won't expire due to
some unexpected
> application side/network delays.
>
> Best regards,
>
> -onur
>
> --
> Visit Nuvoiz.com <http://Nuvoiz.com> for
our SoftPhone Soltutions
> A. Onur Cinar - Senior Software Engineer
> T: 1.408.454.6138 F: 1.408.754.6230
> 1973 Landings Drive, Mountain View, CA 94043 USA
>
> On 6/13/07, *Andrew Yu* <andrewasiatel.com.sg
> <mailto:andrewasiatel.com.sg>> wrote:
>
> Dear members,
>
> I'll like to know exactly how SIP registration
interval is implemented
> by the RFC.
>
> When UA send register request with expires 60 and
registrar return 200
> OK but with expires 30, does this mean the next
re-register sent
> by the
> UA will be sent at expiration interval of 30? What
will happen if I've
> configured the endpoint to re-register every 60s,
does this mean that
> the configured setting will be over-ride by the
registrar? Thank you.
>
> --
> Cheers,
>
> Asiatel Singapore Pte Ltd
> Andrew Yu
>
> 19 Jalan Kilang Barat
> #06-01, Acetech Centre
> Singapore 159361
>
> Tel: +65 6271 8233
> Fax: +65 6274 4266
>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options,
please visit
> http:
//sipforum.org/mailman/listinfo/discussion
> Post to the list at discussionsipforum.org
> <mailto:discussionsipforum.org>
>
>
------------------------------
Message: 3
Date: Thu, 14 Jun 2007 18:04:32 +0800
From: Andrew Yu <andrewasiatel.com.sg>
Subject: Re: [SIPForum-discussion] A question on SIP
Registration
Interval
To: kaushikncoretech.com
Cc: discussionsipforum.org
Message-ID: <467112B0.10709asiatel.com.sg>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi Kaushik,
You're correct to point this out, the UA is carrying the new
expiration
interval set by the registrar everytime it is
re-registering. Is the UA
right to use the value dictated by the registrar or it
should registered
with same "configured" expiration value during
every re-registering? Thanks.
--
Cheers,
Asiatel Singapore Pte Ltd
Andrew Yu
19 Jalan Kilang Barat
#06-01, Acetech Centre
Singapore 159361
Tel: +65 6271 8233
Fax: +65 6274 4266
kaushikncoretech.com wrote:
> Hi Andrew,
>
> I think the problem is related to REGISTER carrying
> new expires value everytime it is Re-Registering.
>
> If you can make device / client register with same
"configured"
> expires value during every Re-Registering then it will
solve
> your problem.
>
> Regards,
> Kaushik
>
> Quoting Andrew Yu <andrewasiatel.com.sg>:
>
>
>> Hi Vijay & Onur,
>>
>> My appreciation for your kind response.
>>
>> Dear Members,
>>
>> Actually, I'm facing a problem where the sbc
reduces the requested
>> expiration interval by 1sec until the UA expiration
interval reaches 1
>> and deregister itself at expiration interval at 0.
The problem surfaced
>> after a software upgrade was done on the sbc, the
vendor insist that
>> there was nothing wrong and the UA should
re-register itself based on
>> the configured re-register expiration interval of
the UA. Am I
>> misunderstanding something? The weirdest thing is
that this does not
>> affect linksys devices like PAP2. They just
re-register itself at its
>> own pre-configured value.
>>
>> My appreciation if any nextone & cisco/linksys
trained engineers could
>> response to my questions. The sbc is from nextone.
Thanks alot!
>>
>> User Datagram Protocol, Src Port: 5698 (5698), Dst
Port: 5060 (5060)
>> Session Initiation Protocol
>> Request-Line: REGISTER sip:sip.abc.com SIP/2.0
>> Method: REGISTER
>> [Resent Packet: False]
>> Message Header
>> Via: SIP/2.0/UDP
>>
10.0.0.130:5698;branch=z9hG4bK0a0000825698-1470;rport
>> From: sip:12345678sip.abc.com;tag=0A0000821642-805261B80
>> To: sip:12345678sip.abc.com
>> Call-ID: 1805261b82954a000082
>> CSeq: 72 REGISTER
>> User-Agent:
SIP-6328-2Re-v8.0.3-12345678/v2.0 Enabled
>> Contact:
"12345678"<sip:1234567810.0.0.130:5698>
>> Expires: 2
>> Max-Forwards: 70
>> Content-Length: 0
>>
>> User Datagram Protocol, Src Port: 5060 (5060), Dst
Port: 5698 (5698)
>> Session Initiation Protocol
>> Status-Line: SIP/2.0 200 OK
>> Status-Code: 200
>> [Resent Packet: False]
>> Message Header
>> Via: SIP/2.0/UDP
>>
10.0.0.130:5698;received=210.24.99.168;branch=z9hG4bK0a00008
25698-1470;rport
>> From: <sip:12345678sip.abc.com>;tag=0A0000821642-805261B80
>> To: <sip:12345678sip.abc.com>
>> Call-ID: 1805261b82954a000082
>> CSeq: 72 REGISTER
>> Expires: 1
>> Contact: "12345678"
<sip:6826769110.0.0.130:5698>
>> Content-Length: 0
>>
>> --
>> Cheers,
>>
>> Asiatel Singapore Pte Ltd
>> Andrew Yu
>>
>> 19 Jalan Kilang Barat
>> #06-01, Acetech Centre
>> Singapore 159361
>>
>> Tel: +65 6271 8233
>> Fax: +65 6274 4266
>>
>>
>> vijay sukrishnaan nair wrote:
>>
>>> Hi,
>>>
>>> If you get expire time as 30 seconds from
registrar it means that
>>> after 30 seconds you will loose registration.
So you must send
>>> reregister request within 30 seconds. Yes the
UA should reset the
>>> expire time depend upon the response. Please
discard this reply if i
>>> am wrong.
>>>
>>>
>> Onur Cinar wrote:
>>
>>> Hi Andrew,
>>>
>>> Yes, that is the case, your UA should obey the
registrar's decision.
>>> Based on your example, the registrar will keep
your registration for
>>> 30 seconds, and then it will clean it from its
database. So for
>>> example, if your UA receives an INVITE at 45
seconds then the calling
>>> party will get a 404 although your UA is still
running. So you should
>>> register in every 30 seconds instead of 60.
>>>
>>> Based on my experience, in your UA, make sure
to register a little
>>> earlier than 30 seconds. I'm mostly registering
5-10 seconds earlier
>>> to make sure that my registration won't expire
due to some unexpected
>>> application side/network delays.
>>>
>>> Best regards,
>>>
>>> -onur
>>>
>>> --
>>> Visit Nuvoiz.com <http://Nuvoiz.com> for
our SoftPhone Soltutions
>>> A. Onur Cinar - Senior Software Engineer
>>> T: 1.408.454.6138 F: 1.408.754.6230
>>> 1973 Landings Drive, Mountain View, CA 94043
USA
>>>
>>> On 6/13/07, *Andrew Yu* <andrewasiatel.com.sg
>>> <mailto:andrewasiatel.com.sg>>
wrote:
>>>
>>> Dear members,
>>>
>>> I'll like to know exactly how SIP
registration interval is implemented
>>> by the RFC.
>>>
>>> When UA send register request with expires
60 and registrar return 200
>>> OK but with expires 30, does this mean the
next re-register sent
>>> by the
>>> UA will be sent at expiration interval of
30? What will happen if I've
>>> configured the endpoint to re-register
every 60s, does this mean that
>>> the configured setting will be over-ride by
the registrar? Thank you.
>>>
>>> --
>>> Cheers,
>>>
>>> Asiatel Singapore Pte Ltd
>>> Andrew Yu
>>>
>>> 19 Jalan Kilang Barat
>>> #06-01, Acetech Centre
>>> Singapore 159361
>>>
>>> Tel: +65 6271 8233
>>> Fax: +65 6274 4266
>>>
>>>
>>>
_______________________________________________
>>> This is the SIP Forum discussion mailing
list
>>> TO UNSUBSCRIBE, or edit your delivery
options, please visit
>>> http:
//sipforum.org/mailman/listinfo/discussion
>>> Post to the list at discussionsipforum.org
>>> <mailto:discussionsipforum.org>
>>>
>>>
>>>
>> _______________________________________________
>> This is the SIP Forum discussion mailing list
>> TO UNSUBSCRIBE, or edit your delivery options,
please visit
>> http:
//sipforum.org/mailman/listinfo/discussion
>> Post to the list at discussionsipforum.org
>>
>>
>
>
>
>
> __________ NOD32 2328 (20070613) Information
__________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
>
>
>
------------------------------
Message: 4
Date: Thu, 14 Jun 2007 18:42:29 +0800 (CST)
From: toothhe <toothhe163.com>
Subject: [SIPForum-discussion] audio packet loss
To: discussionsipforum.org
Message-ID:
<3405835.1534381181817749408.JavaMail.coremailbj163app62.163.com>
Content-Type: text/plain; charset="gbk"
Hi dear all,I'm now doing some workload tests of Asterisk by
the SIPp, and got many lp (lost package) in the Master.csv
log file on Asterisk side.
But when I test with X-Lite, there's no lost package.
I'm puzzled by this result.What does lp in Master.csv file
means? Is there any weakness in SIPp about lossing package,
such as audio package?
Thanks a lot~!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/p
ipermail/discussion/attachments/20070614/40ca46a5/attachment
-0001.html
------------------------------
Message: 5
Date: Thu, 14 Jun 2007 18:12:55 +0530
From: "Yogesh Agrawal" <ayogeshTechMahindra.com>
Subject: [SIPForum-discussion] Query about IP Security
To: <discussionsipforum.org>
Message-ID:
<B27CCEBBCCC2214A9209EEED6C6AE85105DC735DSINMUMEX001.TechMahindra.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
What is the significance of "spi" directive
in the Security
headers?
e.g. Security-Client: digest, IPsec-3gpp
;alg=hmac-sha-l-96;spi-c=23456789
;spi-s=12345678;port-c=2468
;port-s=1357
RFC 3329 says - It defines the SPI number used for inbound
messages
(10DIGIT; 0 to 4294967295)
John Wiley says - the SPI used for the IPsec SA that relates
to the
protected client port (spi-c) as
well as the SPI used for the
IPsec SA that
relates to the protected server port
(spi - s).
Could you please elaborate on its significance ?
Yogesh Agarwal | IMS| Tech Mahindra
9/7,Hosur road,Bangalore-29.
* Office: 91-80-2553 9233| Extn: 1409 |
Cell:9986512707
Email: ayogeshtechmahindra.com
www.techmahindra.com <BLOCKED::http://www.techmahin
dra.com/>
============================================================
============================================================
====
Disclaimer:
This message and the information contained herein is
proprietary and confidential and subject to the Tech
Mahindra policy statement, you may review the policy at
<a href="http:/
/www.techmahindra.com/Disclaimer.html">http://www.te
chmahindra.com/Disclaimer.html</a> externally and
<a href="http:/
/tim.techmahindra.com/Disclaimer.html">http://tim.te
chmahindra.com/Disclaimer.html</a> internally
within Tech Mahindra.
============================================================
============================================================
====
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://sipforum.org/piperm
ail/discussion/attachments/20070614/5055a9cb/attachment.html
------------------------------
_______________________________________________
This is the SIP Forum discussion mailing list
TO UNSUBSCRIBE, or edit your delivery options, please visit
http:
//sipforum.org/mailman/listinfo/discussion
Post to the list at discussionsipforum.org
End of discussion Digest, Vol 23, Issue 18
******************************************
|
