Hi Bogdan, I would like to handle the attended transfer.
Thanks in advance, Santi Antón Responsable de operaciones Tel. 902 520 520 ext 106 Fax. 93 589 14 90 [email protected] 902 520 520 www.quarea.com Quarea ITC Management & Consulting Su experto en Redes Voz-Datos IP: Asterisk, Cisco, Polycom, Colt Telecom Este mensaje está dirigido únicamente a su destinatario. Contiene información CONFIDENCIAL sometida a secreto profesional o cuya divulgación está prohibida por la ley. Si ha recibido este mensaje por error, debe saber que su lectura, copia y uso no están autorizados. Le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. El correo electrónico vía Internet no permite asegurar la confidencialidad de los mensajes que se transmiten ni su integridad o correcta recepción. QUAREA no asume responsabilidad por estas circunstancias y se reserva el derecho a ejercer las acciones legales que le correspondan contra todo tercero que acceda de forma ilegítima al contenido de este mensaje y al de los ficheros contenidos en el mismo. Si el destinatario de este mensaje no consintiera la utilización del correo electrónico vía Internet y la grabación de los mensajes, rogamos lo ponga en nuestro conocimiento de forma inmediata. De conformidad con la LOPD y la LSSICE, le informamos que su correo electrónico forma parte de nuestra BBDD de contactos con la finalidad de enviarle información de nuestros productos. Puede ejercer sus derechos de acceso, rectificación, cancelación y oposición dirigiendo un escrito a [email protected] indicando en el asunto LOPD. -----Mensaje original----- De: [email protected] [mailto:[email protected]] En nombre de Bogdan-Andrei Iancu Enviado el: lunes, 16 de junio de 2014 17:25 Para: Santi Antón; OpenSIPS users mailling list Asunto: Re: [OpenSIPS-Users] Second call on transferred with B2B refer scenario Hi Santi, Thanks for the logs - now I understand you want to put an attended transfer through OpenSIPS, but attended (handled by OpenSIPS) does not work (only un-attended or REFER pass through). Do you want OpenSIPS to handle the attended transfer, or you want to be transparent and allow the end point to handle it ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com On 16.06.2014 11:48, Santi Antón wrote: > Hi Bogdan, > > Next you can find a link to Refer log. > > https://drive.google.com/file/d/0B3db2bUGbNDQT2F1cDlQNlF2aVU/edit?usp= > sharing > > Regards, > > > Santi Antón > Responsable de operaciones > > Tel. 902 520 520 ext 106 > Fax. 93 589 14 90 > > [email protected] > > > > > > > > 902 520 520 > www.quarea.com > Quarea ITC Management & Consulting > Su experto en Redes Voz-Datos IP: > Asterisk, Cisco, Polycom, Colt Telecom > > > > > Este mensaje está dirigido únicamente a su destinatario. Contiene información > CONFIDENCIAL sometida a secreto profesional o cuya divulgación está prohibida > por la ley. Si ha recibido este mensaje por error, debe saber que su lectura, > copia y uso no están autorizados. Le rogamos que nos lo comunique > inmediatamente por esta misma vía y proceda a su destrucción. El correo > electrónico vía Internet no permite asegurar la confidencialidad de los > mensajes que se transmiten ni su integridad o correcta recepción. QUAREA no > asume responsabilidad por estas circunstancias y se reserva el derecho a > ejercer las acciones legales que le correspondan contra todo tercero que > acceda de forma ilegítima al contenido de este mensaje y al de los ficheros > contenidos en el mismo. Si el destinatario de este mensaje no consintiera la > utilización del correo electrónico vía Internet y la grabación de los > mensajes, rogamos lo ponga en nuestro conocimiento de forma inmediata. > De conformidad con la LOPD y la LSSICE, le informamos que su correo > electrónico forma parte de nuestra BBDD de contactos con la finalidad de > enviarle información de nuestros productos. Puede ejercer sus derechos de > acceso, rectificación, cancelación y oposición dirigiendo un escrito a > [email protected] indicando en el asunto LOPD. > > > > > > > > > > > > > > > > > > > > > > > > -----Mensaje original----- > De: Bogdan-Andrei Iancu [mailto:[email protected]] Enviado el: > viernes, 13 de junio de 2014 13:25 > Para: OpenSIPS users mailling list; Santi Antón > Asunto: Re: [OpenSIPS-Users] Second call on transferred with B2B refer > scenario > > Hi Santi, > > Indeed there is no new Refer-To hdr in the resulting INVITE (frame 38). > As you can reproduce it, could you please run in full debug (debug=4) and > send me the logs corresponding to the REFER processing ? > > Thank and Regards, > > Bogdan-Andrei Iancu > OpenSIPS Founder and Developer > http://www.opensips-solutions.com > > On 11.06.2014 13:06, Santi Antón wrote: >> Hi, >> >> Nobody else had found the same issue trying refer scenario with b2b module? >> Someone has a valid opensips.cfg to compare it with mine? >> >> Regards, >> >> Santi Antón >> >> >> >> -----Mensaje original----- >> De: Santi Antón >> Enviado el: miércoles, 04 de junio de 2014 11:04 >> Para: OpenSIPS users mailling list; 'Bogdan-Andrei Iancu' >> Asunto: RE: [OpenSIPS-Users] Second call on transferred with B2B >> refer scenario >> >> Hi Bogdan, >> >> Do you need my opensips.cfg? It seems very strange that this issue could be >> general, I think that maybe I'm making a mistake in opensips configuration. >> >> Regards, >> >> >> Santi Antón >> >> >> -----Mensaje original----- >> De: [email protected] >> [mailto:[email protected]] En nombre de Santi Antón >> Enviado el: miércoles, 28 de mayo de 2014 9:35 >> Para: 'Bogdan-Andrei Iancu'; OpenSIPS users mailling list >> Asunto: Re: [OpenSIPS-Users] Second call on transferred with B2B >> refer scenario >> >> Hi Bogdan, >> >> Yes, it is. >> >> Thanks in advance, >> >> >> Santi Antón >> >> >>> -----Mensaje original----- >>> De: Bogdan-Andrei Iancu [mailto:[email protected]] Enviado el: >>> miércoles, 28 de mayo de 2014 8:15 >>> Para: OpenSIPS users mailling list; Santi Antón >>> Asunto: Re: [OpenSIPS-Users] Second call on transferred with B2B >>> refer scenario >>> >>> Hi, >>> >>> You mean the frame 38 in your trace, right ? Indeed the TO should have only >>> the URI, not the REPLACE stuff ....I will look into. >>> >>> Regards, >>> >>> Bogdan-Andrei Iancu >>> OpenSIPS Founder and Developer >>> http://www.opensips-solutions.com >>> >>> On 27.05.2014 17:10, Santi Antón wrote: >>> Hello, >>> >>> I noticed that INVITE with Replaces header is built like this: >>> >>> INVITE sip:[email protected]:5063 SIP/2.0 >>> Record-Route: <sip:172.16.53.59;lr> >>> Via: SIP/2.0/UDP 172.16.53.59:5060;branch=z9hG4bK4867.fe529da6.0 >>> Via: SIP/2.0/UDP 172.16.53.59:5060;branch=z9hG4bK4867.ee529da6.0 >>> To: >>> sip:[email protected]?Replaces=377952018%40172.16.51.138%3Bto-tag%3D >>> B >>> 2 >>> B.124.358%3Bfrom-tag%3D741375670 >>> From: >>> <sip:[email protected];transport=UDP>;tag=fde67a95c41efd29d5eb8ddaec >>> d >>> b >>> abf0-9cb9 >>> CSeq: 4 INVITE >>> Call-ID: B2B.345.6691153 >>> Max-Forwards: 69 >>> Content-Length: 376 >>> User-Agent: OpenSIPS (1.10.1-notls (x86_64/linux)) >>> Content-Type: application/sdp >>> Supported: replaces, norefersub, extended-refer, timer, >>> X-cisco-serviceuri >>> Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, >>> INFO, SUBSCRIBE >>> Contact: <sip:172.16.53.59:5060> >>> >>> >>> The replaces header is inside "To" header, is it correct? The examples I >>> saw the Replaces header has an independent header like next: >>> >>> F6 INVITE Transferee -> Transfer Target >>> >>> INVITE sips:[email protected];gr=8594958 SIP/2.0 >>> Via: SIP/2.0/TLS 192.0.2.4;branch=z9hG4bKnaslu82 >>> Max-Forwards: 70 >>> To: <sips:[email protected];gr=8594958> >>> From: <sips:[email protected]>;tag=954 >>> Call-ID: kmzwdle3dl3d08 >>> CSeq: 41 INVITE >>> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY >>> Supported: gruu, replaces, tdialog >>> Contact: <sips:[email protected];gr=3413kj2ha> >>> Replaces: 592435881734450904;to-tag=9m2n3wq;from-tag=763231 >>> Content-Type: application/sdp >>> Content-Length: ... >>> >>> Regards, >>> >>> Santi Antón >>> >>> >>>> -----Mensaje original----- >>>> De: Santi Antón >>>> Enviado el: lunes, 26 de mayo de 2014 9:46 >>>> Para: '[email protected]'; 'Bogdan-Andrei Iancu' >>>> Asunto: RV: [OpenSIPS-Users] Second call on transferred with B2B >>>> refer scenario >>>> >>>> Oh, I forget to attach the file. Next you can find a link to pcap. >>>> >>>> https://drive.google.com/file/d/0B3db2bUGbNDQWFIzSjhoVFFKVUk/edit?u >>>> s >>>> p >>>> =sharing >>>> >>>> Regards, >>>> >>>> Santi Antón >>>> >>>> >>>> -----Mensaje original----- >>>> De: Bogdan-Andrei Iancu [mailto:[email protected]] Enviado el: >>>> jueves, 22 de mayo de 2014 18:29 >>>> Para: [email protected]; Santi Antón >>>> Asunto: Re: [OpenSIPS-Users] Second call on transferred with B2B >>>> refer scenario >>>> >>>> Hello Santi, >>>> >>>> There is nothing attached and it is not a good practice to have large >>>> attachments on the mailing lists (as you are flooding the inboxes). >>>> Better uploade your trace on a pastebin like side (or store pcap on >>>> ftp/http servers) and just post the link. >>>> >>>> Regards, >>>> >>>> Bogdan-Andrei Iancu >>>> OpenSIPS Founder and Developer >>>> http://www.opensips-solutions.com >>>> >>>> On 22.05.2014 13:28, Santi Antón wrote: >>>> Hello, >>>> >>>> I'm trying to implement attendant transfer capability to our Opensips >>>> server with the b2b module and refer.xml scenario. >>>> Attended transfer works fine except the transferred receives a new call >>>> rather than update the ongoing call with transferor. >>>> Looking for the cause I saw that from tag is different between the initial >>>> call (INVITE) to transferred and the from tag in Replaces header (INVITE). >>>> I think the two from tag have to be the same to consider the second INVITE >>>> an update and not a new call. >>>> Attached you can find a capture with an isolated example (9443 calls 9441 >>>> and does an attended transfer to 9442). >>>> Maybe I'm not understanding the module behavior but I couldn't find any >>>> clue in module's documentation. >>>> >>>> Thanks in advance, >>>> >>>> Santi Antón >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Users mailing list >>>> [email protected] >>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>>> >>>> >>> _______________________________________________ >>> Users mailing list >>> [email protected] >>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >>> >>> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> _______________________________________________ >> Users mailing list >> [email protected] >> http://lists.opensips.org/cgi-bin/mailman/listinfo/users >> >> _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
