Contents of Devel digest multi-domain roamning

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Contents of Devel digest multi-domain roamning

zhangchao00001
Dear sir: 
              NAT
Register: C1--------->P2-------->P1
case 1: P1 send the Response message directly to C1. Because C1 dosen't connect with P1 directly, the NAT will block the message, it will not reach C1
case 2: P1 send the response message to P2. Because P2 dosen't have C1's address, it will reply "404 Not Found error" message
In both cases, C2 will not telephone with C1 sucessfully. We suppose that C1 must register to P1 through P2
 C1        NAT         P2       P1        C2
  |         |          |        |         |
  | INVITE  |          |        |         |
  |-------->|--------->|        |         |
  |         |          |------->|         |
  |         |          |        |-------->|
  |         |          |        |         |
C1 dosen't register to P1 directly but through P2, so P1 will not reach C1 directly which will be blocked by NAT, it need forward the message to P2 firstly. However, P2 dosen't have the C1 address in its database, it reply "404 Not Found error" .How to make the phone ?

在2009-09-11,[hidden email] 写道:
>Send Devel mailing list submissions to
>	[hidden email]
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>or, via email, send a message with subject or body 'help' to
>	[hidden email]
>
>You can reach the person managing the list at
>	[hidden email]
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Devel digest..."
>
>
>Today's Topics:
>
>   1. questions about inter-domain roaming (zhangchao00001)
>   2. Re: questions about inter-domain roaming (Thomas Gelf)
>   3. Test results for per-branch reply routes (Thomas Gelf)
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Fri, 11 Sep 2009 08:40:26 +0800 (CST)
>From: zhangchao00001 <[hidden email]>
>Subject: [OpenSIPS-Devel] questions about inter-domain roaming
>To: opensip-devel <[hidden email]>
>Message-ID:
>	<[hidden email]>
>Content-Type: text/plain; charset="gbk"
>
>
>
>Hello everybody, I have some questions about Inter-domain Roaming.
>________________________________
>|                               | 
>|     C1@DomainA  C3@DomainB    |
>|_______________________________|           
>|_____________NAT_______________|Domain B
>|                               |
>|_____________P2________________|
>               |       
>               |
>               |
>     __________|___________
>     |                    |
>     |     P1(S1)         |
>     |                    |           
>     |                    |
>     |     C2@DomainA     |
>     |____________________|
>            Domain A
>Here is my experiment environment(the picture above):there are two Domains A and B, C1?C2 belong to Domain A, C3 to Domain B, P1 and P2 are proxy server. C1 roams in Domain B and register to P1 through P2. then C2 want to make a telephone to C1, C1 and C3 have the private ip address and connect to P2 throught nat(port reserved) device. I want to ask how to write the correct config file to make the call? Because P2 dosen't have the C1 in its location table, when the Invite message come to P2, P2 dosen't know where to send the Invite message. if P1 send the Invite message to C1 directly, the nat device will block it.
>-------------- next part --------------
>An HTML attachment was scrubbed...
>URL: http://lists.opensips.org/pipermail/devel/attachments/20090911/c17b6a3c/attachment.html 
>
>------------------------------
>
>Message: 2
>Date: Fri, 11 Sep 2009 02:55:42 +0200
>From: Thomas Gelf <[hidden email]>
>Subject: Re: [OpenSIPS-Devel] questions about inter-domain roaming
>To: [hidden email]
>Message-ID: <h8c76d$up3$[hidden email]>
>Content-Type: text/plain; charset=UTF-8
>
>zhangchao00001 wrote:
>> Hello everybody, I have some questions about Inter-domain Roaming.
>> ...
>> Here is my experiment environment(the picture above):there are two
>> Domains A and B, C1?C2 belong to Domain A, C3 to Domain B, P1 and P2
>> are proxy server. C1 roams in Domain B and register to P1 through P2.
>> then C2 want to make a telephone to C1...
>
>It doesn't matter where C1 is to be found, it will always be registered
>to P1. P1 will be able to reach it, takes care of keepalives, NAT fixes
>etc. Both P1 and P2 shall obviously record_route. Doing so C2 will
>always be able to call C1 (using it's proxy P1).
>
>If C3 wants to call C1 (belonging to a foreign domain) it shall use P2
>as outbound proxy, P2 will look up C1's domain (eventually repecting
>SRV records) and send the call to P1. As we learned before, P1 will
>be able to contact C1.
>
>There will be no SIP packets from peer to peer, if you allow that (and
>don't record_route) you will be lost.
>
>Best regards,
>Thomas Gelf
>
>-- 
> mail: [hidden email]
>  web: http://thomas.gelf.net/
>
>
>
>
>------------------------------
>
>Message: 3
>Date: Fri, 11 Sep 2009 05:58:46 +0200
>From: Thomas Gelf <[hidden email]>
>Subject: [OpenSIPS-Devel] Test results for per-branch reply routes
>To: [hidden email]
>Message-ID: <h8chtj$j4g$[hidden email]>
>Content-Type: text/plain; charset=ISO-8859-15
>
>Hi All,
>
>I can report that it works like a charme, as it has been promised!
>Tried forking call to NAT and non-NAT UAC, uac_replac_both branches,
>short: all kind of bad stuff ;-)
>
>The only thing I discovered failing badly: uac_replace_to works if
>called in a branch route - however if there are multiple branches
>restoring To: in reply packets fails badly.
>
>Best regards,
>Thomas Gelf
>
>-- 
> mail: [hidden email]
>  web: http://thomas.gelf.net/
>
>
>
>
>------------------------------
>
>_______________________________________________
>Devel mailing list
>[hidden email]
>http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>
>
>End of Devel Digest, Vol 15, Issue 19
>*************************************



"中国制造",讲述中国60年往事

_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Reply | Threaded
Open this post in threaded view
|

Re: Contents of Devel digest multi-domain roamning

Bogdan-Andrei Iancu
Hi,

if the request went C1 -> P2 -> P1, the replies will go exactly the same
way (backwards) as the requests.

So for replies, everything should work.

For registering through a proxy (like C1 registering with P1 via P2), in
SIP, there are 2 ways to go:
1) step by step registration: C1 registers with P2 (P2 will have C1
contact) and P2 registers with P1 (P1 will have P2 contact)
2) use PATH support

Regards,
Bogdan

zhangchao00001 wrote:

> Dear sir:
> NAT
> Register: C1--------->P2-------->P1
> case 1: P1 send the Response message directly to C1. Because C1
> dosen't connect with P1 directly, the NAT will block the message, it
> will not reach C1
> case 2: P1 send the response message to P2. Because P2 dosen't have
> C1's address, it will reply "404 Not Found error" message
> In both cases, C2 will not telephone with C1 sucessfully. We suppose
> that C1 must register to P1 through P2
> C1 NAT P2 P1 C2
> | | | | |
> | INVITE | | | |
> |-------->|--------->| | |
> | | |------->| |
> | | | |-------->|
> | | | | |
> C1 dosen't register to P1 directly but through P2, so P1 will not
> reach C1 directly which will be blocked by NAT, it need forward the
> message to P2 firstly. However, P2 dosen't have the C1 address in its
> database, it reply "404 Not Found error" .How to make the phone ?
>
> 在2009-09-11,[hidden email] <mailto:[hidden email]> 写道:
> >Send Devel mailing list submissions to
> > [hidden email] <mailto:[hidden email]>
> >
> >To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
> >or, via email, send a message with subject or body 'help' to
> > [hidden email] <mailto:[hidden email]>
> >
> >You can reach the person managing the list at
> > [hidden email] <mailto:[hidden email]>
> >
> >When replying, please edit your Subject line so it is more specific
> >than "Re: Contents of Devel digest..."
> >
> >
> >Today's Topics:
> >
> >   1. questions about inter-domain roaming (zhangchao00001)
> >   2. Re: questions about inter-domain roaming (Thomas Gelf)
> >   3. Test results for per-branch reply routes (Thomas Gelf)
> >
> >
> >----------------------------------------------------------------------
> >
> >Message: 1
> >Date: Fri, 11 Sep 2009 08:40:26 +0800 (CST)
> >From: zhangchao00001 <[hidden email] <mailto:[hidden email]>>
> >Subject: [OpenSIPS-Devel] questions about inter-domain roaming
> >To: opensip-devel <[hidden email] <mailto:[hidden email]>>
> >Message-ID:
> > <[hidden email] <mailto:[hidden email]>>
> >Content-Type: text/plain; charset="gbk"
> >
> >
> >
> >Hello everybody, I have some questions about Inter-domain Roaming.
> >________________________________
> >|                               |
> >|     C1@DomainA  C3@DomainB    |
> >|_______________________________|          
> >|_____________NAT_______________|Domain B
> >|                               |
> >|_____________P2________________|
> >               |      
> >               |
> >               |
> >     __________|___________
> >     |                    |
> >     |     P1(S1)         |
> >     |                    |          
> >     |                    |
> >     |     C2@DomainA     |
> >     |____________________|
> >            Domain A
> >Here is my experiment environment(the picture above):there are two Domains A and B, C1?C2 belong to Domain A, C3 to Domain B, P1 and P2 are proxy server. C1 roams in Domain B and register to P1 through P2. then C2 want to make a telephone to C1, C1 and C3 have the private ip address and connect to P2 throught nat(port reserved) device. I want to ask how to write the correct config file to make the call? Because P2 dosen't have the C1 in its location table, when the Invite message come to P2, P2 dosen't know where to send the Invite message. if P1 send the Invite message to C1 directly, the nat device will block it.
> >-------------- next part --------------
> >An HTML attachment was scrubbed...
> >URL: http://lists.opensips.org/pipermail/devel/attachments/20090911/c17b6a3c/attachment.html 
> >
> >------------------------------
> >
> >Message: 2
> >Date: Fri, 11 Sep 2009 02:55:42 +0200
> >From: Thomas Gelf <[hidden email] <mailto:[hidden email]>>
> >Subject: Re: [OpenSIPS-Devel] questions about inter-domain roaming
> >To: [hidden email] <mailto:[hidden email]>
> >Message-ID: <h8c76d$up3$[hidden email] <mailto:[hidden email]>>
> >Content-Type: text/plain; charset=UTF-8
> >
> >zhangchao00001 wrote:
> >> Hello everybody, I have some questions about Inter-domain Roaming.
> >> ...
> >> Here is my experiment environment(the picture above):there are two
> >> Domains A and B, C1?C2 belong to Domain A, C3 to Domain B, P1 and P2
> >> are proxy server. C1 roams in Domain B and register to P1 through P2.
> >> then C2 want to make a telephone to C1...
> >
> >It doesn't matter where C1 is to be found, it will always be registered
> >to P1. P1 will be able to reach it, takes care of keepalives, NAT fixes
> >etc. Both P1 and P2 shall obviously record_route. Doing so C2 will
> >always be able to call C1 (using it's proxy P1).
> >
> >If C3 wants to call C1 (belonging to a foreign domain) it shall use P2
> >as outbound proxy, P2 will look up C1's domain (eventually repecting
> >SRV records) and send the call to P1. As we learned before, P1 will
> >be able to contact C1.
> >
> >There will be no SIP packets from peer to peer, if you allow that (and
> >don't record_route) you will be lost.
> >
> >Best regards,
> >Thomas Gelf
> >
> >--
> > mail: [hidden email] <mailto:[hidden email]>
> >  web: http://thomas.gelf.net/
> >
> >
> >
> >
> >------------------------------
> >
> >Message: 3
> >Date: Fri, 11 Sep 2009 05:58:46 +0200
> >From: Thomas Gelf <[hidden email] <mailto:[hidden email]>>
> >Subject: [OpenSIPS-Devel] Test results for per-branch reply routes
> >To: [hidden email] <mailto:[hidden email]>
> >Message-ID: <h8chtj$j4g$[hidden email] <mailto:[hidden email]>>
> >Content-Type: text/plain; charset=ISO-8859-15
> >
> >Hi All,
> >
> >I can report that it works like a charme, as it has been promised!
> >Tried forking call to NAT and non-NAT UAC, uac_replac_both branches,
> >short: all kind of bad stuff ;-)
> >
> >The only thing I discovered failing badly: uac_replace_to works if
> >called in a branch route - however if there are multiple branches
> >restoring To: in reply packets fails badly.
> >
> >Best regards,
> >Thomas Gelf
> >
> >--
> > mail: [hidden email] <mailto:[hidden email]>
> >  web: http://thomas.gelf.net/
> >
> >
> >
> >
> >------------------------------
> >
> >_______________________________________________
> >Devel mailing list
> >[hidden email] <mailto:[hidden email]>
> >http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
> >
> >
> >End of Devel Digest, Vol 15, Issue 19
> >*************************************
>  
>
>
> ------------------------------------------------------------------------
> "中国制造 ",讲述中国60年往事
> <http://news.163.com/madeinchina/index.html?from=mailfooter>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>  


_______________________________________________
Devel mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel