<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body style="font-family: Calibri; font-size: 11pt;" 
text="#000000" bgcolor="#FFFFFF"><div style="font-size: 
11pt;font-family: Calibri;"><span><span><span><span style="font-family: 
Calibri;">I think I might  have resolved the issue to run media-proxy on
 multiple 
interfaces on the same machine.<br>Once I can confirm this is working 
will
 I elaborate on how I achieved this.</span> </span></span></span><br><br><span><span>I'm

 facing a problem though and it is as follows:<br><br>I'm registered via
 SIP Client on my Internal Network <a class="moz-txt-link-abbreviated" 
href="mailto:0839999989@41.218.72.25">0839999989@192.168.0.250</a>.<br><br>One
 
of the Carriers is registered to fake subscriber <a 
class="moz-txt-link-abbreviated" href="mailto:0839999999@41.218.72.69">0839999999@10.222.0.250</a>
 with Alias 44113001417.<br><br>I've made 100% sure that my re-write 
rule is set on both the subscribers.<br><br>I make call to 00</span></span><span><span><span>44113001417</span></span>
 </span><span><span></span><span><span></span>,
 but call fail with " No PSTN gateways available</span> " in the proxy 
log.<br><br>I'm also not 100% sure why it is not calling to the local 
hosted domain 10.222.0.250</span><span>?<br><br>The LB is listening on 
10.222.0.250:6090</span>.<br><span><br>Attached the output of the call 
within the proxy log.<br><br><br>Thanks
 again for any assistance.<br> </span><br>Kind Regards<br>Deon<br><blockquote
 style="border: 0px none;" cite="mid:20130419001454.3c58eedf@quenya" 
type="cite"><div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
 style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px">       <div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="jbonilla@sipwise.com" photoname="Jon Bonilla (Manwe)" 
src="cid:part1.05070409.04030407@gmail.com" name="postbox-contact.jpg" 
width="25px" height="25px"></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
        <a moz-do-not-send="true" href="mailto:jbonilla@sipwise.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Jon Bonilla (Manwe)</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">April 18, 2013 
11:14 PM</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><div>El Thu, 18 Apr 2013 
14:04:56 +0200<br><br></div><div><!----><br>I have found this 
requirement, where the peer requires a vpn or any other<br>tunnel 
scenario to be established to send the traffic and they will only accept<br>traffic
 from the tunnel. Most common carrier asking for this is British Telecom<br>(BT)<br><br>The
 extra_socket option does not work here because the rtp will still be 
sent<br>and received in the default ip address, which is not the one 
used for the<br>tunnel.<br><br>2 ways of dealing with it:<br><br>* 
Create the tunnel in your router. This is the "righ way" (imho). I've 
also<br>  seen operator purchasing a small cisco router just for this 
function. It's<br>  easy and cheap.<br><br>* Use an aditional spce to 
route the calls between the tunnel and the main<br>  spce. This is the 
same Thilo achieves with his kamailio-sems combo. This<br>  additional 
spce will listen in the tunnel address and that ip will be<br>  
routeable from/to the main spce's default ip address.<br><br></div><div>_______________________________________________<br>Spce-user
 mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br><a class="moz-txt-link-freetext" href="http://lists.sipwise.com/listinfo/spce-user">http://lists.sipwise.com/listinfo/spce-user</a><br></div></div><div
 style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div 
style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px">       <div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="thilo.bangert@gmail.com" photoname="Thilo Bangert" 
src="cid:part2.08020409.03070406@gmail.com" 
name="compose-unknown-contact.jpg" width="25px" height="25px"></div>   <div
 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
        <a moz-do-not-send="true" href="mailto:thilo.bangert@gmail.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Thilo Bangert</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">April 18, 2013 
1:04 PM</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody"><pre wrap="">On Thursday, April 18, 2013 11:58:02 AM Deon Vermeulen wrote:
</pre><blockquote type="cite"><pre wrap="">Hi

Can anyone please help me to achieve the following network configuration:

                                                                 PROVIDER 2


                                                                  SIP TRUNK


Internal Network  ---- SIP TRUNK  -----   SPCE   ----- SIP TRUNK -----
PROVIDER 1


                                                                  SIP TRUNK


                                                                 PROVIDER 3

</pre></blockquote><pre wrap=""><!---->
we have solved this by having provider specific peering gateways, consisting 
of a kamailio and sems combo on a different (virtual) host.

kind regards
Thilo


</pre><blockquote type="cite"><pre wrap="">Thanks a lot.

Kind Regards

Deon
</pre></blockquote><pre wrap=""><!---->
_______________________________________________
Spce-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a class="moz-txt-link-freetext" href="http://lists.sipwise.com/listinfo/spce-user">http://lists.sipwise.com/listinfo/spce-user</a>
</pre></div><div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
 style="display:table;width:100%;border-top:1px solid 
#EDEEF0;padding-top:5px">       <div 
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
 photoaddress="vermeulen.deon@gmail.com" photoname="Deon Vermeulen" 
src="cid:part3.06080407.07060609@gmail.com" name="postbox-contact.jpg" 
width="25px" height="25px"></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
        <a moz-do-not-send="true" href="mailto:vermeulen.deon@gmail.com" 
style="color:#737F92 
!important;padding-right:6px;font-weight:bold;text-decoration:none 
!important;">Deon Vermeulen</a></div>   <div 
style="display:table-cell;white-space:nowrap;vertical-align:middle;">   
  <font color="#9FA2A5"><span style="padding-left:6px">April 18, 2013 
11:58 AM</span></font></div></div></div><div 
style="color:#888888;margin-left:24px;margin-right:24px;" 
__pbrmquotes="true" class="__pbConvBody">
<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
<div style="font-size: 11pt;font-family: Calibri;"><span 
style="font-family: Calibri;">Hi<br><br>Can anyone please help me to 
achieve the following network configuration:<br><br></span><span><span 
style="font-family: Calibri;">                                        
                        PROVIDER 2</span></span><br><span><span 
style="font-family: Calibri;">                                        
                                |</span> </span><span><span 
style="font-family: Calibri;"></span></span><br><span><span 
style="font-family: Calibri;">                                        
                                |</span> </span><br><span><span 
style="font-family: Calibri;">                                        
                         SIP TRUNK</span></span><br><span><span 
style="font-family: Calibri;">                                        
                                |</span> </span><span><span 
style="font-family: Calibri;"></span></span><br><span 
style="font-family: Calibri;">                                        
                                |<br>Internal Network  ---- SIP TRUNK  
-----   SPCE   ----- SIP TRUNK ----- PROVIDER 1<br></span><span><span 
style="font-family: Calibri;">                                        
                                |</span> <br></span><span><span 
style="font-family: Calibri;">                                        
                                |</span> <br></span><span><span><span 
style="font-family: Calibri;">                                        
                         SIP TRUNK</span></span><br>
<span><span style="font-family: Calibri;">                            
                                            |</span> </span><span><span 
style="font-family: Calibri;"></span></span><br>
<span style="font-family: Calibri;">                                    
                                    |</span> </span><br><span><span><span
 style="font-family: Calibri;">                                        
                        PROVIDER 3</span></span></span><br><br><br>Network

 Addresses and Listening Ports:<br><br>Internal Network<br>- Eth0<br>     

 ip: 192.168.0.10<br>      netmask: 255.255.255.0<br>      port: 5060<br>     

 protocol: udp<br>      rtp_ext<br>      web_int<br>      web_ext<br><br><span>PROVIDER

 1<br>
- Eth1<br>
      ip: 172.16.1.10<br>
      netmask: 255.255.255.0<br>
      port: 6080 </span><br><span>      protocol: udp </span><br>      
rtp_ext<br><br><span>PROVIDER 2<br>
- Eth2<br>
      ip: 172.16.2.10<br>
      netmask: 255.255.255.0<br>
      port: 6085<br></span><span>      protocol: udp </span><br><span>     

 rtp_ext:<br><br></span><span><span>PROVIDER 3<br>
- Eth3<br>
      ip: 172.16.3.10<br>
      netmask: 255.255.255.0<br>
      port: 6090</span></span><br><span>      protocol: udp<br>      
rtp_ext<br></span><br><br>OBJECTIVES:<br>1. All services should be 
available on the Internal Network.<br>2. Only SIP and RTP services 
should be available on the PROVIDER networks.<br>3. Only the assigned 
SIP Ports should be available to the respective PROVIDER, ie. PROVIDER 1
 only port 6080 udp.<br>4. I'm not sure how the roles should be setup 
for each respective interface?<br><br><br>Thanks a lot.<br><br>Kind 
Regards<br><br>Deon<br></div>
</div></blockquote></div></body></html>