<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
El 22/02/2012 19:29, Mario Contreras escribió:
<blockquote cite="mid:4F4533EE.2070902@innovasur.es" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
El 22/02/2012 15:58, Andreas Granig escribió:
<blockquote cite="mid:4F45027B.3080907@sipwise.com" type="cite">
<pre wrap="">Hi Mario,
I guess you get back a "403 domain not served here", right? If that's
the case, try to just add the IP address as an empty domain (don't
create any subscribers in it, just leave it empty).
This is a bit of a hack, but the only way for now to receive inbound
calls from a peer where you have to register before.
Andreas
On 02/22/2012 11:40 AM, Mario Contreras wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hello again,
like I say in the subject, some configurations of my sipwise don't work
correctly with inbound calls(from a sip peering).
If I write in peer_auth_user, peer_auth_pass and peer_auth_realm the
needed values with peer_auth_register enabled in subscribers with
find_subscriber_by_auth_user enabled in peer host preferences it works
perfect.
But here it's my question: Doesn't it work with the same result if those
preferences were all in peer host? I mean, with the correct E.164 in
subscribers. I have try enabling e164_to_ruri but my . I guess it can be
done. But how?
Thanks.
_______________________________________________
Spce-user mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sipwise.com/listinfo/spce-user">http://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Spce-user mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.sipwise.com/listinfo/spce-user">http://lists.sipwise.com/listinfo/spce-user</a>
</pre>
</blockquote>
It's not like you say. I have aleady did the hack. <br>
<ul>
<li>I have a sip server with like ip=200.200.200.10, and I know
that server use ip's from netmask 255.255.255.0 to make
connections. </li>
<li>The 'from number' is like 988666666</li>
<li>The to number is like 511111111. Note that it's the same
configured in the subscriber's e164, but whitout country code<br>
</li>
</ul>
<br>
The calls are like this:<br>
From: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="sip:988666666@200.200.200.9"><sip:988666666@200.200.200.9></a>;<br>
To: <a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="sip:511111111@200.200.200.20"><sip:511111111@200.200.200.20></a><br>
<br>
The answer from my sipwise is 404 (not found), instead of 403.<br>
<br>
Thanks.<br>
</blockquote>
Sorry, I made a mistake writing. The ip of my peering server(the ip
I configured) is 200.200.200.10, and the call is To: <a
moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="sip:511111111@200.200.200.20"><sip:511111111@200.200.200.10>.
</a>Both are equals.<br>
<br>
Thanks.<br>
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="sip:511111111@200.200.200.20"></a>
</body>
</html>