VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
| View previous topic :: View next topic |
| Author |
Message |
annusfictus at gmail.com
Guest
|
 Posted: Sun Jul 17, 2016 7:31 am Post subject: [asterisk-users] PJSIP - State of the art |
 |
|
Hello,
I'd like share with you my tests about PJSIP channel with the aim of improving the functioning of the channel: - Multi domain support not work correctly: https://issues.asterisk.org/jira/browse/ASTERISK-26026
- Different context subscribe for each endpoint not possible: https://issues.asterisk.org/jira/browse/ASTERISK-25471
- BLF don't work correctly on my tests with X-Lite, BRIA, JiTSI. Only work partially with microsip but because this softphone use the same SIP STACK (PJSIP). I test BLF with the latest Asterisk version and latest FreePBX version. The problem is when a softphone is on the phone on the other softphone appear off-line. On Jitsi not is possible know if a Endpoints is or not online
The main idea of the new channel was working on a multi-domain environment, have more then one device registered with same credentials and have more stability.
Be Better still with Asterisk 1.11.X?
Regards
|
|
| Back to top |
|
 |
jcolp at digium.com
Guest
|
|
| Back to top |
|
|
gmludo at gmail.com
Guest
|
| Posted: Sun Jul 17, 2016 4:20 pm Post subject: [asterisk-users] PJSIP - State of the art |
|
|
2016-07-17 14:30 GMT+02:00 Annus Fictus <annusfictus@gmail.com (annusfictus@gmail.com)>:
| Quote: |
The main idea of the new channel was working on a multi-domain environment
|
For now, to my experience, it's more future-proof compliant to use a prefix in the SIP username than multi-domain environment.
Even if the multi-domain support was perfect in Asterisk, we tested some crappy SIP endpoints where in fact, even if you configure a domain name everywhere in the configuration, you have only IPs in SIP packets.
We have that on production for our cloud plateform, it works pretty well and also simplify whitelabel handling.
Moreover, if you have a good provisioning support, it will be invisible for your users.
When I see the time needed to really use on production the SNI feature in SSL, and you have only 5 majors HTTP endpoints (aka Web browsers).
In the SIP world, I'm not sure you can use multi domain except if you can force the SIP endpoints used by your clients.
| Quote: |
, have more then one device registered with same credentials and have more stability.
|
Since 13.9.1, we have a better experience of pjsip.
Nevertheless, not yet massively used on production for now, we planned to migrate endpoint by endpoint to minimize the risk.
| Quote: |
Be Better still with Asterisk 1.11.X?
|
Maybe you could use Asterisk 13 with chan_sip to start, it works pretty well and already think to support chan_pjsip in the same time.
The benefit to think about that if one day you need to use an alternative channel like chan_iax2, it should be easier to implement for you.
|
|
| Back to top |
|
|
BryantZ at zktech.com
Guest
|
| Posted: Mon Jul 18, 2016 7:17 am Post subject: [asterisk-users] PJSIP - State of the art |
|
|
I agree the multi-domain environment is a nice idea, but too many endpoints don't properly support. We to use a prefix in the SIP username for multi-domain environments.
Thanks Bryant
From: "Ludovic Gasc" <gmludo@gmail.com> Sent: Sunday, July 17, 2016 5:20 PM To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users@lists.digium.com> Subject: Re: [asterisk-users] PJSIP - State of the art
2016-07-17 14:30 GMT+02:00 Annus Fictus <annusfictus@gmail.com (annusfictus@gmail.com)>: | Quote: |
The main idea of the new channel was working on a multi-domain environment
|
For now, to my experience, it's more future-proof compliant to use a prefix in the SIP username than multi-domain environment.
Even if the multi-domain support was perfect in Asterisk, we tested some crappy SIP endpoints where in fact, even if you configure a domain name everywhere in the configuration, you have only IPs in SIP packets.
We have that on production for our cloud plateform, it works pretty well and also simplify whitelabel handling.
Moreover, if you have a good provisioning support, it will be invisible for your users.
When I see the time needed to really use on production the SNI feature in SSL, and you have only 5 majors HTTP endpoints (aka Web browsers).
In the SIP world, I'm not sure you can use multi domain except if you can force the SIP endpoints used by your clients.
| Quote: |
, have more then one device registered with same credentials and have more stability.
|
Since 13.9.1, we have a better experience of pjsip.
Nevertheless, not yet massively used on production for now, we planned to migrate endpoint by endpoint to minimize the risk.
| Quote: |
Be Better still with Asterisk 1.11.X?
|
Maybe you could use Asterisk 13 with chan_sip to start, it works pretty well and already think to support chan_pjsip in the same time.
The benefit to think about that if one day you need to use an alternative channel like chan_iax2, it should be easier to implement for you.
|
|
| Back to top |
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
Search
