We use this functionality quite a lot in Linphone, although we don't call
within a local LAN much so the comments by Stuart are probably valid in
your scenario regarding IPv6.
 just three comments on this:
1) We put the prefix "sip:user@:" in front of the IP address (e.g.
sip:[email protected]). It seems to help Linphone know this isn't a phone
number but a URI.
2) We've published a free "reduced feature set" version of Linphone for iOS
and Android that might help you (assuming you don't need video). It's
designed specifically to call without registration. If you simply key in an
IP address it will complete the URI for you before making the call. It also
keeps its own phone book, aside from the phone's main contact list. Search
for "fieldtap" on the app stores.
3) It's entirely possible that if the receive side is registered, invites
from destinations other than the registrar may be rejected.

On Tue, May 14, 2019 at 12:14 PM <[email protected]> wrote:

> Send Linphone-users mailing list submissions to
>         [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.nongnu.org/mailman/listinfo/linphone-users
> or, via email, send a message with subject or body 'help' to
>         [email protected]
>
> You can reach the person managing the list at
>         [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Linphone-users digest..."
>
>
> Today's Topics:
>
>    1. Re:  [Linphone-developers] serverless voip call (dinis braz?o)
>    2. Re:  [Linphone-developers] serverless voip call
>       (Stuart D. Gathman)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 14 May 2019 09:54:27 +0100
> From: dinis braz?o <[email protected]>
> To: [email protected], [email protected]
> Subject: Re: [Linphone-users] [Linphone-developers] serverless voip
>         call
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="us-ascii"
>
> An HTML attachment was scrubbed...
> URL: <
> http://lists.nongnu.org/archive/html/linphone-users/attachments/20190514/f79e043b/attachment.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Tue, 14 May 2019 11:51:54 -0400 (EDT)
> From: "Stuart D. Gathman" <[email protected]>
> To: [email protected]
> Cc: [email protected]
> Subject: Re: [Linphone-users] [Linphone-developers] serverless voip
>         call
> Message-ID: <[email protected]>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> On Tue, 14 May 2019, dinis braz?o wrote:
>
> > The useage scenario is:? mobiles in the same wifi network but without
> access
> > to server.
> > I am looking for a way to make them call each other without needing a
> server
> >
> > User2 would dial [email protected]:5060??? targetting directly
> the
> > user 1.
> > No need for registration.
>
> Yes, that is the primary way I use linphone.  Using IPv6, you can
> call directly without being in the same wifi network - but as most
> wifi (or mobile) routers in the US do not implement IPv6, you have
> to install a VPN.  The IPv6 VPN I use is Cjdns - but the app for that
> is not in an app store, and has to be installed manually.  I use
> laptops.  :-)
>
> In the peer-to-peer setup, the IP becomes the "phone number" quite
> literally, instead of a metaphor when trying to explain IP to lay people.
>
> Here is what an IPv6 peer-to-peer sip address looks like:
>
> "John Doe" <sip:jdoe@[fce9:1328:adf1:bffe:4b6b:f53f:48ba:1882]>
>
> The port 5060 is the default.
>
> I have linphone-3.6.1, and unfortunately, an underlying library
> recently decided that it didn't like sending certain SIP signalling
> messages
> to a private IP like the above or 192.168.x.x.  It would attempt to send
> from a public IP instead, usually resulting in failure (although it
> works when the IPs are actually public).
>
> The symptom is that the call works perfectly with audio both ways
> for 30 secs - then gets disconnected when the caller times out waiting
> for the call setup acknowledgement.
>
> If your version is having that problem, you need to use public IPs,
> which means using a VPN.  Using a public IPv6 via VPN effectively
> works around the problem.
>
> --
>               Stuart D. Gathman <[email protected]>
> "Confutatis maledictis, flamis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial.
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Linphone-users mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/linphone-users
>
>
> ------------------------------
>
> End of Linphone-users Digest, Vol 198, Issue 6
> **********************************************
>
_______________________________________________
Linphone-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/linphone-users

Reply via email to