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: Can’t register SIP client to Centrex Proxy on open LAN Post ReplyPost New Topic
Author
Message << Prev Topic | Next Topic >>
outerringz
Intermediate
Intermediate


Joined: November 15 2007
Location: United States
Posts: 15
Posted: November 16 2007 at 1:19pm | IP Logged Quote outerringz
Ultimately, I want to use Centrex Proxy (proxy) and VOIP Media Proxy (media proxy) as a SIP gateway behind NAT, for my remote NAT’d clients to connect to, to get to my Asterisk PBX.

I have loaded proxy and media proxy, and configured them per the included .chm help files. Everything is currently on an open LAN for testing. Proxy is configured to connect to a MySQL database for the Registrar and Authentication. I have enabled Authentication, and keyed a static UserName (1166) and Password (1166) into the “authinfo” table. For test purposes, I am using two soft phone clients, IDEFISK using SIP, and X-Lite using SIP. I have setup internal DNS to resolve sip.dei.com to the proxy server at 192.168.0.213, and configured each soft phone to connect to sip.dei.com with a user name 1166 and password 1166. NOTE: I’m only testing one soft phone at a time, which is why they are both configured for the same account. Neither of the phones can make a successful connection, they both log “SIP/2.0 401 Unauthorized” in the proxy SIP log file. I have included my proxy and media proxy config’s below, along with the SIP log from proxy. Any help you can provide is appreciated.


CENTREX PROXY CONFIG
--------------------
[Software_LanScape_Centrex Proxy_Settings]
DomainNameList=sip.dei.com
GatewayAddress=0.0.0.0
DosEnabled=1
DosEnableIpAddressMonitoring=1
DosRateSeconds=30
DosBanHostDurationSeconds=60
AuthenticationDomain=sip.dei.com
AuthenticationMode=on
AuthenticateRegister=1
AuthenticateInvite=1
AuthenticateBye=1
AuthenticateSubscribe=1
AuthenticateNotify=1
AuthenticateExternalRealmRequests=0
ServerIpAddress=192.168.0.213
ServerNicMacAddress=000BDBD958B7
ServerIpDynamic=1
ServerIpDynamicMonitorIntervalSeconds=60
LocalSipPort=5060
WebUrlNatDetection=
WebUrlNatDatabase=
StaticWanIpAddress=
IpAddressFormat=ClientIPaddress:###(
PortFormat=ClientPort:###(
IpMonitorIntervalSeconds=3600
HuntAnswerTimeoutSeconds=10
InviteResponseTimeoutSeconds=2
FinalAnswerTimeoutSeconds=30
EnableWanIpAddressParameter=0
RegistrarName=Registrar
RegistrarIsCaseSensitive=0
RegistrarDefaultRegistrationTimeSeconds=3600
RegistrarDbName=RegisteredUsers.ldb
RegistrarDbType=1119
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=1
StartMinimizedInSystemTray=1
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=0
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=1
EnableExtendedErrorAndWarnings=0
EnableReatimeMode=0
MediaProxyEnabled=1
MediaProxyControlPort=9000
MediaProxyCommandResponseTimeoutMs=2000
MediaProxyMaxErrors=3
MediaProxyUserName=deiadmin
MediaProxyPassword=##########
MediaProxyRealm=sip.dei.com
MediaProxyAllCalls=0
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=47
AppWindowRight=457
AppWindowTop=699
AppWindowBottom=930
[Software_LanScape_Centrex Proxy_Database Extensions_Authentication]
UseCustomConnectString=1
CustomConnectString=Driver={MySQL ODBC 3.51 Driver};Database=#######;Server=#######;uid=#######;password =#######;Option=3;////****COMMENTED OUT FOR SECURITY****////
UserName=
Password=
OdbcDriverName=Microsoft Access Driver (*.mdb)
DbName=
AuthTableName=authinfo
UserNameFieldName=UserName
PasswordFieldName=Password
[Software_LanScape_Centrex Proxy_Database Extensions_Registrar]
UseCustomConnectString=1
CustomConnectString=__enc_str__:4472697665723D7B4D7953514C20 4F44424320332E3531204472697665727D3B44617461626173653D646569 7369703B5365727665723D3139322E3136382E302E3230303B7569643D44 454961646D696E3B70617373776F72643D6B25454066413D7A656B3B4F70 74696F6E3D333B0D0A
UserName=
Password=
OdbcDriverName=Microsoft Access Driver (*.mdb)
DbName=



VOIP MEDIA PROXY CONFIG
-----------------------
[Software_LanScape_VOIP Media Proxy_Settings]
WebUrlNatDetection=
WebUrlNatDatabase=
StaticWanIpAddress=
DirectoryServerName=Server4730B047
DirectoryServerPort=80
PathFromRoot=
EnableRealtimeMode=0
ServerIpAddress=192.168.0.213
ServerNicMacAddress=000BDBD958B7
ServerIpDynamic=0
ServerIpDynamicMonitorIntervalSeconds=60
RelateSiblingMediaSessions=1
EnableDeadMediaDetection=1
EnableEncryptedRtpMedia=1
IpAddressFormat=ClientIPaddress:###(
PortFormat=ClientPort:###(
IpMonitorIntervalSeconds=3600
EnableWanIpAddressParameter=1
LogSoundsEnabled=1
DisplaySplash=1
StartMinimizedInSystemTray=0
EnableEventLogging=1
ConfirmClearLog=1
EventLogAutoSaveEnabled=1
EventLogSaveIntervalSeconds=3600
MaxLogEntries=500
CallActivity=1
RegistrationRequests=1
ProxyWarnings=1
ProxyInformation=1
ProxyErrors=1
LogExtendedMediaSessionInfo=1
LastConfigPage=202
EnableDynamicNatDetection=0
EnableStaticWanIpAddress=0
EnableNatDatabaseUrl=0
MasterServersColumn1Width=145
MasterServersColumn2Width=291
MediaProxySessionTimeoutMs=20000
MediaProxySessionEvaluateIntervalMs=1000
MediaProxyOrphanedSessionTimeoutMs=120000
MediaProxyPortLow=16000
MediaProxyPortHigh=16200
MediaProxyTerminateSessions=1
MediaProxyCommandResponseTimeoutMs=2000
MediaProxyUserName=deiadmin
MediaProxyPassword=##########
MediaProxyRealm=sip.dei.com
MediaProxySipServerMonitorPeriodMs=1000
MediaProxySipServerPingPeriodMs=10000
MediaProxyUdpBufferSizeInBytes=1500
LicenseFileName=C:\Program Files\LanScape\License Manager\Installed Licenses\Trial-VOIP Media Proxy Server-Enterprise-Tue Nov 06 09_59_13 2007\Trial-VOIP Media Proxy Server-Enterprise License.lic
DissimilarMediaDetectionEnabled=0
DissimilarMediaTolerateTimeMs=2000
RemoteEventLoggingEnable=0
RemoteEventLogHost=
RemoteEventLogPort=22000
EnableSystemTrayBalloons=1
UseEvenPortsOnly=0
AppWindowLeft=707
AppWindowRight=121
AppWindowTop=1360
AppWindowBottom=594



IDEFISK SOFTPHONE
-----------------
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-ad9e1bdd796367b2-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1166@66.106.160.248:5060;rinstance=f7c6b58c6ebc1960& gt;
To: "1166"<sip:1166@sip.dei.com>
From: "1166"<sip:1166@sip.dei.com>;tag=9f7dfa6d
Call-ID: NmRlZDk1MGI3NzRkNWMzMTc3Njc0YTIxNGY3ZDkxNDU.
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.0.102:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-ad9e1bdd796367b2-1 ---d8754z-;rport=5060;received=192.168.0.102
From: "1166" <sip:1166@sip.dei.com>;tag=9f7dfa6d
To: "1166" <sip:1166@sip.dei.com>
Call-ID: NmRlZDk1MGI3NzRkNWMzMTc3Njc0YTIxNGY3ZDkxNDU.
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip.dei.com", nonce="bb7d8e2c9df2dd2b7718f945cef13b37", opaque="0fd4b9e12288f95441736af7da18905c"
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0



X-LITE SOFTPHONE
----------------
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:43446) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 192.168.0.102:43446;branch=z9hG4bK-d87543-bc3c9039d936f005-1 --d87543-;rport
Max-Forwards: 70
Contact: <sip:1166@192.168.0.102:43446;rinstance=2ab2e807d8b62464& gt;
To: "1166"<sip:1166@sip.dei.com>
From: "1166"<sip:1166@sip.dei.com>;tag=9814450c
Call-ID: MTY5ZjQxNDNmODJhOWM4ODhhZGEzYzBiNGJhNzBkYWQ.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: X-Lite release 1011s stamp 41150
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.0.102:43446) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.0.102:43446;branch=z9hG4bK-d87543-bc3c9039d936f005-1 --d87543-;rport=43446;received=192.168.0.102
From: "1166" <sip:1166@sip.dei.com>;tag=9814450c
To: "1166" <sip:1166@sip.dei.com>
Call-ID: MTY5ZjQxNDNmODJhOWM4ODhhZGEzYzBiNGJhNzBkYWQ.
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip.dei.com", nonce="46da2dac7c37eb42f87c2c1646bfcba1", opaque="9cd772402083a0a97f37b5bf717c927a"
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
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 19 2007 at 8:21am | IP Logged Quote support
Hi outerringz,

Thanks for posting your information. You did a great job in describing your setup. We will take a look and repost.


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 19 2007 at 8:59am | IP Logged Quote support
outerringz,

In your original posting, it looks like the two soft phones are being challenged by the LanScape Centrex SIP proxy properly. Your soft phones however are not responding to the challenge. See the REGISTER SIP messages of your original posting. We have highlighted the “WWW-Authenticate:” SIP headers your soft phones should be responding to.

At this time, it looks like you must add proper authentication credentials to your soft phones so that they can respond to the REGISTER authentication challege.


Two other items:

1) Disable authentication at the LanScape Centrex proxy and see if your soft phone will register.

2)
Disable “split media” in your Centrex proxy basic Settings config page. You will not need it.


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 19 2007 at 4:47pm | IP Logged Quote outerringz
Thank you for your response. I have disabled “split media” and tested a few other things I came up with and here is what I know now.

When I could not successfully register a SIP account, I had Centrex Proxy (proxy) configured to communicate with a MySQL database for both the Registrar and Authentication.

I then performed several configuration tests using MySQL for the Authentication database, the local Authentication database, MySQL as the Registrar database, and memory cache as the Registrar database.

I found that I am able to register an Authenticated SIP account using MySQL as the Authentication database as long as I do not use MySQL for the Registrar database, but rather memory cache as the Registrar database. I can also register Authenticated SIP accounts using only the local (built-in) databases.

I have checked, and tested MySQL access permissions for the proxy server and granted the account from the proxy servers IP complete global permissions to the MySQL server.

I have included two versions of the EventLog and SipLog. The first is a failed Authenticated SIP registration attempt using MySQL for both the Registrar and Authentication. The second version is a successful Authenticated SIP registration using MySQL as the Authentication database and Memory Cache as the Registrar database.

I’m at a loss here, I just can figure out why MySQL is working for the Authentication database read, but the Registrar is failing to write the registration to MySQL, when I can use the same connection string, from the same IP, and using the same MySQL account to write changes to the database from a MySQL management console.
Any help you can provide is appreciated.

Using ODBC driver to connect Registrar and Authentication to MySQL
============================================================ ======
SIP registration fails
======================
Event Log
---------
#Rec#2#14:08:56 11/19/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#14:08:56 11/19/07#LanScape Centrex Proxy® Starting...
#Rec#2#14:08:56 11/19/07#DNS reports the following IP address for domain "sip.dei.com": 192.168.0.213
#Rec#2#14:08:56 11/19/07#Opening database connection...
#Rec#2#14:08:56 11/19/07#"Registrar ODBC Driver" database extension initialized.
#Rec#2#14:08:56 11/19/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#14:08:56 11/19/07#Server Name: LanScape Centrex Proxy/3.42.2.5
#Rec#2#14:08:56 11/19/07#Private IP: 192.168.0.213
#Rec#2#14:08:56 11/19/07#WAN IP: 192.168.0.213
#Rec#2#14:08:56 11/19/07#Server Port: 5060
#Rec#2#14:08:56 11/19/07#Domain: sip.dei.com
#Rec#2#14:08:56 11/19/07#Authentication: on
#Rec#2#14:08:56 11/19/07#Authentication Realm: sip.dei.com
#Rec#2#14:08:56 11/19/07#Initializing remote authentication database.
#Rec#2#14:08:56 11/19/07#Opening database connection...
#Rec#2#14:08:56 11/19/07#"Authentication ODBC Driver" database extension initialized.
#Rec#2#14:08:56 11/19/07#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#14:08:56 11/19/07#Call Routing: DISABLED
#Rec#2#14:08:57 11/19/07#Initializing control Port 9000...
#Rec#2#14:08:57 11/19/07#Media Proxy support started. Using control port 9000.
#Rec#2#14:08:57 11/19/07#Proxy Ready
#Rec#2#14:08:58 11/19/07#VOIP Media Proxy 192.168.0.213:16000 is on-line.

SIP Log
-------
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-144feb3b6d381b43-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060;rinstance=a9ccf8d8654f48fb& gt;
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=0a362b5d
Call-ID: MTBhOWJkNjUwMDQ0NzQ4NDYzOWUzYmNmOWRkMjZjYzM.
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.0.102:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-144feb3b6d381b43-1 ---d8754z-;rport=5060;received=192.168.0.102
From: "1167" <sip:1167@sip.dei.com>;tag=0a362b5d
To: "1167" <sip:1167@sip.dei.com>
Call-ID: MTBhOWJkNjUwMDQ0NzQ4NDYzOWUzYmNmOWRkMjZjYzM.
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip.dei.com", nonce="2fccd3e8f3e9b88e747c41a2e4576004", opaque="41e457ba70bb93f7f65ebff28ca8344a"
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-af3ed25d897f3924-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060;rinstance=a9ccf8d8654f48fb& gt;
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=0a362b5d
Call-ID: MTBhOWJkNjUwMDQ0NzQ4NDYzOWUzYmNmOWRkMjZjYzM.
CSeq: 2 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Authorization: Digest username="1167",realm="sip.dei.com",nonce="2fccd3e8f3e9b88e7 47c41a2e4576004",uri="sip:sip.dei.com",response="521e0a6735d 1d172fac81c6c4006a6d8",algorithm=MD5,opaque="41e457ba70bb93f 7f65ebff28ca8344a"
Allow-Events: presence
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.0.102:5060) >>>>
SIP/2.0 400 Bad Request
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-af3ed25d897f3924-1 ---d8754z-;rport=5060;received=192.168.0.102
From: "1167" <sip:1167@sip.dei.com>;tag=0a362b5d
To: "1167" <sip:1167@sip.dei.com>
Call-ID: MTBhOWJkNjUwMDQ0NzQ4NDYzOWUzYmNmOWRkMjZjYzM.
CSeq: 2 REGISTER
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-3f16e761533df773-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060;rinstance=c72e101640b42d8f& gt;
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=3e5a0b6a
Call-ID: M2RkNjhkYjExYzg0MDM2NWQ2NWU4YTZiZWQ5ZTZjNjI.
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.0.102:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-3f16e761533df773-1 ---d8754z-;rport=5060;received=192.168.0.102
From: "1167" <sip:1167@sip.dei.com>;tag=3e5a0b6a
To: "1167" <sip:1167@sip.dei.com>
Call-ID: M2RkNjhkYjExYzg0MDM2NWQ2NWU4YTZiZWQ5ZTZjNjI.
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip.dei.com", nonce="2fccd3e8f3e9b88e747c41a2e4576004", opaque="c1fd1ab24f158a732a0f16ae02ebba81"
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-a09e66718a5755aa-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060;rinstance=c72e101640b42d8f& gt;
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=3e5a0b6a
Call-ID: M2RkNjhkYjExYzg0MDM2NWQ2NWU4YTZiZWQ5ZTZjNjI.
CSeq: 2 REGISTER
Expires: 70
Allow: INVITE, ACK, C


Using ODBC driver to connect Authentication to MySQL while leaving Registrar to use memory cache.
=============================== ============================================================ ======
SIP registration successful
===========================
Event Log
#Rec#2#14:14:08 11/19/07#***************************** Centrex Proxy Session Start *****************************
#Rec#2#14:14:08 11/19/07#LanScape Centrex Proxy® Starting...
#Rec#2#14:14:08 11/19/07#DNS reports the following IP address for domain "sip.dei.com": 192.168.0.213
#Rec#2#14:14:08 11/19/07#LanScape Centrex Proxy® running. Configuration settings follow:
#Rec#2#14:14:08 11/19/07#Server Name: LanScape Centrex Proxy/3.42.2.5
#Rec#2#14:14:08 11/19/07#Private IP: 192.168.0.213
#Rec#2#14:14:08 11/19/07#WAN IP: 192.168.0.213
#Rec#2#14:14:08 11/19/07#Server Port: 5060
#Rec#2#14:14:08 11/19/07#Domain: sip.dei.com
#Rec#2#14:14:08 11/19/07#Authentication: on
#Rec#2#14:14:08 11/19/07#Authentication Realm: sip.dei.com
#Rec#2#14:14:08 11/19/07#Initializing remote authentication database.
#Rec#2#14:14:08 11/19/07#Opening database connection...
#Rec#2#14:14:08 11/19/07#"Authentication ODBC Driver" database extension initialized.
#Rec#2#14:14:08 11/19/07#SIP protocol log file name: CentrexProxySipLog.log
#Rec#2#14:14:08 11/19/07#Call Routing: DISABLED
#Rec#2#14:14:08 11/19/07#Initializing control Port 9000...
#Rec#2#14:14:08 11/19/07#Media Proxy support started. Using control port 9000.
#Rec#2#14:14:09 11/19/07#Proxy Ready
#Rec#2#14:14:09 11/19/07#VOIP Media Proxy 192.168.0.213:16000 is on-line.
#Rec#8#14:14:15 11/19/07#REGISTER 1167@192.168.0.102:5060 (70 sec)    Received from: 192.168.0.102:5060    Registering UA/Contact: 66.106.160.248:5060    (NAT Detected)

SIP Log
-------
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-8bac2d21ecd3e8b9-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060;rinstance=0a596ed4ea155a06& gt;
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=21141862
Call-ID: ODllZWEwMTBmYTQxMDQwMzIxY2UyOGJiYWRmNjAwOGQ.
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.0.102:5060) >>>>
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-8bac2d21ecd3e8b9-1 ---d8754z-;rport=5060;received=192.168.0.102
From: "1167" <sip:1167@sip.dei.com>;tag=21141862
To: "1167" <sip:1167@sip.dei.com>
Call-ID: ODllZWEwMTBmYTQxMDQwMzIxY2UyOGJiYWRmNjAwOGQ.
CSeq: 1 REGISTER
WWW-Authenticate: Digest realm="sip.dei.com", nonce="13dbb74ff6bdd7fb3685c8d97b5549d6", opaque="5364dbd3a8d3134f266de4baafaf3e12"
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
REGISTER sip:sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-1a01ca2e04bc0972-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060;rinstance=0a596ed4ea155a06& gt;
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=21141862
Call-ID: ODllZWEwMTBmYTQxMDQwMzIxY2UyOGJiYWRmNjAwOGQ.
CSeq: 2 REGISTER
Expires: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Authorization: Digest username="1167",realm="sip.dei.com",nonce="13dbb74ff6bdd7fb3 685c8d97b5549d6",uri="sip:sip.dei.com",response="a8167cec326 7d19104507d766575eb18",algorithm=MD5,opaque="5364dbd3a8d3134 f266de4baafaf3e12"
Allow-Events: presence
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.0.102:5060) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-1a01ca2e04bc0972-1 ---d8754z-;rport=5060;received=192.168.0.102
From: "1167" <sip:1167@sip.dei.com>;tag=21141862
To: "1167" <sip:1167@sip.dei.com>;tag=41
Call-ID: ODllZWEwMTBmYTQxMDQwMzIxY2UyOGJiYWRmNjAwOGQ.
CSeq: 2 REGISTER
Contact: <sip:1167@66.106.160.248:5060;rinstance=0a596ed4ea155a06& gt;;expires=70
Expires: 70
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
SUBSCRIBE sip:1167@sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-85ed1e20073290cc-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060>
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=5127984e
Call-ID: ODU1NTQ5OGNiN2MyZjJjMjhjMzc2NWI0Mzk5Y2RlODQ.
CSeq: 1 SUBSCRIBE
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, NOTIFY, REFER, MESSAGE, OPTIONS
User-Agent: Idefisk
Event: message-sumamry
Content-Length: 0

>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To: 192.168.0.102:5060) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-85ed1e20073290cc-1 ---d8754z-;rport=5060;received=192.168.0.102
From: "1167" <sip:1167@sip.dei.com>;tag=5127984e
To: "1167" <sip:1167@sip.dei.com>
Call-ID: ODU1NTQ5OGNiN2MyZjJjMjhjMzc2NWI0Mzk5Y2RlODQ.
CSeq: 1 SUBSCRIBE
Proxy-Authenticate: Digest realm="sip.dei.com", nonce="13dbb74ff6bdd7fb3685c8d97b5549d6", opaque="5364dbd3a8d3134f266de4baafaf3e12"
Server: LanScape Centrex Proxy/3.42.2.5 (www.LanScapeCorp.com)
Content-Length: 0

<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From: 192.168.0.102:5060) <<<<
SUBSCRIBE sip:1167@sip.dei.com SIP/2.0
Via: SIP/2.0/UDP 66.106.160.248:5060;branch=z9hG4bK-d8754z-47ed32a20bb22b90-1 ---d8754z-;rport
Max-Forwards: 70
Contact: <sip:1167@66.106.160.248:5060>
To: "1167"<sip:1167@sip.dei.com>
From: "1167"<sip:1167@sip.dei.com>;tag=5127984e
Call-ID: ODU1NTQ5OGNiN2MyZjJjMjhjMz
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:04am | IP Logged Quote support
We will verify that using both MySql for authentication and registrar DB are OK here. Maybe a bug was introduced in the product somewhere.

Good work on your part. Sounds as if you are doing everything properly.

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 20 2007 at 7:36am | IP Logged Quote support
When we use MySql for both authentication and registrar databases, all looks ok. We use the supplied RegistrarDatabaseDriver.dll and AuthDatabaseDriver.dll lanscape plugins for the database I/O.

The authentication Db has the following attributes:

DB name: authdatabase
Table: authinfo

Columns:
`UserName` char(50) NOT NULL default ''
`Password` char(50) NOT NULL default ''



Here is similar info for the registrar Db:

DB name: registrardatabase
Table: registereduseragents

Columns:
'RegistrationName` char(50) NOT NULL default '',
`IpAddressStr` char(16) default NULL,
`Port` int(11) default NULL,
`ExpireTimeSeconds` int(11) unsigned default NULL,
`IsNated` int(11) default NULL,
`UserAgent` char(255) NOT NULL default '',
`DomainName` char(255) NOT NULL default '',
`ExternalDomainName` char(255) NOT NULL default '',
`ProxyServerPort` int(11) default NULL


So, what are we missing? Check that your table names and field definitions match those above.

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:53pm | IP Logged Quote outerringz
Thank you for describing this thoroughly, I had both tables in the same DB and I used the “Empty_MySQL_registrardatabase.sql” file to build the registerduseragents structure, which left out the ExternalDomainName field.

I’m not sure if my issue was the missing field or that I had both tables in the same DB, but I’m now working with both the Registrar and Authentication databases in MySQL and all is well.

Thanks,

Mike
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:23pm | IP Logged Quote support
OK, We will update the empty database creation file to make sure the ExternalDomainName MySQL field is added. Good work.

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