Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK:5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf- acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK:5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: <sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf-
acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
1) Without REFER support at kamailio. I expect MS just will do transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
2) Kamilio support REFER and send it to FS. FS should transfer such call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK:5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: <sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf-
acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
And how exactly is this Kamailio-related?
On Thu, May 14, 2020 at 3:24 PM Yuriy Nasida ynasida@gmail.com wrote:
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
- Without REFER support at kamailio. I expect MS just will do
transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
- Kamilio support REFER and send it to FS. FS should transfer such
call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK:5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: <sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf-
acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
This looks Fs-related, not kamailio.
On Thu, 14 May 2020 at 20:25, Yuriy Nasida ynasida@gmail.com wrote:
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
- Without REFER support at kamailio. I expect MS just will do
transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
- Kamilio support REFER and send it to FS. FS should transfer such
call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK:5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: <sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf-
acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Yes, Kamailio just send MS refer to FS. In my opinion it is MS related, because their REFER is weird. This list have members who did MS integration with Kamailio. That is why I would like to ask if you get attended (consult), transfer working with MS (with refer or without refer - it doesn't matter). Do you handle refer at kamailio somehow?
чт, 14 мая 2020 г., 23:02 David Villasmil david.villasmil.work@gmail.com:
This looks Fs-related, not kamailio.
On Thu, 14 May 2020 at 20:25, Yuriy Nasida ynasida@gmail.com wrote:
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
- Without REFER support at kamailio. I expect MS just will do
transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
- Kamilio support REFER and send it to FS. FS should transfer such
call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK:5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: <sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf-
acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
I personally chose the option of not removing the REFER from supported methods. Had to handle in a custom way the attended transfer context in Asterisk (my choice of B2B). I don't know how it is in FS.
Good luck.
On Fri, May 15, 2020 at 2:32 AM Yuriy Nasida ynasida@gmail.com wrote:
Yes, Kamailio just send MS refer to FS. In my opinion it is MS related, because their REFER is weird. This list have members who did MS integration with Kamailio. That is why I would like to ask if you get attended (consult), transfer working with MS (with refer or without refer - it doesn't matter). Do you handle refer at kamailio somehow?
чт, 14 мая 2020 г., 23:02 David Villasmil <david.villasmil.work@gmail.com
:
This looks Fs-related, not kamailio.
On Thu, 14 May 2020 at 20:25, Yuriy Nasida ynasida@gmail.com wrote:
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
- Without REFER support at kamailio. I expect MS just will do
transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
- Kamilio support REFER and send it to FS. FS should transfer such
call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK:5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: <sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf-
acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Thanks again Sergiu!
Can you please look at REFER i sent and let me know if your REFER to asterisk looks same?
MS's REFER is so weird honesty. Especially if I compare it with REFER from zoiper.
пт, 15 мая 2020 г., 21:25 Sergiu Pojoga pojogas@gmail.com:
I personally chose the option of not removing the REFER from supported methods. Had to handle in a custom way the attended transfer context in Asterisk (my choice of B2B). I don't know how it is in FS.
Good luck.
On Fri, May 15, 2020 at 2:32 AM Yuriy Nasida ynasida@gmail.com wrote:
Yes, Kamailio just send MS refer to FS. In my opinion it is MS related, because their REFER is weird. This list have members who did MS integration with Kamailio. That is why I would like to ask if you get attended (consult), transfer working with MS (with refer or without refer - it doesn't matter). Do you handle refer at kamailio somehow?
чт, 14 мая 2020 г., 23:02 David Villasmil <david.villasmil.work@gmail.com
:
This looks Fs-related, not kamailio.
On Thu, 14 May 2020 at 20:25, Yuriy Nasida ynasida@gmail.com wrote:
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
- Without REFER support at kamailio. I expect MS just will do
transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
- Kamilio support REFER and send it to FS. FS should transfer such
call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
Well, I saw similar questions in the list already but looks like nobody has answer.
Please look at REFER below.
Kamilio get REFER from MS and sends it to FS node. Next, FS node try to make 3th call for some reason.I expect that FS will not do 3th call and just will connect Alice and Bob itself.
2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 TO: sip:Alice_number@FQDN_OF_TRUNK :5061;user=phone;tag=e8ct9S6ty13va CSEQ: 4 REFER CALL-ID: 2c71b2a6669b5343a231e1244b19c945 MAX-FORWARDS: 50 Via: SIP/2.0/UDP FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 CONTACT: <sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc CONTENT-LENGTH: 0 REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls REFERRED-BY: <sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf-
acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< sip:customer1@m365x587912.onmicrosoft.com> PRIVACY: id X-AUTH-IP: 52.114.75.24 X-AUTH-PORT: 3136
Any advice?
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Comrad Yuriy,
I'm too lazy to start comparing... but I'm not special either, so most likely I get the same REFER from MS as everyone else. You just have to figure out how to handle it, as with any MS product, lol
P.S. Zoiper isn't by far the de-facto diamond standard in following SIP compliance, lol
Cheers.
On Fri, May 15, 2020 at 4:55 PM Yuriy Nasida ynasida@gmail.com wrote:
Thanks again Sergiu!
Can you please look at REFER i sent and let me know if your REFER to asterisk looks same?
MS's REFER is so weird honesty. Especially if I compare it with REFER from zoiper.
пт, 15 мая 2020 г., 21:25 Sergiu Pojoga pojogas@gmail.com:
I personally chose the option of not removing the REFER from supported methods. Had to handle in a custom way the attended transfer context in Asterisk (my choice of B2B). I don't know how it is in FS.
Good luck.
On Fri, May 15, 2020 at 2:32 AM Yuriy Nasida ynasida@gmail.com wrote:
Yes, Kamailio just send MS refer to FS. In my opinion it is MS related, because their REFER is weird. This list have members who did MS integration with Kamailio. That is why I would like to ask if you get attended (consult), transfer working with MS (with refer or without refer - it doesn't matter). Do you handle refer at kamailio somehow?
чт, 14 мая 2020 г., 23:02 David Villasmil < david.villasmil.work@gmail.com>:
This looks Fs-related, not kamailio.
On Thu, 14 May 2020 at 20:25, Yuriy Nasida ynasida@gmail.com wrote:
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
- Without REFER support at kamailio. I expect MS just will do
transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
- Kamilio support REFER and send it to FS. FS should transfer such
call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
Remove the REFER from Supported header if you want MS to initiate a separate call leg, it's described in the direct dialing documentation.
Cheers.
On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com wrote:
> Well, I saw similar questions in the list already but looks like > nobody has answer. > > Please look at REFER below. > > Kamilio get REFER from MS and sends it to FS node. Next, FS node try > to make 3th call for some reason.I expect that FS will not do 3th call and > just will connect Alice and Bob itself. > > > 2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 > REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 > FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 ;user=phone>;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 > TO: sip:Alice_number@FQDN_OF_TRUNK :5061>;user=phone;tag=e8ct9S6ty13va > CSEQ: 4 REFER > CALL-ID: 2c71b2a6669b5343a231e1244b19c945 > MAX-FORWARDS: 50 > Via: SIP/2.0/UDP > FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c > VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 > CONTACT: sip:api-du-a-euwe.pstnhub.microsoft.com:443 ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc > CONTENT-LENGTH: 0 > REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 ;user=phone;transport=tls> > REFERRED-BY: sip:sip.pstnhub.microsoft.com:5061 ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf- > > acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> > USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 > ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY > P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< > sip:customer1@m365x587912.onmicrosoft.com> > PRIVACY: id > X-AUTH-IP: 52.114.75.24 > X-AUTH-PORT: 3136 > > > Any advice? > > > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Zoiper just follows RFC recommendation for Refer (unlike MS as always). Well, at least i know that there is somebody who have it working. Thanks comrade, I will hack it soon also.
Btw, i finally got MS working with Record-Route headers. They just didn't like ;lr=on param and wanted to have only ;lr. Like we all know, MS docs do not say how they work with Record-Route headers. Thus it can help to many others list members. Same things with refer.
Please advice if you have any advice regarding subject.
сб, 16 мая 2020 г., 2:13 Sergiu Pojoga pojogas@gmail.com:
Comrad Yuriy,
I'm too lazy to start comparing... but I'm not special either, so most likely I get the same REFER from MS as everyone else. You just have to figure out how to handle it, as with any MS product, lol
P.S. Zoiper isn't by far the de-facto diamond standard in following SIP compliance, lol
Cheers.
On Fri, May 15, 2020 at 4:55 PM Yuriy Nasida ynasida@gmail.com wrote:
Thanks again Sergiu!
Can you please look at REFER i sent and let me know if your REFER to asterisk looks same?
MS's REFER is so weird honesty. Especially if I compare it with REFER from zoiper.
пт, 15 мая 2020 г., 21:25 Sergiu Pojoga pojogas@gmail.com:
I personally chose the option of not removing the REFER from supported methods. Had to handle in a custom way the attended transfer context in Asterisk (my choice of B2B). I don't know how it is in FS.
Good luck.
On Fri, May 15, 2020 at 2:32 AM Yuriy Nasida ynasida@gmail.com wrote:
Yes, Kamailio just send MS refer to FS. In my opinion it is MS related, because their REFER is weird. This list have members who did MS integration with Kamailio. That is why I would like to ask if you get attended (consult), transfer working with MS (with refer or without refer - it doesn't matter). Do you handle refer at kamailio somehow?
чт, 14 мая 2020 г., 23:02 David Villasmil < david.villasmil.work@gmail.com>:
This looks Fs-related, not kamailio.
On Thu, 14 May 2020 at 20:25, Yuriy Nasida ynasida@gmail.com wrote:
I do not want MS to initiate a separate call leg. I want to get attended (consult) transfer. I call from A to B. Next call from A to C. Next, I want transfer B to C. B and C is pstn numbers (i.e. not MS side).
I expect 2 variants:
- Without REFER support at kamailio. I expect MS just will do
transfer B-->C at MS side. But MS send one more INVITE to C Instead of this. i.e. C side already has the call. I do transfer and.. C side gets one more call instead of transfer.
- Kamilio support REFER and send it to FS. FS should transfer such
call inside itself (like it does for REFERs from zoiper or other usual softphones). But... MS sends weird REFER and FS can not handle it it the same way like FS does for zoiper.
Please advice.
On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com wrote:
> Remove the REFER from Supported header if you want MS to initiate a > separate call leg, it's described in the direct dialing documentation. > > Cheers. > > On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com > wrote: > >> Well, I saw similar questions in the list already but looks like >> nobody has answer. >> >> Please look at REFER below. >> >> Kamilio get REFER from MS and sends it to FS node. Next, FS node >> try to make 3th call for some reason.I expect that FS will not do 3th call >> and just will connect Alice and Bob itself. >> >> >> 2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 >> REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 >> FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 > ;user=phone>;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 >> TO: sip:Alice_number@FQDN_OF_TRUNK > :5061>;user=phone;tag=e8ct9S6ty13va >> CSEQ: 4 REFER >> CALL-ID: 2c71b2a6669b5343a231e1244b19c945 >> MAX-FORWARDS: 50 >> Via: SIP/2.0/UDP >> FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c >> VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 >> CONTACT: sip:api-du-a-euwe.pstnhub.microsoft.com:443 > ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc >> CONTENT-LENGTH: 0 >> REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 > ;user=phone;transport=tls> >> REFERRED-BY: sip:sip.pstnhub.microsoft.com:5061 > ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf- >> >> acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> >> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 >> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY >> P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< >> sip:customer1@m365x587912.onmicrosoft.com> >> PRIVACY: id >> X-AUTH-IP: 52.114.75.24 >> X-AUTH-PORT: 3136 >> >> >> Any advice? >> >> >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Well. After some break I got it working. Yes, it's FS related and I had to use quite fat hack at Freeswitch to get MS hold/unhold working (with MS MOH).You know... MS does transfer to their side to play MOH and... they use re-invite to get the call that was blind transfered. As for FS I had to use manual way with park/execute_on_sip_reinvite/intercept. Not so secret knowladge. It is weird that no one wanted to share global way how to handle extra MS invites they so like to send. So I will share a bit for others :)
On Sat, 16 May 2020 at 10:13, Yuriy Nasida ynasida@gmail.com wrote:
Zoiper just follows RFC recommendation for Refer (unlike MS as always). Well, at least i know that there is somebody who have it working. Thanks comrade, I will hack it soon also.
Btw, i finally got MS working with Record-Route headers. They just didn't like ;lr=on param and wanted to have only ;lr. Like we all know, MS docs do not say how they work with Record-Route headers. Thus it can help to many others list members. Same things with refer.
Please advice if you have any advice regarding subject.
сб, 16 мая 2020 г., 2:13 Sergiu Pojoga pojogas@gmail.com:
Comrad Yuriy,
I'm too lazy to start comparing... but I'm not special either, so most likely I get the same REFER from MS as everyone else. You just have to figure out how to handle it, as with any MS product, lol
P.S. Zoiper isn't by far the de-facto diamond standard in following SIP compliance, lol
Cheers.
On Fri, May 15, 2020 at 4:55 PM Yuriy Nasida ynasida@gmail.com wrote:
Thanks again Sergiu!
Can you please look at REFER i sent and let me know if your REFER to asterisk looks same?
MS's REFER is so weird honesty. Especially if I compare it with REFER from zoiper.
пт, 15 мая 2020 г., 21:25 Sergiu Pojoga pojogas@gmail.com:
I personally chose the option of not removing the REFER from supported methods. Had to handle in a custom way the attended transfer context in Asterisk (my choice of B2B). I don't know how it is in FS.
Good luck.
On Fri, May 15, 2020 at 2:32 AM Yuriy Nasida ynasida@gmail.com wrote:
Yes, Kamailio just send MS refer to FS. In my opinion it is MS related, because their REFER is weird. This list have members who did MS integration with Kamailio. That is why I would like to ask if you get attended (consult), transfer working with MS (with refer or without refer - it doesn't matter). Do you handle refer at kamailio somehow?
чт, 14 мая 2020 г., 23:02 David Villasmil < david.villasmil.work@gmail.com>:
This looks Fs-related, not kamailio.
On Thu, 14 May 2020 at 20:25, Yuriy Nasida ynasida@gmail.com wrote:
> I do not want MS to initiate a separate call leg. I want to get > attended (consult) transfer. I call from A to B. Next call from A to C. > Next, I want transfer B to C. > B and C is pstn numbers (i.e. not MS side). > > I expect 2 variants: > > 1) Without REFER support at kamailio. I expect MS just will do > transfer B-->C at MS side. But MS send one more INVITE to C Instead of > this. i.e. C side already has the call. I do transfer and.. C side gets > one more call instead of transfer. > > 2) Kamilio support REFER and send it to FS. FS should transfer such > call inside itself (like it does for REFERs from zoiper or other usual > softphones). > But... MS sends weird REFER and FS can not handle it it the same way > like FS does for zoiper. > > Please advice. > > > > > > > > On Thu, 14 May 2020 at 18:39, Sergiu Pojoga pojogas@gmail.com > wrote: > >> Remove the REFER from Supported header if you want MS to initiate a >> separate call leg, it's described in the direct dialing documentation. >> >> Cheers. >> >> On Thu, May 14, 2020, 11:14 AM Yuriy Nasida, ynasida@gmail.com >> wrote: >> >>> Well, I saw similar questions in the list already but looks like >>> nobody has answer. >>> >>> Please look at REFER below. >>> >>> Kamilio get REFER from MS and sends it to FS node. Next, FS node >>> try to make 3th call for some reason.I expect that FS will not do 3th call >>> and just will connect Alice and Bob itself. >>> >>> >>> 2020/05/14 12:32:00.637027 KAM_IP:5060 -> FS_IP:5060 >>> REFER sip:Alice_number@FS_IP:5060;transport=udp SIP/2.0 >>> FROM: Customer1sip:MS_TRUNK_NUMBER@sip.pstnhub.microsoft.com:5061 >> ;user=phone>;tag=a860c50a3fb54d08b4e5740fa2dfb3d6 >>> TO: sip:Alice_number@FQDN_OF_TRUNK >> :5061>;user=phone;tag=e8ct9S6ty13va >>> CSEQ: 4 REFER >>> CALL-ID: 2c71b2a6669b5343a231e1244b19c945 >>> MAX-FORWARDS: 50 >>> Via: SIP/2.0/UDP >>> FQDN_OF_TRUNK:5060;branch=z9hG4bK10ae.2c42897feca117121a23bf0c8d54cd19.0;i=c >>> VIA: SIP/2.0/TLS 52.114.75.24:5061;branch=z9hG4bK7e3e8998 >>> CONTACT: sip:api-du-a-euwe.pstnhub.microsoft.com:443 >> ;x-i=6b68e7aa-f5e2-44ec-9edf-0bacbabfce07;x-c=2c71b2a6669b5343a231e1244b19c945/d/8/b68f86794a8e44d19543f8edbee6b2fc >>> CONTENT-LENGTH: 0 >>> REFER-TO: sip:Bob_number@sip.pstnhub.microsoft.com:5061 >> ;user=phone;transport=tls> >>> REFERRED-BY: sip:sip.pstnhub.microsoft.com:5061 >> ;x-m=8:orgid:21bc47d3-c050-4292-8234-46f7005b97aa;x-t=fb788ef8-3c4c-455a-8d62-f3c20832c0d3;x-ti=6b68e7aa-f5e2-44ec-9edf- >>> >>> acbabfce07;x-tt=aHR0cHM6Ly9hcGktZHUtYS1ldXdlLnBzdG5odWIubWljcm9zb2Z0LmNvbS92MS9uZ2MvY2FsbG5vdGlmaWNhdGlvbj9kY2k9YzIxMjE3MzEyNTQ2NDk1ZjlhYTcwODliYTkwNGIxZGQ%3D> >>> USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2020.5.6.2 i.EUWE.4 >>> ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY >>> P-ASSERTED-IDENTITY: tel:MS_TRUNK_NUMBER,< >>> sip:customer1@m365x587912.onmicrosoft.com> >>> PRIVACY: id >>> X-AUTH-IP: 52.114.75.24 >>> X-AUTH-PORT: 3136 >>> >>> >>> Any advice? >>> >>> >>> >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users@lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users@lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users@lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337 _______________________________________________ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi Yuriy, regarding REFER, MS does not follow RFC at all!!!! I can tell you for sure. In REFER-TO it pretend to have Request-URI IP address. So is not telling you to who "REFER TO" but it telling you that it want to handle itself. Very strange interpretation of RFS ;-)
Anyway, can you share your working code? Thanks
-- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html
-
Agiftel -
David Villasmil -
Sergiu Pojoga -
Yuriy Nasida