03.03.2010 15:43:45
Rik
Posts: 7
|
Hi,
in attachment you will find a trace. There seems to be something wrong with the 2nd invite. My Sip client doesn't like this invite. (cannot decode)
Is this a bug in your program?
Rik
|
|
• permalink
• reply with quote
|
04.03.2010 09:55:01
admin
Administrator
Posts: 106
|
Hi,
Is it possible you to send me also TekSIP.log after setting log level to debug at Settings / Service parameters?
Best regards,
Yasin KAPLAN
|
|
• permalink
• reply with quote
|
04.03.2010 10:35:09
Rik
Posts: 7
|
@font-face { font-family: FuturaA Bk BT;}@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; }P.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "FuturaA Bk BT"}LI.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "FuturaA Bk BT"}DIV.MsoNormal { FONT-SIZE: 11pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "FuturaA Bk BT"}A:link { COLOR: blue; TEXT-DECORATION: underline}SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline}A:visited { COLOR: #606420; TEXT-DECORATION: underline}SPAN.MsoHyperlinkFollowed { COLOR: #606420; TEXT-DECORATION: underline}SPAN.EmailStyle17 { COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose}DIV.Section1 { page: Section1}
I think the problem is quite clear. the proxy removes the body of the message.
The headerpart is separated from the bodypart via a double CRLF.
|
|
• permalink
• reply with quote
|
04.03.2010 12:36:35
admin
Administrator
Posts: 106
|
Is TekSIP configured for ims.belab.com domain and endpoint 027590171 registered to TekSIP?
|
|
• permalink
• reply with quote
|
04.03.2010 13:21:54
Rik
Posts: 7
|
yes and yes. I think there is somewhere a missing CRLF in the invite from TEKSIP.
|
|
• permalink
• reply with quote
|
04.03.2010 13:39:13
admin
Administrator
Posts: 106
|
Yes, there is a problem with INVITE processing of TekSIP. I'm trying to understand your case. Does the domain name has a valid DNS entry and it's accessible for TekSIP?
|
|
• permalink
• reply with quote
|
04.03.2010 14:11:51
Rik
Posts: 7
|
My system cannot decode the invite coming from TEKSIP. No problem with DNS.
|
|
• permalink
• reply with quote
|
04.03.2010 17:23:31
Rik
Posts: 7
|
According to the RFC : the bodypart must be seperated by the header part with a CR/LF sequence. This seems to be missing in TEKSIP's invite.
|
|
• permalink
• reply with quote
|
05.03.2010 08:52:37
admin
Administrator
Posts: 106
|
Which versiopn of TekSIP are you testing? Is it the latest build which is available on TekSIP web site?
|
|
• permalink
• reply with quote
|
05.03.2010 10:01:22
Rik
Posts: 7
|
yes. I have downloaded this version some days ago. (v2.6)
|
|
• permalink
• reply with quote
|
05.03.2010 11:05:58
admin
Administrator
Posts: 106
|
Hi,
I think I've found the cause of the problem. Please download http://www.teksip.com/release/TekSIP-M.zip and replace existing TekSIP.exe
Let me know the result.
|
|
• permalink
• reply with quote
|
08.03.2010 09:11:50
Rik
Posts: 7
|
the problem is solved. Thanks.
|
|
• permalink
• reply with quote
|
08.03.2010 10:59:04
admin
Administrator
Posts: 106
|
You welcome
|
|
• permalink
• reply with quote
|
21.06.2010 13:23:34
sp.mohan
Posts: 6
|
can i get teksip-M.zip?
|
|
• permalink
• reply with quote
|
21.06.2010 17:13:53
admin
Administrator
Posts: 106
|
I was a special built and I has been deleted.
|
|
• permalink
• reply with quote
|