I am the dialtone provider for 90% of my customers - If I could have a similar deal on FOP2 that included a WebPhone that worked with FreePBX without modifying the extension, I would jump on it!
I can think of at least 10 customers off the top of my head that would take it tomorrow!
No, just the opposite - if you configure the extension for FOP2 to use it, you CAN’T use it at the same time with a Hard-Phone - That’s the problem.
I am not looking to make a buck on this at all - I am trying to provide a missing feature - a Web-Based SoftPhone with an interface for watching the other extensions + Chat and presence.
If for some reason it got bundled (working) into FreePBX, I would happily give it away.
All I am saying is that if I have to pay something to make this work the way it should, I would be happy to - and I think a lot of other people would too!
Then have you tried the route FreePBX has gone, two endpoints that share the same state and presence? Just would need to Dial() both at once for incoming calls.
Yes, I have used that method in several places and it works fine - but it would be way better if (like Connect and UCP) it was an invisible pair of the primary extension and all the plumbing was automatic.
Except that’s not what is being talked about here. As the quote from Josh pointed out, you can’t have an IP phone and WebRTC on the same endpoint config because of the DTLS-SRTP requirements for WebRTC. So in order to have a WebRTC phone and a desk phone you need two endpoints which would need to be in the Dial() command for incoming calls to hit them both. Bumping max contacts doesn’t solve this issue.
Yeah - it would be really great if you COULD set up the contacts with different settings - not only would it fix this problem, it would allow you to do E911 on the contacts with different Caller-ID’s - very handy to have the same extension at your office and house, but different 911’s for each phone - same extension, but different settings.
Contacts have nothing to do with outbound calls. Contacts are there to tell the system where to send requests to, so in this case incoming calls to the devices. Contacts don’t need to exist for an outbound call to happen.
I set unique callerid names on each of the devices that share the same endpoint. I use that to determine which E9-1-1 details to send.
I think there must be a terminology problem here. My understanding of the term outgoing, for a SIP, is a call in which Asterisk acts as the SIP client, e.g. a typical B leg, whether trunk or extension.
PJSIP contacts are only for such calls, although they can be bypassed by providing extra information in the dial string.
That’s not always the case. I can initiate a call straight from Asterisk via different methods. So I send an call via PJSIP to an endpoint’s contacts that is just a single leg call.
But you are correct that you don’t even need an AOR or Contacts to send a call to a destination URI, the only thing you need is a valid Endpoint.