Toerless Eckert

On Sat, Mar 09, 2019 at 10:09:26AM -0000, Thomas Ries wrote: Siproxd is designed to cover the typical case where VoIP equipment in a local network using RFC1918 address space (private IP adrdesses) needs to communicate with a Registrar in the public Internet. This is the typical home- and small office setup. Understood. Your use case is completely different. I'm not saying it can't be done, but it ist not a scenario that is considered supported by siproxd. Also I believe that it really depends on...

On Fri, Mar 08, 2019 at 06:35:06AM -0000, Thomas Ries wrote: Hi, No this will not work. Siproxd is desgined to help with NATs where the Client (phone) is in a private network segment and the PBX / SIP provider is in the publicc Internet. you are basically trying to do the reverse. Thanks for the quick answer!! Too bad ;-(( Any suggestion what my most simple option would be to solve this issue ? Also: Just for curiosity and only if there is any chance for a non-SIP person like myself to understand...

Sorry if this is too stupid a question, but i trie to figure out the answer from reading the documentation, but due to the absence of some "theory of operations" section i failed to understand it. I have from my new ISP the access parameter to connect SIP clients to their SIP server, e.g.: proxy server, SIP domain, port, etc. pp. And lets assume this will work fine like it did with my old ISP, e.g.: using gigaset and linphone to connect. Alas, the proxy server uses a 10 net address, so it is only...