| Author |
|
will
Junior
Joined: February 07 2005
Location: Canada
Posts: 48
|
| Posted: February 17 2005 at 3:55pm | IP Logged
|
|
|
When testing, the application lost registration session after certain period of time, then we changed the
RegistrationIntervalSeconds=300;//set to 5 minutes;
which is one of the paramers of API EnableSipRegisterServer to let the application re-register every 5 minutes, but still lose registration connection after about 30 minuts if the testers don't make calls.
So do you have any idea to solve this problem, or we have to start another thread in the application to do registration in certain intervals.
regards,
will
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: February 18 2005 at 6:07am | IP Logged
|
|
|
Thanks Will for your question.
We are assuming that “lost registration” means that your application had problems registering with your SIP registrar server? We ask that in the future you be as specific as possible with the problem description so we can resolve issues quickly. For example:
Have you generated a SIP protocol log file and examined it for the cause of the problem?
What registrar server are you using?
Is the registration interval being accepted or rejected by the registrar?
Is the registrar enforcing challenge authentication of SIP REGISTER messages?
Where is the registrar server located on the network in proximity to the soft phone having the issues?
Is the registrar server behind a NAT router/firewall?
If you experience problems, the first place to start is to identify if the problem is repeatable. If you think you have identified a problem, you must generate a SIP protocol log file of the SIP transactions and look at it for a possible cause. We do assist customers in reviewing their SIP logs however we can only do this to a limited extent.
Examining the SIP log file will go a long way to revealing to you exactly what is causing the problem. Below is an example of a soft phone that uses the VOIP media engine and registers with our SIP proxy/registrar server:
Registration Cycle – Digest Challenge authentication enforced by the server:
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (0 Ms, To: 192.168.1.2:7000) >>>>
REGISTER sip:lanscapecorp.dnsalias.com:7000 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:10000
From: <sip:rziegler@lanscapecorp.dnsalias.com:10000>;tag=280 1b3
To: <sip:rziegler@lanscapecorp.dnsalias.com:10000>
Call-Id: 2b0ca57d-245e-4fca-ba52-f0f3ad348e83@192.168.1.2
CSeq: 2633930 REGISTER
Expires: 3600
Max-Forwards: 70
Contact: <sip:rziegler@192.168.1.2:10000>
User-Agent: LanScape VOIP Media Engine/5.10.0102 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (0 Ms, From: 192.168.1.2:7000) <<<<
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.2:10000;received=192.168.1.2:10000
From: <sip:rziegler@lanscapecorp.dnsalias.com:10000>;tag=280 1b3
To: <sip:rziegler@lanscapecorp.dnsalias.com:10000>
Call-ID: 2b0ca57d-245e-4fca-ba52-f0f3ad348e83@192.168.1.2
CSeq: 2633930 REGISTER
WWW-Authenticate: Digest realm="LanScapeRealm", nonce="639237b74e43b0b594c7ff529296892a", opaque="e712264917b6c58fb1bf1797145c9eba"
User-Agent: LanScape Centrex Proxy/3.40 (www.LanScapeCorp.com)
Content-Length: 0
>>>> TxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (20 Ms, To: 192.168.1.2:7000) >>>>
REGISTER sip:lanscapecorp.dnsalias.com:7000 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:10000
From: <sip:rziegler@lanscapecorp.dnsalias.com:10000>;tag=27b 720
To: <sip:rziegler@lanscapecorp.dnsalias.com:10000>
Call-Id: 2b0ca57d-245e-4fca-ba52-f0f3ad348e83@192.168.1.2
CSeq: 2633931 REGISTER
Authorization: Digest algorithm=md5, nonce="639237b74e43b0b594c7ff529296892a", opaque="e712264917b6c58fb1bf1797145c9eba", realm="LanScapeRealm", response="4c6ac4655a20666a913ffbe3cd864c1e", uri="sip:lanscapecorp.dnsalias.com:7000", username="guest"
Expires: 3600
Max-Forwards: 70
Contact: <sip:rziegler@192.168.1.2:10000>
User-Agent: LanScape VOIP Media Engine/5.10.0102 (www.LanScapeCorp.com)
Content-Length: 0
<<<< RxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (30 Ms, From: 192.168.1.2:7000) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:10000;received=192.168.1.2:10000
From: <sip:rziegler@lanscapecorp.dnsalias.com:10000>;tag=27b 720
To: <sip:rziegler@lanscapecorp.dnsalias.com:10000>;tag=41
Call-ID: 2b0ca57d-245e-4fca-ba52-f0f3ad348e83@192.168.1.2
CSeq: 2633931 REGISTER
Contact: <sip:rziegler@192.168.1.2:10000>;expires=3600
User-Agent: LanScape Centrex Proxy/3.40 (www.LanScapeCorp.com)
Content-Length: 0
The last SIP message of “SIP/2.0 200 OK” must be received by your soft phone for the registration to succeed. If you do not receive “200 OK” responses back from a REGISTER transaction, then the next step is figuring out why.
IMPORTANT: Please determine if the VOIP Media Engine is not sending SIP REGISTER messages to your registrar or if your registrar is refusing the REGISTER messages from your application.
Another thing you can do is to handle the following events in your application:
SipRegisterReceived
SipRegisterTrying
SipRegisterSuccess
SipRegistrationIntervalError
SipRegistrationTimeOut
SipRegisterError
They will tell you if there are registration problems.
These events (and many, many more) are documented in the Software developer’s reference. Please become as familiar as possible with the Software developer’s reference and SIP protocol logging so that you can diagnose problems to a higher degree.
Post back to this forum with your results.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: February 18 2005 at 6:39am | IP Logged
|
|
|
I thought I'd pass this along to you also. Intel has a terrific application note on how to use the open source Ethereal network protocol analyzer to debug SIP and RTP problems.
Using Ethereal to Debug SIP and RTP on Voice over IP:
http://resource.intel.com/telecom/support/appnotes/9008/9008 an.pdf
Consider using Ethereal with the VOIP Media Engine's SIP logs to locate problems fast.
|
| Back to Top |
|
| |
|
|
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Topic: about refreshing the registration
