[Serusers] Ser as a presence server with other SIP proxy asregistrar and rtp proxy
Vaclav Kubart
vaclav.kubart at iptel.org
Tue Apr 4 17:20:04 CEST 2006
Hi,
I tried to forward message to other port than 5060 and it was realy
forwarded there, thus t_forward_nonack really works.
Vaclav
On Fri, Mar 31, 2006 at 05:38:24PM +0300, ?lker Aktuna (Koç.net) wrote:
> Hi again,
>
> I think I've found the problem. The client doesn't receive the packet from server because of network problems.
> So I had to change the SIP port of my SIP Proxy to 5061
>
> Now , following forward command does not work (SER still sends to 5060) , why ?
>
> if (!t_forward_nonack("193.243.202.97", 5061)) {
> log(1, "forward failed\n");
> t_reply("500", "Forward failed");
> }
>
> Thanks,
> ilker
>
>
> ________________________________
>
> From: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org] On Behalf Of ?lker Aktuna (Koç.net)
> Sent: Friday, March 31, 2006 3:21 PM
> To: Vaclav Kubart
> Cc: serusers at lists.iptel.org
> Subject: RE: [Serusers] Ser as a presence server with other SIP proxy asregistrar and rtp proxy
>
>
>
> Hi Vaclav,
>
> Thanks for the information.
> I changed my configuration for REGISTER messages and they were forwarded to my SIP proxy.
> But the clien't can't connect. I think that's because of authentication requirement on my SIP proxy.
>
> When I make the client connect directly to my SIP proxy I see the following SIP header on it:
>
> 12:09:22.967260: SIP: 193.243.202.97:5060 << 85.105.102.167:8359 payload: 792 bytes
> REGISTER sip:193.243.202.97 SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.6:8359;branch=z9hG4bK-d87543-c2540260b6061b1e-1--d87543-;rport
> Max-Forwards: 70
> Contact: <sip:200000900568888888 at 192.168.2.6:8359;rinstance=c314db726308b27a>
> To: "900568888888"<sip:200000900568888888 at 193.243.202.97>
> From: "900568888888"<sip:200000900568888888 at 193.243.202.97>;tag=f72f1c2c
> Call-ID: 2748934b5d115c55 at TkVUV09SS1lPTi5jb21wYW55MS50c3Q.
> CSeq: 2 REGISTER
> Expires: 3600
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
> Supported: eventlist
> User-Agent: eyeBeam release 3014w stamp 26359
> Authorization: Digest username="200000900568888888",realm="NcxSip",nonce="48058627",uri="sip:193.243.202.97",response="92be0838ca4f794d23d4bb3d34e12aa9",algorithm=MD5
> Content-Length: 0
>
> 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:
>
> 12:16:42.263635: SIP: 193.243.202.97:5060 << 193.243.207.107:10003 payload: 716 bytes
> REGISTER sip:193.243.202.97 SIP/2.0
> Via: SIP/2.0/UDP 10.100.100.15;branch=z9hG4bKcee1.8c792d45.0
> Via: SIP/2.0/UDP 192.168.2.6:8359;received=85.105.102.167;branch=z9hG4bK-d87543-aa1ee14dcf543535-1--d87543-;rport=10002
> Max-Forwards: 16
> Contact: <sip:200000900568888888 at 192.168.2.6:8359;rinstance=2c28e04a9c62f011>
> To: "900568888888"<sip:200000900568888888 at 193.243.202.97>
> From: "900568888888"<sip:200000900568888888 at 193.243.202.97>;tag=d37fe827
> Call-ID: 6d7923631c258f31 at TkVUV09SS1lPTi5jb21wYW55MS50c3Q.
> CSeq: 1 REGISTER
> Expires: 3600
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
> Supported: eventlist
> User-Agent: eyeBeam release 3014w stamp 26359
> Content-Length: 0
>
> It seems that when the SIP message is forwarded through SER, the Authorization information is missing.
> How can I make SER to forward the message without modifying the message ?
>
> Also how can I modify user and domain information for the forwarded messages ?
>
> Thanks,
> ilker
>
> -----Original Message-----
> From: Vaclav Kubart [mailto:vaclav.kubart at iptel.org]
> Sent: Friday, March 31, 2006 8:37 AM
> To: ?lker Aktuna (Koç.net)
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] Ser as a presence server with other SIP proxy as registrar and rtp proxy
>
> Hi,
> your solution is possible - separated presence server from other SIP communication. For forwarding you need cfg like this:
>
> if (method=="...") { # here put method name which should be forwarded
> if (!t_newtran()) {
> log(1, "newtran error\n");
> sl_reply_error();
> break;
> };
>
> if (!t_forward_nonack("machine.domain.com", 5060)) {
> log(1, "forward failed\n");
> t_reply("500", "Forward failed");
> }
> break;
> }
>
> I'm using SER as proxy and other SER as presence server. Proxy forwards presence related messages to presence server, it looks like:
>
>
> C "-//W3C//DTD HTML 4.0 Transitional//EN">
> Hi again,
>
> I think I've found the problem. The client doesn't receive the packet from server because of network problems.
> So I had to change the SIP port of my SIP Proxy to 5061
>
> Now , following forward command does not work (SER still sends to 5060) , why ?
>
> if (!t_forward_nonack("193.243.202.97", 5061)) {
> log(1, "forward failed\n");
> t_reply("500", "Forward failed");
> }
>
> Thanks,
> ilker
>
>
> ________________________________
>
> From: serusers-bounces at iptel.org [mailto:serusers-bounces at lists.iptel.org] On Behalf Of ?lker Aktuna (Koç.net)
> Sent: Friday, March 31, 2006 3:21 PM
> To: Vaclav Kubart
> Cc: serusers at lists.iptel.org
> Subject: RE: [Serusers] Ser as a presence server with other SIP proxy asregistrar and rtp proxy
>
>
>
> Hi Vaclav,
>
> Thanks for the information.
> I changed my configuration for REGISTER messages and they were forwarded to my SIP proxy.
> But the clien't can't connect. I think that's because of authentication requirement on my SIP proxy.
>
> When I make the client connect directly to my SIP proxy I see the following SIP header on it:
>
> 12:09:22.967260: SIP: 193.243.202.97:5060 << 85.105.102.167:8359 payload: 792 bytes
> REGISTER sip:193.243.202.97 SIP/2.0
> Via: SIP/2.0/UDP 192.168.2.6:8359;branch=z9hG4bK-d87543-c2540260b6061b1e-1--d87543-;rport
> Max-Forwards: 70
> Contact: <sip:200000900568888888 at 192.168.2.6:8359;rinstance=c314db726308b27a>
> To: "900568888888"<sip:200000900568888888 at 193.243.202.97>
> From: "900568888888"<sip:200000900568888888 at 193.243.202.97>;tag=f72f1c2c
> Call-ID: 2748934b5d115c55 at TkVUV09SS1lPTi5jb21wYW55MS50c3Q.
> CSeq: 2 REGISTER
> Expires: 3600
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
> Supported: eventlist
> User-Agent: eyeBeam release 3014w stamp 26359
> Authorization: Digest username="200000900568888888",realm="NcxSip",nonce="48058627",uri="sip:193.243.202.97",response="92be0838ca4f794d23d4bb3d34e12aa9",algorithm=MD5
> Content-Length: 0
>
> 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:
>
> 12:16:42.263635: SIP: 193.243.202.97:5060 << 193.243.207.107:10003 payload: 716 bytes
> REGISTER sip:193.243.202.97 SIP/2.0
> Via: SIP/2.0/UDP 10.100.100.15;branch=z9hG4bKcee1.8c792d45.0
> Via: SIP/2.0/UDP 192.168.2.6:8359;received=85.105.102.167;branch=z9hG4bK-d87543-aa1ee14dcf543535-1--d87543-;rport=10002
> Max-Forwards: 16
> Contact: <sip:200000900568888888 at 192.168.2.6:8359;rinstance=2c28e04a9c62f011>
> To: "900568888888"<sip:200000900568888888 at 193.243.202.97>
> From: "900568888888"<sip:200000900568888888 at 193.243.202.97>;tag=d37fe827
> Call-ID: 6d7923631c258f31 at TkVUV09SS1lPTi5jb21wYW55MS50c3Q.
> CSeq: 1 REGISTER
> Expires: 3600
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
> Supported: eventlist
> User-Agent: eyeBeam release 3014w stamp 26359
> Content-Length: 0
>
> It seems that when the SIP message is forwarded through SER, the Authorization information is missing.
> How can I make SER to forward the message without modifying the message ?
>
> Also how can I modify user and domain information for the forwarded messages ?
>
> Thanks,
> ilker
>
> -----Original Message-----
> From: Vaclav Kubart [mailto:vaclav.kubart at iptel.org]
> Sent: Friday, March 31, 2006 8:37 AM
> To: ?lker Aktuna (Koç.net)
> Cc: serusers at lists.iptel.org
> Subject: Re: [Serusers] Ser as a presence server with other SIP proxy as registrar and rtp proxy
>
> Hi,
> your solution is possible - separated presence server from other SIP communication. For forwarding you need cfg like this:
>
> if (method=="...") { # here put method name which should be forwarded
> if (!t_newtran()) {
> log(1, "newtran error\n");
> sl_reply_error();
> break;
> };
>
> if (!t_forward_nonack("machine.domain.com", 5060)) {
> log(1, "forward failed\n");
> t_reply("500", "Forward failed");
> }
> break;
> }
>
> I'm using SER as proxy and other SER as presence server. Proxy forwards presence related messages to presence server, it looks like:
>
>
>
>
>
> <http://387555.sigclick.mailinfo.com/sigclick/03090F04/06044907/014D0A10181315.jpg>
> _____________________________________________________________________________________________________________________________________________
> 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.
> 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.
> _____________________________________________________________________________________________________________________________________________
More information about the sr-users
mailing list