[Spce-user] wrong registration with contact from an internal IP address

[Tóth Csaba]

Hi,

hundreds of other subscriber works well, only this not, so i don't think
the problem is with routing. By the way, i just checked, everything is fine.

Anyway thanks for help!

Csaba





2015.02.10. 18:07 keltezéssel, Marc Storck írta:
> If you need a static route to the external IP in order for packets to arrive at the external IP of the client, it seems that your Layer 3 routing is the culprit…
> 
> Do you have a default route on your system? (E.g. does route -n show a route for Destination 0.0.0.0?)
> Does the Gateway for your default route differ from the Gateway on your default route?
> Do the Flags, Metric or Iface differ between your default route and the static route?
> 
> I don’t know why the Panel only shows the Contact and not the (optional) the public IP of the endpoint. Eventually you have to ask that directly to Sipwise.
> 
> Regards,
> 
> Marc
> 
>> On 10 Feb 2015, at 17:59, Tóth Csaba <tsabi at tsabi.hu> wrote:
>>
>> Dear Marc,
>>
>> thank you the quick and so informative answer!
>>
>> The problem what we faced here is the Kamailio was not able to make an
>> invite for this subscriber, because it tried to connect with the
>> contact, what contained the internal IP address. We tried to trace it
>> with wireshark, and this is what we understanded. Maybe we were wrong
>> with this. :(
>> After we setted a static route to the real external IP address the calls
>> goes in well.
>>
>> So it doesn't matter what is the stored contact? Why we not see it back
>> in the frontend what is the real IP/real contact? :/
>>
>> Thanks,
>> Csaba
>>
>>
>>
>> 2015.02.10. 17:40 keltezéssel, Marc Storck írta:
>>> The contact is not wrong at all, the content of the content is not used to route the call on the IP level.  The contact field is used to construct the correct Request header for inbound calls.
>>>
>>> Kamailio stores the public IP and public port of the user in the “received” field of the kamailio table.
>>>
>>> Here is an example for my test user:
>>>
>>> Contact:
>>> sip:MyTestUser at 192.168.178.22:59969;transport=tls;registering_acc=sld_tld
>>>
>>> received:
>>> sip:203.0.113.244:59969;transport=tls
>>>
>>> path:
>>> <sip:lb at 127.0.0.1;lr;received=sip:203.0.113.244:59969%3Btransport%3Dtls;socket=sip:100.64.177.34:5061>
>>>
>>> Inbound calls to that user are sent to IP 203.0.113.244 port 59969 and the Request URI is constructed correctly using the stored contact.
>>>
>>> Eventually you can tell us which problem you try to solve and the members on the mailing list can assist you on how to solve it.
>>>
>>> Regards,
>>>
>>> Marc
>>>
>>>
>>>> On 10 Feb 2015, at 17:20, Tóth Csaba <tsabi at tsabi.hu> wrote:
>>>>
>>>> Dear List, SipWise Team,
>>>>
>>>> how can i disabled registrations what try to register a contact into an
>>>> internal IP address range?
>>>>
>>>> For example this is a contact what a subscriber registered with:
>>>> "sip:361*******@10.102.2.1;transport=UDP;user=phone"
>>>>
>>>> How can i disable the possibility to these kind of registrations not be
>>>> able to register, or "maybe" (?) better the system do a replace on the
>>>> invalid IP address to the real external IP address it gots the
>>>> registration from? Our old call distribution system does this latter
>>>> mechanism, i am not so satisfied with it, i think the first method (a
>>>> decline on the registration) would be better.
>>>>
>>>> Thanks in advance!
>>>> Csaba Tóth
>>>> _______________________________________________
>>>> Spce-user mailing list
>>>> Spce-user at lists.sipwise.com
>>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>>>
>>>
>>> _______________________________________________
>>> Spce-user mailing list
>>> Spce-user at lists.sipwise.com
>>> https://lists.sipwise.com/listinfo/spce-user
>>>
>> _______________________________________________
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> https://lists.sipwise.com/listinfo/spce-user
> 
> 
> 
> _______________________________________________
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> https://lists.sipwise.com/listinfo/spce-user
>