Home
»
General
»
Unkown user account 404
TekSIP - General issues
06.04.2010 02:53:36
mlangman
Posts: 13
|
Hi
I have read through all the posts and was not able to resolve the "Unkown user account 404", issue.
Our final goal is to help our clients make calls behind NAT, to a VoIP provider. But one step at
a time.
The endpoint I entered is the same as the "From:" in the "INVITE".
This is our own product, so if you disagree with what we are doing, just let us know and we
can make changes on our side to.
Overview:
Our SIP Client :192.168.2.23
Your TekSIP Solution: 192.168.2.30
Endpoint: 1000@192.168.2.23
Registrations: Yes 1000 is seen under the registrations with an IP Address of: 192.168.2.23
Log file:
4/5/2010 4:32:12 PM - Database has been compacted successfully.
4/5/2010 4:32:12 PM - TekSIP Service 2.6.0.0 (Revision 0) is being started on : 192.168.2.30:5060 [Accounting disabled] (Microsoft Windows NT 5.1.2600 Service Pack 3).
4/5/2010 4:32:12 PM - TekSIP Service is started on : 192.168.2.30:5060
SIP req. from : 192.168.2.23:5060 (UDP) - 4/5/2010 4:32:15 PM
REGISTER sip:192.168.2.30 SIP/2.0
[From] = <sip:1000@192.168.2.23>;tag=ACU-27b4-4bc4d61
[To] = sip:1000@192.168.2.30
[Contact] = sip:1000@192.168.2.23
[Call-ID] = 01E7D590-4BBA72EE@192.168.2.23
[CSeq] = 110 REGISTER
[Content-Length] = 0
[Expires] = 3600
[Via] = SIP/2.0/UDP 192.168.2.23:5060;rport;branch=z9hG4bK6d9dc5ca-410b-11df-a168-e29984e5292d
[Max-Forwards] = 70
[Route] = <sip:192.168.2.30:5060;lr>
SIP req. to : 192.168.2.23:5060 (UDP) - 4/5/2010 4:32:15 PM
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.23:5060;received=192.168.2.23;rport=5060;branch=z9hG4bK6d9dc5ca-410b-11df-a168-e29984e5292d
From: <sip:1000@192.168.2.23>;tag=ACU-27b4-4bc4d61
To: sip:1000@192.168.2.30
Contact: sip:1000@192.168.2.23
Call-ID: 01E7D590-4BBA72EE@192.168.2.23
CSeq: 110 REGISTER
Max-Forwards: 69
Date: Mon, 05 Apr 2010 23:32:15 GMT
Expires: 3600
Content-Length: 0
SIP req. from : 192.168.2.23:5060 (UDP) - 4/5/2010 4:32:36 PM
INVITE sip:19496776072@192.168.2.30 SIP/2.0
[From] = 1000 <sip:1000@192.168.2.23>;tag=ACU-4f1d-6b6b40d
[To] = 19496776072 <sip:19496776072@192.168.2.30>
[Contact] = <sip:192.168.2.23>
[Call-ID] = 05243C01-00000000-4BBA730F-000000A7@192.168.2.23
[CSeq] = 4201 INVITE
[Content-Length] = 193
[Content-Type] = application/sdp
[Allow] = INVITE
[Allow] = ACK
[Allow] = BYE
[Allow] = CANCEL
[Allow] = OPTIONS
[Allow] = NOTIFY
[Allow] = REFER
[Allow] = PRACK
[Allow] = INFO
[Allow] = UPDATE
[Accept] = application/sdp
[Accept] = application/isup
[Accept] = application/qsig
[Accept] = multipart/mixed
[Accept-Encoding] = identity
[Accept-Language] = en
[Supported] = replaces
[Supported] = 100rel
[Via] = SIP/2.0/UDP 192.168.2.23:5060;rport;branch=z9hG4bK8165c882-410b-11df-a168-e29984e5292d
[Max-Forwards] = 70
[Route] = <sip:192.168.2.30:5060;lr>
SIP req. to : 192.168.2.23:5060 (UDP) - 4/5/2010 4:32:36 PM
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.2.23:5060;received=192.168.2.23;rport=5060;branch=z9hG4bK8165c882-410b-11df-a168-e29984e5292d
From: 1000 <sip:1000@192.168.2.23>;tag=ACU-4f1d-6b6b40d
To: 19496776072 <sip:19496776072@192.168.2.30>
Call-ID: 05243C01-00000000-4BBA730F-000000A7@192.168.2.23
CSeq: 4201 INVITE
Server: TekSIP/v2.6
Content-Length: 0
SIP req. to : 192.168.2.23:5060 (UDP) - 4/5/2010 4:32:36 PM
SIP/2.0 404 Unknown user account
Via: SIP/2.0/UDP 192.168.2.23:5060;received=192.168.2.23;rport=5060;branch=z9hG4bK8165c882-410b-11df-a168-e29984e5292d
From: 1000 <sip:1000@192.168.2.23>;tag=ACU-4f1d-6b6b40d
To: 19496776072 <sip:19496776072@192.168.2.30>
Call-ID: 05243C01-00000000-4BBA730F-000000A7@192.168.2.23
CSeq: 4201 INVITE
Server: TekSIP/v2.6
Content-Length: 0
We would appreciate any help you can offer.
Thank you,
Michael
|
|
0
• permalink
|
06.04.2010 08:36:11
Admin
Administrator
Posts: 254
|
Hi,
Do you have a routing for 19496776072 destination in Routing tab?
Best regards,
Yasin KAPLAN
|
|
0
• permalink
|
06.04.2010 18:21:52
mlangman
Posts: 13
|
I appolagise, could you use this screen shot for the Routing instead, the last one has details to an active account.
Thank you,
Michael
|
|
0
• permalink
|
06.04.2010 19:57:40
mlangman
Posts: 13
|
Hi
Setting the prefix to 19496776072, helped remove this issue. But is it possible to route all calls with any number.
What I am trying to say, can we setup a default route for all calls.
I now have a 403 issue, I will open a new post for that one.
Thank you,
Michael
|
|
0
• permalink
|
08.04.2010 08:29:26
Admin
Administrator
Posts: 254
|
TekSIP utilizes longest matching approach while looking up routing table. You can route all calls to numbers starting "1" prefix by adding a route for "1" prefix.
|
|
0
• permalink
|
08.04.2010 18:20:54
mlangman
Posts: 13
|
Thank you, I will try it.
|
|
0
• permalink
|
09.04.2010 08:21:11
Admin
Administrator
Posts: 254
|
You welcome
|
|
0
• permalink
|