TekSIP - Recent Posts

Topic "dial outgoing call" a message from admin

Fri, 06 Aug 2010 11:09:05 GMT

You welcome

Topic "dial outgoing call" a message from mauro

Thu, 05 Aug 2010 23:19:13 GMT

the problem here is resolved
had a device with the same port 5060 running on the internal network

thanks

Topic "dial outgoing call" a message from admin

Wed, 04 Aug 2010 09:07:17 GMT

Hi,

Set logging level to debug at settings / service parameters and send me the log entries for a sample session.
Log file can be found TekSIP application directory and accessible through file menu.

Topic "dial outgoing call" a message from mauro

Tue, 03 Aug 2010 20:02:56 GMT

I setting my routing now
well this is nice but something yet is wrong --- now ringing at external number only one time then in the x-lite show me failed
where is a problem now
look at this

Topic "Code 400 response to Register method" a message from admin

Mon, 02 Aug 2010 11:36:40 GMT

Hi,

Latest version of TekSIP supports * character in address of records (in From, To and Contact headers). There is no support for "?" yet.

Best regards,

Yasin KAPLAN

Topic "Code 400 response to Register method" a message from CanSipUser

Mon, 02 Aug 2010 09:19:14 GMT

Hello Admin. Im just wondering if the latest build can now handle the * and ? characters. Thanks you

Topic "dial outgoing call" a message from admin

Fri, 30 Jul 2010 16:51:34 GMT

Hi,

You need to add a routing entry for VoIP Rider. See an example below;

Best regards,

Yasin KAPLAN

Topic "dial outgoing call" a message from mauro

Thu, 29 Jul 2010 22:10:06 GMT

have a 2 point here both with x-lite in diferents network net1 is 192.168.0.109 internal ip net2 is 192.168.8.23 internal ip
the xlite of net2 have a domain and target domain in 187.45.23.110 that is my external ip too -- then x-lite to xlite is ok dial ring speak good

well how make this to dial a number 1 902 3432222 to my voip operator that sip is sip.voiprider.com

thanks

Topic "Can not get the remote End Point to Register" a message from admin

Tue, 27 Jul 2010 12:55:39 GMT

You can send logs to info at teksip.com

Topic "Can not get the remote End Point to Register" a message from klgoh

Tue, 27 Jul 2010 12:17:49 GMT

Please ignore my previous posting. Do you have an email that I can send the log file direct to you. I don't like the fix IP to publish on the forum.

I manage to get the HT503 to register to TekSIP by changing the SIP Server setting at the HT503 to the Private IP address of the TekSIP machine but can not dial to the HT503. I notice the following:

1. If using UDP, HT503 do show not register but the TekSIP registered the HT503 with the Address shown on the "Registrations" page as Location B Public IP address. (I did mentioned the Location B UDP may not work. I did try with IPtel.org with UDP also can't register)
2. If change to TCP, HT503 do show register but the TekSIP registered the HT503 with the Address shown on the "Registration" page as FQDN of Location A. I can not dial the HT503 also. Check the log show:

_______________________________________________________

/27/2010 5:05:08 PM - Debug Message (SendUDPPacket-General):

Cannot access a disposed object.
Object name: 'System.Net.Sockets.TcpClient'.

SIP req. to : :0 (UDP) - 7/27/2010 5:05:08 PM

__________________________________________________

any solution?

Topic "Can not get the remote End Point to Register" a message from admin

Tue, 27 Jul 2010 09:30:55 GMT

As far as I understand 202.188.61.2 is the external IP address of location B. You can click "Use External Address" and set external IP address as 202.188.61.2
at Settings / Service Parameters. You should not receive 502 after this setting. Please send me a log for the latest situation.

Topic "Can not get the remote End Point to Register" a message from klgoh

Tue, 27 Jul 2010 07:58:47 GMT

I have download and installed your latest build and I found the following problem.

TekSip is doing a SIP req to the incoming IP with the incoming port number (for my last example 110.159.123.13:2050) when TekSip receive a SIP req from Location B. But TekSIP still receive error 502. This is because the HT503 at Location B is listen to Port 5060 and it is behind the NAT, and the NAT is set to forward incoming port 5060 traffic to HT503. Therefore incoming port 2050 traffic will not forward to HT503.
I also notice that HT503 did a SIP req to the TekSip are using port 5060 (if I set HT503 not to use random port) but when it pass thru Location B NAT (I am using Dlink DI615), the NAT will remap the port (in my last example was port 2050), and the remap to port number is random. Therefore, TekSIP should do a SIP req to Incoming IP address with Port number 5060 (which appear in [Route] = tag). ie 110.159.123.13:5060 when respond to SIP req from HT503.

The "SIP Domain" setting is the Private IP address of the Machine running TekSIP. I did try to change to FQDN (ie sip.location1.com) but it revert back to the Private IP address when I click the "save" button.

Topic "Can not get the remote End Point to Register" a message from admin

Mon, 26 Jul 2010 11:45:14 GMT

Hi,

What is the "SIP Domain" configured in Settings / Service Paramters in TekSIP? I've fixed the issue with 502 response. Download
and test latest built which I've posted to TekSIP web site a couple of minutes ago.

Best regards,

Yasin KAPLAN
edited by admin on 26.07.2010

Topic "Can not get the remote End Point to Register" a message from klgoh

Mon, 26 Jul 2010 10:04:40 GMT

Following is my log during the location B HT503 try to register.

note:

A. sip.location1.com is FQDN for location A will translate to IP address 202.188.61.2 (I have changed the actual IP address for the purpose of this posting)
B. 110.159.123.13 is the public IP for location B. Behind the NAT for this address is the HT503 (private ip 192.168.1.120)
C. TekSIP is running behind the NAT which Public address is 202.188.61.2.

I can notice that the HT503 have send a SIP req to register to the TEKSIP with the correct source Public IP. BUt when TekSIP try to respond to this request, it make a SIP req to the public IP of Location A instate of place the SIP req to the public IP of the Location B. Please advise.

_______________________________________________________________________________

SIP req. from : 110.159.123.13:2050 (TCP) - 7/26/2010 2:49:28 PM

REGISTER sip:sip.location1.com SIP/2.0
[Via] = SIP/2.0/TCP 192.168.1.120:5060;branch=z9hG4bK1285751670;rport;alias
[Route] =
[From] = ;tag=784203400
[To] =
[Call-ID] = 1057814588-5060-1@192.168.1.120
[CSeq] = 2000 REGISTER
[Contact] = ;reg-id=1;+sip.instance=""
[Max-Forwards] = 70
[User-Agent] = Grandstream HT-503 V1.1B 1.0.1.63
[Supported] = path
[Expires] = 1800
[Allow] = INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE
[Content-Length] = 0

SIP req. to : 202.188.61.2:5060 (TCP) - 7/26/2010 2:49:28 PM

SIP/2.0 502 Unknown host or domain
Via: SIP/2.0/TCP 192.168.1.120:5060;branch=z9hG4bK1285751670;received=110.159.123.13;rport=2050;alias
From: ;tag=784203400
To:
Call-ID: 1057814588-5060-1@192.168.1.120
CSeq: 2000 REGISTER
Server: TekSIP/v2.9
Content-Length: 0

___________________________________________________________________________________

Topic "Can not get the remote End Point to Register" a message from admin

Thu, 22 Jul 2010 19:35:40 GMT

Yes, TekSIP supports TCP transport. Can you send me TekSIP log after setting log level to debug at settings / service parameters for REGISTER requests from location B?

Topic "Can not get the remote End Point to Register" a message from klgoh

Thu, 22 Jul 2010 18:06:16 GMT

Yes, in the router for Location A and B, port forward 5060 to respective device as you mentioned but still can not get Location B to register to TEKSIP server at location A. Need to point out one matter, Location B, I set the HT503 to use TCP instate of UDP. I think my Location B ISP block UDP transport. I did setup Location B for IPtel.org service and only TCP can register to IPtel.org SIP server successfully. TEKSIP supported TCP, right?

Topic "Can not get the remote End Point to Register" a message from admin

Thu, 22 Jul 2010 17:45:12 GMT

Hi,

Have you set up a reverse mapping for UDP port 5060 to Grandstream HT503 at location B? You need to have a similar mapping at location A for TekSIP.

Best regards,

Yasin KAPLAN

Topic "Can not get the remote End Point to Register" a message from klgoh

Thu, 22 Jul 2010 12:11:07 GMT

I would like to do a setup to link two location A and B together. The setup as follows:
Location A: Fix IP, NAT, TekSIP server is installed behind the NAT. ATA is Grandstream HT286 install same LAN with TekSIP server. I manage to make the ATA registered to the TekSIP Server.
Location B: Dynamic IP, NAT. ATA is Grandstream HT503 is behind NAT. The ATA can not register to TekSIP Server at location A.

The idea is to enable the ATA at Location A and Location B can call each other. Is this possible? If possible, what is the setup for Location A Router, Location B Router and ATA. Thanks in advance.

Topic "not forwarding the ip to client" a message from sp.mohan

Tue, 22 Jun 2010 20:55:00 GMT

if its a bug means, please fixed it and give me. do you aware of sipp call simulator?

Topic "not forwarding the ip to client" a message from admin

Tue, 22 Jun 2010 17:07:51 GMT

Do you need anything to be fixed at this point?

Topic "not forwarding the ip to client" a message from sp.mohan

Tue, 22 Jun 2010 14:30:22 GMT

sorry for confusion. i tried without registration. its works fine for me. when i tried with registration. i found forwarding invite message has ip mismatch in the TO filed.please check both PCAP logs.

Topic "not forwarding the ip to client" a message from admin

Tue, 22 Jun 2010 14:20:54 GMT

Would you like TekSIP to route calls from 172.27.14.3 to 172.27.14.2 without registration?

Topic "not forwarding the ip to client" a message from sp.mohan

Tue, 22 Jun 2010 10:45:44 GMT

hello

thanks you very much for your reply. please find one more teksip.pcap which doesn't have any registrar. If you see this teksip.pcap logs, you can understand what i am trying to tell you. shall i sent you my scenarios for sipp call simulator?

Topic "not forwarding the ip to client" a message from admin

Tue, 22 Jun 2010 10:35:50 GMT

No, TekSIP keeps From and To headers unchanged since they are informational headers. TekSIP alters only request URI;

SIP req. to : 172.27.14.2:5060 (UDP) - 6/21/2010 3:22:17 PM

INVITE sip:ua2@172.27.14.2 SIP/2.0 <---- Request URI
Via: SIP/2.0/UDP 172.27.14.3:5060;branch=z9hG4bK-181372
Via: SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3;received=172.27.14.4
From: ua1 ;tag=7128SIPpTag07b1
To: ua2 should be 172.27.14.2 ???
Call-ID: 1-7128@172.27.14.4
CSeq: 1 INVITE
Contact: sip:ua1@172.27.14.4:5060
Max-Forwards: 69
Subject: Performance Test
Record-Route:
Content-Type: application/sdp
Content-Length: 131
v=0
o=user1 53655765 2353687637 IN IP4 172.27.14.4
s=-
c=IN IP4 172.27.14.4
t=0 0
m=audio 6000 RTP/AVP 0

Topic "not forwarding the ip to client" a message from sp.mohan

Tue, 22 Jun 2010 10:09:20 GMT

TekSIP forwards it to 172.27.14.2:5060 as expected;

SIP req. to : 172.27.14.2:5060 (UDP) - 6/21/2010 3:22:17 PM
INVITE sip:ua2@172.27.14.2 SIP/2.0
Via: SIP/2.0/UDP 172.27.14.3:5060;branch=z9hG4bK-181372
Via: SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3;received=172.27.14.4
From: ua1 ;tag=7128SIPpTag07b1
To: ua2 ua2@172.27.14.3:5060> should be 172.27.14.2 ???
Call-ID: 1-7128@172.27.14.4
CSeq: 1 INVITE
Contact: sip:ua1@172.27.14.4:5060
Max-Forwards: 69
Subject: Performance Test
Record-Route:
Content-Type: application/sdp
Content-Length: 131
v=0
o=user1 53655765 2353687637 IN IP4 172.27.14.4
s=-
c=IN IP4 172.27.14.4
t=0 0
m=audio 6000 RTP/AVP 0

can you confirm me is it right behavior?

Topic "not forwarding the ip to client" a message from admin

Tue, 22 Jun 2010 10:01:24 GMT

What is the configured domain for TekSIP? Is it 172.27.14.3? If so two endpoints are registered;

ua1 : 172.27.14.4:5060
ua2 : 172.27.14.2:5060

an INVITE message is destined to ua2. That means TekSIP will forward it to 172.27.14.2:5060;

SIP req. from : 172.27.14.4:5060 (UDP) - 6/21/2010 3:22:17 PM
INVITE sip:ua2@172.27.14.3 SIP/2.0
[Via] = SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3
[From] = ua1 ;tag=7128SIPpTag07b1
[To] = ua2
[Call-ID] = 1-7128@172.27.14.4
[CSeq] = 1 INVITE
[Contact] = sip:ua1@172.27.14.4:5060
[Max-Forwards] = 70
[Subject] = Performance Test
[Content-Type] = application/sdp
[Content-Length] = 131
v=0
o=user1 53655765 2353687637 IN IP4 172.27.14.4
s=-
c=IN IP4 172.27.14.4
t=0 0
m=audio 6000 RTP/AVP 0

and TekSIP forwards it to 172.27.14.2:5060 as expected;

SIP req. to : 172.27.14.2:5060 (UDP) - 6/21/2010 3:22:17 PM
INVITE sip:ua2@172.27.14.2 SIP/2.0
Via: SIP/2.0/UDP 172.27.14.3:5060;branch=z9hG4bK-181372
Via: SIP/2.0/UDP 172.27.14.4:5060;branch=z9hG4bK-7128-1-3;received=172.27.14.4
From: ua1 ;tag=7128SIPpTag07b1
To: ua2
Call-ID: 1-7128@172.27.14.4
CSeq: 1 INVITE
Contact: sip:ua1@172.27.14.4:5060
Max-Forwards: 69
Subject: Performance Test
Record-Route:
Content-Type: application/sdp
Content-Length: 131
v=0
o=user1 53655765 2353687637 IN IP4 172.27.14.4
s=-
c=IN IP4 172.27.14.4
t=0 0
m=audio 6000 RTP/AVP 0

same behavior can be observed in Wireshark log.

What is the problem?

Topic "not forwarding the ip to client" a message from admin

Mon, 21 Jun 2010 17:16:54 GMT

Hi,

As far as I see from the log TekSIP forwards incoming INVITE to 172.127.14.2 as expected. Can you also send me a Wireshark log?

Best regards,

Yasin KAPLAN

Topic "invalid format of SIP header" a message from admin

Mon, 21 Jun 2010 17:13:53 GMT

I was a special built and I has been deleted.

Topic "invalid format of SIP header" a message from sp.mohan

Mon, 21 Jun 2010 13:23:34 GMT

can i get teksip-M.zip?

Topic "not forwarding the ip to client" a message from sp.mohan

Mon, 21 Jun 2010 13:13:01 GMT

hello

i am using the sipp call simulator.

ua1:172.27.14.4
teksip:172.27.14.3
ua2:172.27.14.2
teksip forwarding the inivite message with 172.27.14.4 to 172.27.14.3 instead of 172.27.14.4 to 172.27.14.2.
attaching teksip.log

Please check in inivite message "TO" filed. attaching snapshot

br
mohan.S
edited by sp.mohan on 22.06.2010