<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-16"><TITLE></TITLE>
<META http-equiv=EXPIRES content=0>
<META http-equiv=EXPIRESABSOLUTE content="Tue, 01 Jun 1999 12:00:00 GMT">
<META http-equiv=PRAGMA content=NO-CACHE>
<META http-equiv=CACHE-CONTROL content=PRIVATE>
<META http-equiv=CACHE-CONTROL content=NO-CACHE>
<META content="MSHTML 6.00.2900.2838" name=GENERATOR></HEAD>
<BODY >
<DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>Hi again,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>I think I've found the problem. The client doesn't
receive the packet from server because of network problems.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>So I had to change the SIP port of my SIP Proxy to
5061</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>Now , following forward command does not work (SER
still sends to 5060) , why ?</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>
if (!t_forward_nonack("193.243.202.97", 5061))
{<BR>
log(1, "forward
failed\n");<BR>
t_reply("500", "Forward
failed");<BR>
}</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=605093314-31032006><FONT face=Arial color=#0000ff
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=605093314-31032006><FONT face=Arial color=#0000ff
size=2>ilker</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> serusers-bounces@lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] <B>On Behalf Of </B>İlker Aktuna
(Koç.net)<BR><B>Sent:</B> Friday, March 31, 2006 3:21 PM<BR><B>To:</B> Vaclav
Kubart<BR><B>Cc:</B> serusers@lists.iptel.org<BR><B>Subject:</B> RE: [Serusers] Ser as
a presence server with other SIP proxy asregistrar and rtp
proxy<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><!-- Converted from text/plain format -->
<P><FONT size=2>Hi Vaclav,<BR><BR>Thanks for the information. <BR>I changed
my configuration for REGISTER messages and they were forwarded to my SIP
proxy.<BR>But the clien't can't connect. I think that's because of
authentication requirement on my SIP proxy.<BR><BR>When I make the client
connect directly to my SIP proxy I see the following SIP header on
it:<BR><BR>12:09:22.967260: SIP:
193.243.202.97:5060
<<
85.105.102.167:8359 payload: 792 bytes<BR>REGISTER
sip:193.243.202.97 SIP/2.0<BR>Via: SIP/2.0/UDP
192.168.2.6:8359;branch=z9hG4bK-d87543-c2540260b6061b1e-1--d87543-;rport<BR>Max-Forwards:
70<BR>Contact:
<sip:200000900568888888@192.168.2.6:8359;rinstance=c314db726308b27a><BR>To:
"900568888888"<sip:200000900568888888@193.243.202.97><BR>From:
"900568888888"<sip:200000900568888888@193.243.202.97>;tag=f72f1c2c<BR>Call-ID:
2748934b5d115c55@TkVUV09SS1lPTi5jb21wYW55MS50c3Q.<BR>CSeq: 2
REGISTER<BR>Expires: 3600<BR>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
NOTIFY, MESSAGE, SUBSCRIBE, INFO<BR>Supported: eventlist<BR>User-Agent: eyeBeam
release 3014w stamp 26359<BR>Authorization: Digest
username="200000900568888888",realm="NcxSip",nonce="48058627",uri="sip:193.243.202.97",response="92be0838ca4f794d23d4bb3d34e12aa9",algorithm=MD5<BR>Content-Length:
0<BR><BR>But if I make the client connect to SER and then forward the REGISTER
message to my SIP proxy, I see the following SIP header
arriving:<BR><BR>12:16:42.263635: SIP:
193.243.202.97:5060
<< 193.243.207.107:10003
payload: 716 bytes<BR>REGISTER sip:193.243.202.97 SIP/2.0<BR>Via: SIP/2.0/UDP
10.100.100.15;branch=z9hG4bKcee1.8c792d45.0<BR>Via: SIP/2.0/UDP
192.168.2.6:8359;received=85.105.102.167;branch=z9hG4bK-d87543-aa1ee14dcf543535-1--d87543-;rport=10002<BR>Max-Forwards:
16<BR>Contact:
<sip:200000900568888888@192.168.2.6:8359;rinstance=2c28e04a9c62f011><BR>To:
"900568888888"<sip:200000900568888888@193.243.202.97><BR>From:
"900568888888"<sip:200000900568888888@193.243.202.97>;tag=d37fe827<BR>Call-ID:
6d7923631c258f31@TkVUV09SS1lPTi5jb21wYW55MS50c3Q.<BR>CSeq: 1
REGISTER<BR>Expires: 3600<BR>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
NOTIFY, MESSAGE, SUBSCRIBE, INFO<BR>Supported: eventlist<BR>User-Agent: eyeBeam
release 3014w stamp 26359<BR>Content-Length: 0<BR><BR>It seems that when the SIP
message is forwarded through SER, the Authorization information is
missing.<BR>How can I make SER to forward the message without modifying the
message ?<BR><BR>Also how can I modify user and domain information for the
forwarded messages ?<BR><BR>Thanks,<BR>ilker<BR><BR>-----Original
Message-----<BR>From: Vaclav Kubart [<A
href="mailto:vaclav.kubart@iptel.org">mailto:vaclav.kubart@iptel.org</A>]<BR>Sent:
Friday, March 31, 2006 8:37 AM<BR>To: İlker Aktuna (Koç.net)<BR>Cc:
serusers@lists.iptel.org<BR>Subject: Re: [Serusers] Ser as a presence server with
other SIP proxy as registrar and rtp proxy<BR><BR>Hi,<BR>your solution is
possible - separated presence server from other SIP communication. For
forwarding you need cfg like
this:<BR><BR> if (method=="...") { #
here put method name which should be
forwarded<BR>
if (!t_newtran())
{<BR>
log(1, "newtran
error\n");<BR>
sl_reply_error();<BR>
break;<BR>
};<BR>
<BR>
if
(!t_forward_nonack("machine.domain.com", 5060))
{<BR>
log(1, "forward
failed\n");<BR>
t_reply("500", "Forward
failed");<BR>
}<BR>
break;<BR> }<BR><BR>I'm using SER as
proxy and other SER as presence server. Proxy forwards presence related messages
to presence server, it looks
like:<BR></FONT></P>C "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=EXPIRES content=0>
<META http-equiv=EXPIRESABSOLUTE content="Tue, 01 Jun 1999 12:00:00 GMT">
<META http-equiv=PRAGMA content=NO-CACHE>
<META http-equiv=CACHE-CONTROL content=PRIVATE>
<META http-equiv=CACHE-CONTROL content=NO-CACHE>
<META content="MSHTML 6.00.2900.2838" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>Hi again,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>I think I've found the problem. The client doesn't
receive the packet from server because of network problems.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>So I had to change the SIP port of my SIP Proxy to
5061</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>Now , following forward command does not work (SER
still sends to 5060) , why ?</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=605093314-31032006>
if (!t_forward_nonack("193.243.202.97", 5061))
{<BR>
log(1, "forward
failed\n");<BR>
t_reply("500", "Forward
failed");<BR>
}</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=605093314-31032006><FONT face=Arial color=#0000ff
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=605093314-31032006><FONT face=Arial color=#0000ff
size=2>ilker</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> serusers-bounces@lists.iptel.org
[mailto:serusers-bounces@lists.iptel.org] <B>On Behalf Of </B>İlker Aktuna
(Koç.net)<BR><B>Sent:</B> Friday, March 31, 2006 3:21 PM<BR><B>To:</B> Vaclav
Kubart<BR><B>Cc:</B> serusers@lists.iptel.org<BR><B>Subject:</B> RE: [Serusers] Ser as
a presence server with other SIP proxy asregistrar and rtp
proxy<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV><!-- Converted from text/plain format -->
<P><FONT size=2>Hi Vaclav,<BR><BR>Thanks for the information. <BR>I changed
my configuration for REGISTER messages and they were forwarded to my SIP
proxy.<BR>But the clien't can't connect. I think that's because of
authentication requirement on my SIP proxy.<BR><BR>When I make the client
connect directly to my SIP proxy I see the following SIP header on
it:<BR><BR>12:09:22.967260: SIP:
193.243.202.97:5060
<<
85.105.102.167:8359 payload: 792 bytes<BR>REGISTER
sip:193.243.202.97 SIP/2.0<BR>Via: SIP/2.0/UDP
192.168.2.6:8359;branch=z9hG4bK-d87543-c2540260b6061b1e-1--d87543-;rport<BR>Max-Forwards:
70<BR>Contact:
<sip:200000900568888888@192.168.2.6:8359;rinstance=c314db726308b27a><BR>To:
"900568888888"<sip:200000900568888888@193.243.202.97><BR>From:
"900568888888"<sip:200000900568888888@193.243.202.97>;tag=f72f1c2c<BR>Call-ID:
2748934b5d115c55@TkVUV09SS1lPTi5jb21wYW55MS50c3Q.<BR>CSeq: 2
REGISTER<BR>Expires: 3600<BR>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
NOTIFY, MESSAGE, SUBSCRIBE, INFO<BR>Supported: eventlist<BR>User-Agent: eyeBeam
release 3014w stamp 26359<BR>Authorization: Digest
username="200000900568888888",realm="NcxSip",nonce="48058627",uri="sip:193.243.202.97",response="92be0838ca4f794d23d4bb3d34e12aa9",algorithm=MD5<BR>Content-Length:
0<BR><BR>But if I make the client connect to SER and then forward the REGISTER
message to my SIP proxy, I see the following SIP header
arriving:<BR><BR>12:16:42.263635: SIP:
193.243.202.97:5060
<< 193.243.207.107:10003
payload: 716 bytes<BR>REGISTER sip:193.243.202.97 SIP/2.0<BR>Via: SIP/2.0/UDP
10.100.100.15;branch=z9hG4bKcee1.8c792d45.0<BR>Via: SIP/2.0/UDP
192.168.2.6:8359;received=85.105.102.167;branch=z9hG4bK-d87543-aa1ee14dcf543535-1--d87543-;rport=10002<BR>Max-Forwards:
16<BR>Contact:
<sip:200000900568888888@192.168.2.6:8359;rinstance=2c28e04a9c62f011><BR>To:
"900568888888"<sip:200000900568888888@193.243.202.97><BR>From:
"900568888888"<sip:200000900568888888@193.243.202.97>;tag=d37fe827<BR>Call-ID:
6d7923631c258f31@TkVUV09SS1lPTi5jb21wYW55MS50c3Q.<BR>CSeq: 1
REGISTER<BR>Expires: 3600<BR>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER,
NOTIFY, MESSAGE, SUBSCRIBE, INFO<BR>Supported: eventlist<BR>User-Agent: eyeBeam
release 3014w stamp 26359<BR>Content-Length: 0<BR><BR>It seems that when the SIP
message is forwarded through SER, the Authorization information is
missing.<BR>How can I make SER to forward the message without modifying the
message ?<BR><BR>Also how can I modify user and domain information for the
forwarded messages ?<BR><BR>Thanks,<BR>ilker<BR><BR>-----Original
Message-----<BR>From: Vaclav Kubart [<A
href="mailto:vaclav.kubart@iptel.org">mailto:vaclav.kubart@iptel.org</A>]<BR>Sent:
Friday, March 31, 2006 8:37 AM<BR>To: İlker Aktuna (Koç.net)<BR>Cc:
serusers@lists.iptel.org<BR>Subject: Re: [Serusers] Ser as a presence server with
other SIP proxy as registrar and rtp proxy<BR><BR>Hi,<BR>your solution is
possible - separated presence server from other SIP communication. For
forwarding you need cfg like
this:<BR><BR> if (method=="...") { #
here put method name which should be
forwarded<BR>
if (!t_newtran())
{<BR>
log(1, "newtran
error\n");<BR>
sl_reply_error();<BR>
break;<BR>
};<BR>
<BR>
if
(!t_forward_nonack("machine.domain.com", 5060))
{<BR>
log(1, "forward
failed\n");<BR>
t_reply("500", "Forward
failed");<BR>
}<BR>
break;<BR> }<BR><BR>I'm using SER as
proxy and other SER as presence server. Proxy forwards presence related messages
to presence server, it looks
like:<BR></FONT></P><!--445D5241795C--><BR></DIV>
<!--445D5241795C-->
<br><br><a href="http://387555.sigclick.mailinfo.com/sigclick/03090F04/06044907/014D0A10181315.jpg"><img src="http://387555.signature1.mailinfo.com/confirm2.6/03090F04/06044907/014D0A10181315.jpg" border="0" nosend="1"></a><!--445D5241795C//--></DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">Bu e-posta mesaji kisiye ozel olup, gizli bilgiler iceriyor olabilir. Eger bu e-posta mesaji size yanlislikla ulasmissa, icerigini hic bir sekilde kullanmayiniz ve ekli dosyalari acmayiniz. Bu durumda lutfen e-posta mesajini kullaniciya hemen geri gonderiniz ve tum kopyalarini mesaj kutunuzdan siliniz. Bu e-posta mesaji, hic bir sekilde, herhangi bir amac icin cogaltilamaz, yayinlanamaz ve para karsiligi satilamaz. Bu e-posta mesaji viruslere karsi anti-virus sistemleri tarafindan taranmistir. Ancak yollayici, bu e-posta mesajinin - virus koruma sistemleri ile kontrol ediliyor olsa bile - virus icermedigini garanti etmez ve meydana gelebilecek zararlardan dogacak hicbir sorumlulugu kabul etmez. </DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">This message is intended solely for the use of the individual or entity to whom it is addressed , and may contain confidential information. If you are not the intended recipient of this message or you receive this mail in error, you should refrain from making any use of the contents and from opening any attachment. In that case, please notify the sender immediately and return the message to the sender, then, delete and destroy all copies. This e-mail message, can not be copied, published or sold for any reason. This e-mail message has been swept by anti-virus systems for the presence of computer viruses. In doing so, however, sender cannot warrant that virus or other forms of data corruption may not be present and do not take any responsibility in any occurrence.</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana">_____________________________________________________________________________________________________________________________________________</DIV>
<DIV STYLE="FONT-SIZE: 7pt; COLOR: gray; FONT-FAMILY: verdana" ALIGN="justify">
</DIV>
</DIV>
</DIV></BODY></HTML>