Return to LanScape's home page Go back a page...       Active TopicsActive Topics   Display List of Forum MembersMember List   Knowledge Base SearchSearch   HelpHelp  RegisterRegister  LoginLogin

SIP Proxy and Media Proxy - Pre-Sales Technical Support
 LanScape Support Forum -> SIP Proxy and Media Proxy - Pre-Sales Technical Support
Subject Topic: Possible Bug Found In Centrex Proxy Server Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
outerringz
Intermediate
Intermediate


Joined: November 15 2007
Location: United States
Posts: 15
Posted: November 19 2007 at 5:04pm | IP Logged Quote outerringz
I believe I may have found a bug in Centrex Proxy Server.

Symptom:
---------
When an incorrectly configured SIP client attempts to register with Centrex Proxy Server, Centrex Proxy Server crashes.

Reproducible:
-------------
Yes

Centrex Proxy Server Configuration
----------------------------------
Registrar:
Configured to use memory cache as the registrar database

Authentication:
Disabled

SIP Client Configuration
------------------------
Configured with correct SIP domain, but lacking a username or password

Tested and confirmed with the following devices:
X-lite (soft phone)
IDEFISK (soft phone)
GrandStream GXP2000( hard phone)
Back to Top View outerringz's Profile Search for other posts by outerringz
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: November 20 2007 at 7:06am | IP Logged Quote support
Thanks for identifying this... Sounds nasty.

Please post a registration SIP message that causes the crash.

Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
outerringz
Intermediate
Intermediate


Joined: November 15 2007
Location: United States
Posts: 15
Posted: November 20 2007 at 3:27pm | IP Logged Quote outerringz
Hi,

Unfortunately, it crashes so fast that it never has a chance to write anything to the log. Basically, with the application closed, I delete the log files. Then I launch proxy, wait for it to fully load up, and then connect the mis-configured SIP client, and down the server goes. I have posted the EventLog and my config (with security items commented out) below. Hope that helps narrow it down.

Event Log
---------
#Rec#2#13:10:15 11/20/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#13:10:15 11/20/07#LanScape Centrex Proxy® Starting...
#Rec#2#13:10:15 11/20/07#DNS reports the following IP address for domain "66.106.160.245": 66.106.160.245
#Rec#2#13:10:15 11/20/07#Starting Wan IP address monitoring.
#Rec#2#13:10:15 11/20/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#13:10:15 11/20/07#Server Name: LanScape Centrex Proxy/3.42.2.5
#Rec#2#13:10:15 11/20/07#Private IP: 192.168.0.213
#Rec#2#13:10:15 11/20/07#WAN IP: 66.106.160.245
#Rec#2#13:10:15 11/20/07#Server Port: 5060
#Rec#2#13:10:15 11/20/07#Domain: 66.106.160.245
#Rec#2#13:10:15 11/20/07#Authentication: off
#Rec#2#13:10:15 11/20/07#Authentication Realm: 66.106.160.245
#Rec#2#13:10:15 11/20/07#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#13:10:15 11/20/07#Call Routing: DISABLED
#Rec#2#13:10:15 11/20/07#Initializing control Port 9000...
#Rec#2#13:10:15 11/20/07#Media Proxy support started. Using control port 9000.
#Rec#2#13:10:15 11/20/07#Proxy Ready
#Rec#2#13:10:18 11/20/07#VOIP Media Proxy 192.168.0.213:16000 is on-line.

Config
------
[Software_LanScape_Centrex Proxy_Settings]
DomainNameList=///***PUBLIC IP***///
GatewayAddress=///***PUBLIC IP***///
DosEnabled=1
DosEnableIpAddressMonitoring=1
DosRateSeconds=30
DosBanHostDurationSeconds=60
AuthenticationDomain=///***PUBLIC IP***///
AuthenticationMode=off
AuthenticateRegister=1
AuthenticateInvite=1
AuthenticateBye=1
AuthenticateSubscribe=1
AuthenticateNotify=1
AuthenticateExternalRealmRequests=0
ServerIpAddress=192.168.0.213
ServerNicMacAddress=000BDBD958B7
ServerIpDynamic=0
ServerIpDynamicMonitorIntervalSeconds=60
LocalSipPort=5060
WebUrlNatDetection=
WebUrlNatDatabase=
StaticWanIpAddress=///***PUBLIC IP***///
IpAddressFormat=ClientIPaddress:###(
PortFormat=ClientPort:###(
IpMonitorIntervalSeconds=3600
HuntAnswerTimeoutSeconds=10
InviteResponseTimeoutSeconds=2
FinalAnswerTimeoutSeconds=30
EnableWanIpAddressParameter=0
RegistrarName=Registrar
RegistrarIsCaseSensitive=0
RegistrarDefaultRegistrationTimeSeconds=3600
RegistrarDbName=RegisteredUsers.ldb
RegistrarDbType=1118
RegistrarEnableWriteDbCount=0
RegistrarRuntimeUserDbSaveCount=1
RegistrarEnableWriteDbSeconds=0
RegistrarRuntimeUserDbSaveSeconds=3600
RegistrarDatabseDriverDll=C:\Program Files\LanScape\Centrex Proxy Server Enterprise Trial\Database Driver\RegistrarDatabaseDriver.dll
RegistrarMonitorDbForExpiredEntries=1
RegistrarMonitorDbForExpiredEntriesSeconds=3600
RegistrarEnableEvents=1
RegistrarEventNames=user-available,user-unavailable
CallRoutingDatabaseFile=CallRouting.ldb
EnableSipLog=1
SipLogFileName=C:\Program Files\LanScape\Centrex Proxy Server Enterprise Trial\CentrexProxySipLog.log
RemoteSipLogServerEnabled=0
RemoteSipLogServer=
RemoteSipLogServerPort=19000
SipLogFilterRegister=0
SipLogBadMessages=0
LogSoundsEnabled=1
EnableWanIpAndPortTranslationErrors=0
RemoteEventLoggingEnable=0
RemoteEventLogHost=
RemoteEventLogPort=21000
EnableSystemTrayBalloons=1
DisplaySplash=0
StartMinimizedInSystemTray=0
EnableEventLogging=1
ConfirmClearLog=1
EventLogAutoSaveEnabled=1
EventLogSaveIntervalSeconds=10
MaxLogEntries=500
CallActivity=1
RegistrationRequests=1
ProxyWarnings=1
ProxyInformation=1
ProxyErrors=1
LogExtendedMediaSessionInfo=0
LastConfigPage=202
EnableWanIpUsage=1
DnsMonitorIntervalSeconds=60
DomainNameIsWanIpAddress=1
EnableStaticWanIpAddress=0
EnableDynamicNatDetection=0
EnableNatDatabaseUrl=0
EnableCallRouting=0
EnableUserAgenstCallingThemself=0
EnableGlobalInet=0
LocalDirectoryColumn1Width=145
LocalDirectoryColumn2Width=291
CallRoutingColumn1Width=145
CallRoutingColumn2Width=291
AuthenticationNonceExpireTimeSeconds=3600
AuthenticationColumn1Width=145
AuthenticationColumn2Width=291
AuthenticationDbType=1179
AuthenticationDbDriverDll=C:\Program Files\LanScape\Centrex Proxy Server Enterprise Trial\Database Driver\AuthDatabaseDriver.dll
EnableRecordRoute=1
AllowBadContentLengthHeaders=1
FilterEarlyMediaProvisionalResponses=0
EnableSplitMedia=0
EnableExtendedErrorAndWarnings=0
EnableReatimeMode=0
MediaProxyEnabled=1
MediaProxyControlPort=9000
MediaProxyCommandResponseTimeoutMs=2000
MediaProxyMaxErrors=3
MediaProxyUserName=///***USERNAME***///
MediaProxyPassword=///***PASSWORD***///
MediaProxyRealm=///***REALM***///
MediaProxyAllCalls=1
MediaProxyCallsToOtherDomains=1
MediaProxyCallsFromOtherDomains=1
CallHistoryManagerOrphanTimeoutSeconds=86400
CallHistoryManagerEvaluationIntervalSeconds=3600
GuiPerformanceDataEnabled=1
GuiPerformanceDataUpdateRateSeconds=1
GuiShowListData=0
GuiShowListDataRateMs=500
MaxSipMessagexLength=4096
EnablePlugins=0
PluginFileName=
UnexportedProcWarnings=1
LicenseFileName=C:\Program Files\LanScape\License Manager\Installed Licenses\Trial-Centrex Proxy Server-Enterprise-Tue Nov 06 10_23_44 2007\Trial-Centrex Proxy Server-Enterprise License.lic
IgnoreEmptySipMessages=1
SlaveServerUdpBufferSizeInBytes=1500
AppWindowLeft=74
AppWindowRight=7
AppWindowTop=1056
AppWindowBottom=480
[Software_LanScape_Centrex Proxy_Database Extensions_Authentication]
UseCustomConnectString=1
CustomConnectString=Driver={MySQL ODBC 3.51 Driver};Database=///***MYDATABASE***///;Server=///***DBSERVE R***///;uid=///***USERNAME***///;password=///***PASSWORD***/ //;Option=3;
UserName=
Password=
OdbcDriverName=Microsoft Access Driver (*.mdb)
DbName=
AuthTableName=authinfo
UserNameFieldName=UserName
PasswordFieldName=Password
Back to Top View outerringz's Profile Search for other posts by outerringz
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: November 20 2007 at 4:27pm | IP Logged Quote support
Ok. Here's a thought. We can locate this nasty bug if we get a REGISTER message that causes the blow out.

You should have a command line SipLogD.exe server that comes with the SIP proxy product. Its in your install directory somewhere.

What you can do is temporarily start the SipLogD EXE listening on your normal SIP port. Make sure the SIP proxy is not executing when you do this.

Then run your SIP phone that causes the blow up. You should be able to capture the REGISTER SIP message using the SipLogD EXE. Please send that REGISTER message to us by posting it to this thread.

Thanks,


Support

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
outerringz
Intermediate
Intermediate


Joined: November 15 2007
Location: United States
Posts: 15
Posted: November 20 2007 at 6:52pm | IP Logged Quote outerringz
Here is the log generated by "siplogdtrial.exe" when trying to register a SIP client configured with a valid server IP, but NULL values for the username and password. The log is showing the client as 1167, I believe it's retrieving this from the caller ID field on the softphone. There is no username configured, but this is the exact setup that crashes the the Centrex Proxy every time.

This same client config from the three different SIP client devices I mentioned above cause the Centrex Proxy Server (proxy) to crash when the proxy is configured to use the memory cache Registrar database and Authentication is disabled.

This is the entire log from the start of siplogdtrial.exe to the SIP client registration timeout.


siplogdtrial.exe Log
====================
LanScape SIPlogd Trial for Windows 9x/NT/2k/2003
Copyright 1998-2007 LanScape Corporation (www.LanScapeCorp.com)
LanScape - Simplifying SIP/RTP/VOIP Network Telephony
For help, start server with the -h command line option.
Version 4.83.0.9

------------------------------------------------------------ ----------------
Software license agreement:
This software is protected by US and International copyright law and
is not to be redistributed by LanScape customers or any other individual
or entity. LanScape grants you the right to use this software in conjunction
with any purchased LanScape Voice over IP product. If you have received this
software without first purchasing a valid license for a LanScape VOIP
product, you are not authorized to use this software.
------------------------------------------------------------ ----------------

Server ready. Listening on port 5060
Ctrl+C to exit.
Ctrl+Break to clear the screen.


REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0

REGISTER sip:192.168.0.213 SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1- --d
8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.0.102:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.0.213>
From: "1167"<sip:192.168.0.213>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0
Back to Top View outerringz's Profile Search for other posts by outerringz
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: November 20 2007 at 7:01pm | IP Logged Quote support
you are the man! good job. we will look into ASAP.

Support

Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 
support
Administrator
Administrator


Joined: January 26 2005
Location: United States
Posts: 1666
Posted: November 21 2007 at 8:53am | IP Logged Quote support
Hi Mike,

Thanks for your REGISTER SIP message post. We hunted down the culprit and fixed it. For now you will just have to make sure that your SIP clients specify a user agent name. If this becomes a real problem for you, then we can get you an updated trial image for test.

Here is a log of your REGISTER now working without the crash:

Code:


************* Log Opened (Nov 21 08:48:16) *************

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.1.2:1214) <<<<
REGISTER sip:192.168.1.2 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1--- d8754z-;rport
Max-Forwards: 70
Contact: <sip:192.168.1.2:5060;rinstance=b4eb5b6b8d6b53da>
To: "1167"<sip:192.168.1.2>
From: "1167"<sip:192.168.1.2>;tag=6418b34b
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Allow-Events: presence
Content-Length: 0


>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.1.2:1214) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.2:5060;branch=z9hG4bK-d8754z-0199a12aa0e175f0-1--- d8754z-;rport=1214;received=192.168.1.2
From: "1167" <sip:1167@192.168.1.2>;tag=6418b34b
To: "1167" <sip:1167@192.168.1.2>;tag=6334
Call-ID: MWI3ODBkMTkzMGFiMGQwNzkwNDE4MTViOGZkMWE2ZTg.
CSeq: 1 REGISTER
Contact: <sip:1167@192.168.1.2:5060;rinstance=b4eb5b6b8d6b53da> ;expires=70
Expires: 70
Server: LanScape Centrex Proxy/3.42.2.7 (www.LanScapeCorp.com)
Content-Length: 0

************* Log Closed (Nov 21 08:48:24) *************



Good job.


Support
Back to Top View support's Profile Search for other posts by support Visit support's Homepage
 

If you wish to post a reply to this topic you must first login
If you are not already registered you must first register

  Post ReplyPost New Topic
Printable version Printable version

Forum Jump
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot delete your posts in this forum
You cannot edit your posts in this forum
You cannot create polls in this forum
You cannot vote in polls in this forum





Contact LanScape Hear what the Lawyers have to say How youm may use this site Read your privacy rights