Re: [Freeswitch-users] FreeSwitch and Click 2 Call
What's the problem again? perhaps you should open an issue on jira: http://jira.freeswitch.org That would make it easier to track an ongoing issue since this is simply a mailing list. Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ AIM: anthm MSN:anthony_minessale@hotmail.com JABBER:anthony.minessale@gmail.com IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org pstn:213-799-1400 ----- Original Message ---- From: Helmut Kuper <helmut.kuper@ewetel.de> To: freeswitch-users@lists.freeswitch.org Sent: Tuesday, March 13, 2007 3:26:48 AM Subject: Re: [Freeswitch-users] FreeSwitch and Click 2 Call -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, is there anything new to this ? regards helmut Helmut Kuper schrieb:
Hello,
I downloaded today the actual SVN trunk (4488) of freeswitch and compiled it. I tested again my C2C szenario and have to say it still doesn't work. I get this console output of freeswitch:
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF9mBI4tZeNddg3dwRAqElAKCF60HeER7Ls1JtyoRSOazv84l33gCghg3c JIPkadUHwWuDa3Io38c0Au4= =2QpJ -----END PGP SIGNATURE----- _______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org ____________________________________________________________________________________ We won't tell. Get more on shows you hate to love (and love to hate): Yahoo! TV's Guilty Pleasures list. http://tv.yahoo.com/collections/265
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Anthony, I did that already (FSCORE-21). Problem is, that freeSWITCH is not able to be used in a 3pcc environment. regrads Helmut Anthony Minessale schrieb:
What's the problem again?
perhaps you should open an issue on jira:
That would make it easier to track an ongoing issue since this is simply a mailing list.
Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF97Dv4tZeNddg3dwRAgcIAJ4mqL5f+cPMi3/0Qh1bpZuA0h1XTgCgrY9C q+JByMINnitwKFyqfUqq2GQ= =+U1x -----END PGP SIGNATURE-----
Can you attach a working sip trace vs a non-working? So we can see what it should be doing? On Mar 14, 2007, at 3:23 AM, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Anthony,
I did that already (FSCORE-21). Problem is, that freeSWITCH is not able to be used in a 3pcc environment.
regrads Helmut
Anthony Minessale schrieb:
What's the problem again?
perhaps you should open an issue on jira:
That would make it easier to track an ongoing issue since this is simply a mailing list.
Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF97Dv4tZeNddg3dwRAgcIAJ4mqL5f+cPMi3/0Qh1bpZuA0h1XTgCgrY9C q+JByMINnitwKFyqfUqq2GQ= =+U1x -----END PGP SIGNATURE-----
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, unfortunately not. I attached a screenshot from the INVITE whis is sent to freeswitch to case FSCORE-21. freeSWITCH response to this with a 100-Trying. After that there is no acation from freeSWITCH anymore to this INVITE. I don't have a working SIP-Flow-Trace for 3pcc, but the guys at WeSIP tested 3pcc successful with asterisk. I try to get that trace from there. In RFC 3725 u can c a reference 3pcc-SIP-Flow: A Controller B |(1) INVITE no SDP | | |<------------------| | |(2) 200 offer1 | | |------------------>| | | |(3) INVITE offer1 | | |------------------>| | |(4) 200 OK answer1 | | |<------------------| | |(5) ACK | | |------------------>| |(6) ACK answer1 | | |<------------------| | |(7) RTP | | |.......................................| regards helmut Brian West schrieb:
Can you attach a working sip trace vs a non-working? So we can see what it should be doing? On Mar 14, 2007, at 3:23 AM, Helmut Kuper wrote:
Hi Anthony,
I did that already (FSCORE-21). Problem is, that freeSWITCH is not able to be used in a 3pcc environment.
regrads Helmut
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+RAF4tZeNddg3dwRArsXAKClDxvif3mWGFco/xQhN3pxvWs12ACgnuxC vMMLkbEw0tbXB4xAJRETkpw= =1ee+ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, please find attached a working 3pcc sip flow trace regards helmut Helmut Kuper schrieb:
Hi,
unfortunately not. I attached a screenshot from the INVITE whis is sent to freeswitch to case FSCORE-21. freeSWITCH response to this with a 100-Trying. After that there is no acation from freeSWITCH anymore to this INVITE.
I don't have a working SIP-Flow-Trace for 3pcc, but the guys at WeSIP tested 3pcc successful with asterisk. I try to get that trace from there. In RFC 3725 u can c a reference 3pcc-SIP-Flow:
A Controller B |(1) INVITE no SDP | | |<------------------| | |(2) 200 offer1 | | |------------------>| | | |(3) INVITE offer1 | | |------------------>| | |(4) 200 OK answer1 | | |<------------------| | |(5) ACK | | |------------------>| |(6) ACK answer1 | | |<------------------| | |(7) RTP | | |.......................................|
regards helmut
Brian West schrieb:
Can you attach a working sip trace vs a non-working? So we can see what it should be doing? On Mar 14, 2007, at 3:23 AM, Helmut Kuper wrote:
Hi Anthony,
I did that already (FSCORE-21). Problem is, that freeSWITCH is not able to be used in a 3pcc environment.
regrads Helmut
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+TuL4tZeNddg3dwRAlmJAJ0f+J7VzzQJ08/Y/ft5gC28BzYrxQCgh/pm JIdAlETrCcWNQ7oUhT0iFp8= =hb+m -----END PGP SIGNATURE----- interface: any filter: (ip) and ( port 5060 ) match: 3400000012 U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:3400000012@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK220c.19a99ca6.0..To: sip:3400000012@voztele.com..From: sip:3400000012@vozte le.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 1 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Content-Length: 0..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>.... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK220c.19a99ca6.0..To: sip:3400000012@voztele.com;tag=ba3d51acad53eeb51d56ab2 459dbff7b.bd74..From: sip:3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 1 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Pro xy-Authenticate: Digest realm="voztele.com", nonce="45f9231133cbed8cb14276720dff905025626fd0"..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Length: 0.... U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:3400000012@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK220c.19a99ca6.0..From: sip:3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170 805C1E11..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip:3400000012@voztele.com;tag=ba3d51acad53eeb51d56ab2459dbff7b.bd74..CSeq: 1 ACK..User-Agen t: OpenSer (1.2.0-dev13-notls (i386/linux))..Content-Length: 0.... U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:3400000012@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..To: sip:3400000012@voztele.com..From: sip:3400000012@vozte le.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 2 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Content-Length: 0..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>..Proxy-Authorization: Digest username="3400000012",nonce="45f9231133cbed8cb14276720dff905025626fd0",cnonce="0a4f113b",nc=00 000001,realm="voztele.com",uri="sip:3400000012@voztele.com",response="5a993a2e9e6b35f84803b1b8cc5d2789".... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 Runing CPL script.....Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..To: sip:3400000012@voztele.com..From: sip:3400000012@voztele.com;ta g=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 2 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Le ngth: 0.... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 Runing CPL script.....Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..To: sip:3400000012@voztele.com..From: sip:3400000012@voztele.com;ta g=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 2 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Le ngth: 0.... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 180 Ringing..CSeq: 2 INVITE..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..From: sip:3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805 C1E11..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip:3400000012@voztele.com;tag=4eaa8ed5-4ed1-db11-8547-c725fe65d50d..Allow: INVITE,ACK,OPTIONS, BYE,CANCEL,NOTIFY,REFER,MESSAGE,INFO,PING..Content-Length: 0..Record-Route: <sip:193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>,<sip:193.22.119.20;lr=on ;ftag=C2ED946769B0C8CC8D3D3170805C1E11>.... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 200 OK..CSeq: 2 INVITE..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..From: sip:3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11 ..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip:3400000012@voztele.com;tag=4eaa8ed5-4ed1-db11-8547-c725fe65d50d..Contact: <sip:3400000012@193.22 .119.78:5005;transport=udp>..Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE,INFO,PING..Content-Type: application/sdp..Content-Length: 306..Record-Route: <sip:193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>,<sip:193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>....v=0..o=- 1173955050 1173955050 IN IP4 193.22.119.78..s=Opal SIP Session..c=IN IP4 193.22.119.78..t=0 0..m=audio 5006 RTP/AVP 0 8 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:101 teleph one-event/8000..a=fmtp:101 0-15..m=video 5008 RTP/AVP 31 34..a=rtpmap:31 H261/90000..a=rtpmap:34 H263/90000.. U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:647460197@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK56f5.1a5193c4.0..To: sip:647460197@voztele.com..From: sip:3400000012@voztele .com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 1 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Content-Length: 306..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>..Content-Type: application/sdp....v=0..o=- 1173955050 1173955050 IN IP4 193.22.119.78..s=Opal SIP Session..c=IN IP4 193.22. 119.78..t=0 0..m=audio 5006 RTP/AVP 0 8 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-15..m=video 5008 RTP/AVP 31 34..a=rtpmap:31 H261/90000..a=rtpmap:34 H263/90000.. U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK56f5.1a5193c4.0..To: sip:647460197@voztele.com;tag=ba3d51acad53eeb51d56ab24 59dbff7b.59c4..From: sip:3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 1 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Prox y-Authenticate: Digest realm="voztele.com", nonce="45f9231693c9a9c1d3602935cf5bed06ff5801a7"..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Length: 0.... U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:647460197@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK56f5.1a5193c4.0..From: sip:3400000012@voztele.com;tag=EA0613171D364A5788BBA175A F8C4F4C..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..To: sip:647460197@voztele.com;tag=ba3d51acad53eeb51d56ab2459dbff7b.59c4..CSeq: 1 ACK..User-Agent: OpenSer (1.2.0-dev13-notls (i386/linux))..Content-Length: 0.... U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:647460197@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..To: sip:647460197@voztele.com..From: sip:3400000012@voztele .com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 2 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Content-Length: 306..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>..Proxy-Authorization: Digest username="3400000012",nonce="45f9231693c9a9c1d3602935cf5bed06ff5801a7",cnonce="0a4f113b",nc=00 000001,realm="voztele.com",uri="sip:647460197@voztele.com",response="526f5a60cb08e19a19c752fb7cc412e9"..Content-Type: application/sdp....v=0..o=- 1173955050 1173955 050 IN IP4 193.22.119.78..s=Opal SIP Session..c=IN IP4 193.22.119.78..t=0 0..m=audio 5006 RTP/AVP 0 8 101..a=rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-15..m=video 5008 RTP/AVP 31 34..a=rtpmap:31 H261/90000..a=rtpmap:34 H263/90000.. U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 Runing CPL script.....Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..To: sip:647460197@voztele.com..From: sip:3400000012@voztele.com;tag =EA0613171D364A5788BBA175AF8C4F4C..CSeq: 2 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Len gth: 0.... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..To: sip:647460197@voztele.com..From: sip:34000000 12@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 2 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/li nux))..Content-Length: 0.... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 183 Session Progress..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..From: sip:3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C.. To: sip:647460197@voztele.com;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c.b..Date: Thu, 15 Mar 2007 10:37:30 GMT..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.2 2.119.197..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 2 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGIST ER..Allow-Events: telephone-event..Contact: <sip:99920010034647460197@193.22.119.34:5060>..Record-Route: <sip:193.22.119.10;lr=on>,<sip:193.22.119.20;lr=on;ftag=EA0 613171D364A5788BBA175AF8C4F4C>..Content-Disposition: session;handling=required..Content-Type: application/sdp..Content-Length: 326....v=0..o=CiscoSystemsSIP-GW-User Agent 2178 2841 IN IP4 193.22.119.34..s=SIP Call..c=IN IP4 193.22.119.34..t=0 0..m=audio 17108 RTP/AVP 0 101..c=IN IP4 193.22.119.34..a=rtpmap:0 PCMU/8000..a=rtpmap :101 telephone-event/8000..a=fmtp:101 0-15..a=direction:passive..m=video 0 RTP/AVP 31..c=IN IP4 193.22.119.34..a=direction:passive.. U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..From: sip:3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..To: sip:647460 197@voztele.com;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c.b..Date: Thu, 15 Mar 2007 10:37:30 GMT..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Ser ver: Cisco-SIPGateway/IOS-12.x..CSeq: 2 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Even ts: telephone-event..Contact: <sip:99920010034647460197@193.22.119.34:5060>..Record-Route: <sip:193.22.119.10;lr=on>,<sip:193.22.119.20;lr=on;ftag=EA0613171D364A578 8BBA175AF8C4F4C>..Content-Type: application/sdp..Content-Length: 326....v=0..o=CiscoSystemsSIP-GW-UserAgent 2178 2841 IN IP4 193.22.119.34..s=SIP Call..c=IN IP4 193 .22.119.34..t=0 0..m=audio 17108 RTP/AVP 0 101..c=IN IP4 193.22.119.34..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-15..a=direction:passiv e..m=video 0 RTP/AVP 31..c=IN IP4 193.22.119.34..a=direction:passive.. U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:99920010034647460197@193.22.119.34:5060 SIP/2.0..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..CSeq: 2 ACK..From: <sip:3400000012@voztele.com>;t ag=EA0613171D364A5788BBA175AF8C4F4C..To: <sip:647460197@voztele.com>;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c.b..Max-Forwards: 70..Proxy-Authorization: Digest username="3400000012",nonce="45f9231693c9a9c1d3602935cf5bed06ff5801a7",cnonce="0a4f113b",nc=00000001,realm="voztele.com",uri="sip:647460197@voztele.com",response=" 526f5a60cb08e19a19c752fb7cc412e9"..Via: SIP/2.0/UDP 193.22.119.197:5060;branch=z9hG4bK525822650..Route: <sip:193.22.119.20;lr=on;ftag=EA0613171D364A5788BBA175AF8C4F 4C>,<sip:193.22.119.10;lr=on>..Content-Length: 0.... U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:3400000012@193.22.119.78:5005;transport=udp SIP/2.0..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..CSeq: 2 ACK..From: <sip:3400000012@voztele.co m>;tag=C2ED946769B0C8CC8D3D3170805C1E11..To: <sip:3400000012@voztele.com>;tag=4eaa8ed5-4ed1-db11-8547-c725fe65d50d..Max-Forwards: 70..Proxy-Authorization: Digest us ername="3400000012",nonce="45f9231133cbed8cb14276720dff905025626fd0",cnonce="0a4f113b",nc=00000001,realm="voztele.com",uri="sip:3400000012@voztele.com",response="5a 993a2e9e6b35f84803b1b8cc5d2789"..Via: SIP/2.0/UDP 193.22.119.197:5060;branch=z9hG4bK525822651..Route: <sip:193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11
,<sip:193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>..Content-Type: application/sdp..Content-Length: 326....v=0..o=CiscoSystemsSIP-GW-UserAgent 2178 28 41 IN IP4 193.22.119.34..s=SIP Call..c=IN IP4 193.22.119.34..t=0 0..m=audio 17108 RTP/AVP 0 101..c=IN IP4 193.22.119.34..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephon e-event/8000..a=fmtp:101 0-15..a=direction:passive..m=video 0 RTP/AVP 31..c=IN IP4 193.22.119.34..a=direction:passive..
U 193.22.119.20:5060 -> 193.22.119.197:5060 BYE sip:193.22.119.197:5060;transport=udp SIP/2.0..CSeq: 1 BYE..Via: SIP/2.0/UDP 193.22.119.20;branch=z9hG4bK220c.ef532856.0..Via: SIP/2.0/UDP 193.22.119.20;branch= z9hG4bK220c.df532856.0..Via: SIP/2.0/UDP 193.22.119.78:5005;branch=z9hG4bKba4d4ede-4ed1-db11-8547-c725fe65d50d;rport=5005..From: sip:3400000012@voztele.com;tag=4eaa 8ed5-4ed1-db11-8547-c725fe65d50d..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip:3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..Con tact: <sip:gines@193.22.119.78:5005;transport=udp>..Content-Length: 0..Max-Forwards: 11.... U 193.22.119.197:5060 -> 193.22.119.20:5060 BYE sip:99920010034647460197@193.22.119.34:5060 SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK36f5.632d3c94.0..To: sip:647460197@voztele.com;tag=gj-2k5-45f 58af2-00007916-00000dccR99ff1e6c.b..From: sip:3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 3 BYE..Call-ID: C51B01C56457BE9C94060359F25C8A18@19 3.22.119.197..Route: <sip:193.22.119.20;lr=on;ftag=EA0613171D364A5788BBA175AF8C4F4C>,.. <sip:193.22.119.10;lr=on>..Content-Length: 0..Max-Forwards: 70..Contac t: <sip:193.22.119.197:5060;transport=udp>.... U 193.22.119.197:5060 -> 193.22.119.20:5060 SIP/2.0 200 OK..CSeq: 1 BYE..Via: SIP/2.0/UDP 193.22.119.20;branch=z9hG4bK220c.ef532856.0..Via: SIP/2.0/UDP 193.22.119.20;branch=z9hG4bK220c.df532856.0..Via: SIP/2. 0/UDP 193.22.119.78:5005;branch=z9hG4bKba4d4ede-4ed1-db11-8547-c725fe65d50d;rport=5005..From: sip:3400000012@voztele.com;tag=4eaa8ed5-4ed1-db11-8547-c725fe65d50d..C all-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip:3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..Max-Forwards: 11..Content-Length: 0..W arning: 392 193.22.119.197:5060 "Noisy feedback tells: pid=28352 req_src_ip=193.22.119.20 req_src_port=5060 in_uri=sip:193.22.119.197:5060;transport=udp out_uri=si p:193.22.119.197:5060;transport=udp via_cnt==4147".... U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK36f5.632d3c94.0..From: sip:3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..To: sip:647460 197@voztele.com;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c.b..Date: Thu, 15 Mar 2007 10:37:40 GMT..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Ser ver: Cisco-SIPGateway/IOS-12.x..Content-Length: 0..CSeq: 3 BYE....
Please attach it to the bug report in jira! /b On Mar 15, 2007, at 7:26 AM, Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
please find attached a working 3pcc sip flow trace
regards helmut
Helmut Kuper schrieb:
Hi,
unfortunately not. I attached a screenshot from the INVITE whis is sent to freeswitch to case FSCORE-21. freeSWITCH response to this with a 100-Trying. After that there is no acation from freeSWITCH anymore to this INVITE.
I don't have a working SIP-Flow-Trace for 3pcc, but the guys at WeSIP tested 3pcc successful with asterisk. I try to get that trace from there. In RFC 3725 u can c a reference 3pcc-SIP-Flow:
A Controller B |(1) INVITE no SDP | | |<------------------| | |(2) 200 offer1 | | |------------------>| | | |(3) INVITE offer1 | | |------------------>| | |(4) 200 OK answer1 | | |<------------------| | |(5) ACK | | |------------------>| |(6) ACK answer1 | | |<------------------| | |(7) RTP | | |.......................................|
regards helmut
Brian West schrieb:
Can you attach a working sip trace vs a non-working? So we can see what it should be doing? On Mar 14, 2007, at 3:23 AM, Helmut Kuper wrote:
Hi Anthony,
I did that already (FSCORE-21). Problem is, that freeSWITCH is not able to be used in a 3pcc environment.
regrads Helmut
_______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF+TuL4tZeNddg3dwRAlmJAJ0f+J7VzzQJ08/Y/ft5gC28BzYrxQCgh/pm JIdAlETrCcWNQ7oUhT0iFp8= =hb+m -----END PGP SIGNATURE----- interface: any filter: (ip) and ( port 5060 ) match: 3400000012
U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:3400000012@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK220c.19a99ca6.0..To: sip: 3400000012@voztele.com..From: sip:3400000012@vozte le.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 1 INVITE..Call- ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Content- Length: 0..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>....
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK220c.19a99ca6.0..To: sip: 3400000012@voztele.com;tag=ba3d51acad53eeb51d56ab2 459dbff7b.bd74..From: sip: 3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 1 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Pro xy-Authenticate: Digest realm="voztele.com", nonce="45f9231133cbed8cb14276720dff905025626fd0"..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Length: 0....
U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:3400000012@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK220c.19a99ca6.0..From: sip: 3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170 805C1E11..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip: 3400000012@voztele.com;tag=ba3d51acad53eeb51d56ab2459dbff7b.bd74..CSeq : 1 ACK..User-Agen t: OpenSer (1.2.0-dev13-notls (i386/linux))..Content-Length: 0....
U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:3400000012@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..To: sip: 3400000012@voztele.com..From: sip:3400000012@vozte le.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 2 INVITE..Call- ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Content- Length: 0..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>..Proxy-Authorization: Digest username="3400000012",nonce="45f9231133cbed8cb14276720dff905025626fd0" ,cnonce="0a4f113b",nc=00 000001,realm="voztele.com",uri="sip: 3400000012@voztele.com",response="5a993a2e9e6b35f84803b1b8cc5d2789"... .
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 Runing CPL script.....Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..To: sip: 3400000012@voztele.com..From: sip:3400000012@voztele.com;ta g=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 2 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Le ngth: 0....
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 Runing CPL script.....Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..To: sip: 3400000012@voztele.com..From: sip:3400000012@voztele.com;ta g=C2ED946769B0C8CC8D3D3170805C1E11..CSeq: 2 INVITE..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Le ngth: 0....
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 180 Ringing..CSeq: 2 INVITE..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..From: sip: 3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805 C1E11..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip: 3400000012@voztele.com;tag=4eaa8ed5-4ed1-db11-8547- c725fe65d50d..Allow: INVITE,ACK,OPTIONS, BYE,CANCEL,NOTIFY,REFER,MESSAGE,INFO,PING..Content-Length: 0..Record-Route: <sip: 193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>,<sip: 193.22.119.20;lr=on ;ftag=C2ED946769B0C8CC8D3D3170805C1E11>....
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 200 OK..CSeq: 2 INVITE..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bKf10c.767a1766.0..From: sip: 3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11 ..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip:3400000012@voztele.com;tag=4eaa8ed5-4ed1-db11-8547- c725fe65d50d..Contact: <sip:3400000012@193.22 .119.78:5005;transport=udp>..Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE,INFO,PING..Content- Type: application/sdp..Content-Length: 306..Record-Route: <sip: 193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>,<sip: 193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>....v=0..o=- 1173955050 1173955050 IN IP4 193.22.119.78..s=Opal SIP Session..c=IN IP4 193.22.119.78..t=0 0..m=audio 5006 RTP/AVP 0 8 101..a=rtpmap:0 PCMU/ 8000..a=rtpmap:8 PCMA/8000..a=rtpmap:101 teleph one-event/8000..a=fmtp:101 0-15..m=video 5008 RTP/AVP 31 34..a=rtpmap:31 H261/90000..a=rtpmap:34 H263/90000..
U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:647460197@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK56f5.1a5193c4.0..To: sip: 647460197@voztele.com..From: sip:3400000012@voztele .com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 1 INVITE..Call- ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Content- Length: 306..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>..Content-Type: application/sdp....v=0..o=- 1173955050 1173955050 IN IP4 193.22.119.78..s=Opal SIP Session..c=IN IP4 193.22. 119.78..t=0 0..m=audio 5006 RTP/AVP 0 8 101..a=rtpmap:0 PCMU/ 8000..a=rtpmap:8 PCMA/8000..a=rtpmap:101 telephone-event/ 8000..a=fmtp:101 0-15..m=video 5008 RTP/AVP 31 34..a=rtpmap:31 H261/90000..a=rtpmap:34 H263/90000..
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK56f5.1a5193c4.0..To: sip: 647460197@voztele.com;tag=ba3d51acad53eeb51d56ab24 59dbff7b.59c4..From: sip: 3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 1 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Prox y-Authenticate: Digest realm="voztele.com", nonce="45f9231693c9a9c1d3602935cf5bed06ff5801a7"..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Length: 0....
U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:647460197@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK56f5.1a5193c4.0..From: sip: 3400000012@voztele.com;tag=EA0613171D364A5788BBA175A F8C4F4C..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..To: sip: 647460197@voztele.com;tag=ba3d51acad53eeb51d56ab2459dbff7b. 59c4..CSeq: 1 ACK..User-Agent: OpenSer (1.2.0-dev13-notls (i386/linux))..Content-Length: 0....
U 193.22.119.197:5060 -> 193.22.119.20:5060 INVITE sip:647460197@voztele.com SIP/2.0..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..To: sip: 647460197@voztele.com..From: sip:3400000012@voztele .com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 2 INVITE..Call- ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Content- Length: 306..Max-Forwards: 70..Contact: <sip:193.22.119.197:5060;transport=udp>..Proxy-Authorization: Digest username="3400000012",nonce="45f9231693c9a9c1d3602935cf5bed06ff5801a7" ,cnonce="0a4f113b",nc=00 000001,realm="voztele.com",uri="sip: 647460197@voztele.com",response="526f5a60cb08e19a19c752fb7cc412e9"..Co ntent-Type: application/sdp....v=0..o=- 1173955050 1173955 050 IN IP4 193.22.119.78..s=Opal SIP Session..c=IN IP4 193.22.119.78..t=0 0..m=audio 5006 RTP/AVP 0 8 101..a=rtpmap:0 PCMU/ 8000..a=rtpmap:8 PCMA/8000..a=rtpmap:101 telephone-event/8000..a=fmtp:101 0-15..m=video 5008 RTP/AVP 31 34..a=rtpmap:31 H261/90000..a=rtpmap:34 H263/90000..
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 Runing CPL script.....Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..To: sip: 647460197@voztele.com..From: sip:3400000012@voztele.com;tag =EA0613171D364A5788BBA175AF8C4F4C..CSeq: 2 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/linux))..Content-Len gth: 0....
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 100 trying -- your call is important to us..Via: SIP/2.0/ UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..To: sip: 647460197@voztele.com..From: sip:34000000 12@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 2 INVITE..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Server: OpenSer (1.1.1-notls (i386/li nux))..Content-Length: 0....
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 183 Session Progress..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..From: sip: 3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C.. To: sip: 647460197@voztele.com;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c.b ..Date: Thu, 15 Mar 2007 10:37:30 GMT..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.2 2.119.197..Server: Cisco-SIPGateway/IOS-12.x..CSeq: 2 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGIST ER..Allow-Events: telephone-event..Contact: <sip: 99920010034647460197@193.22.119.34:5060>..Record-Route: <sip: 193.22.119.10;lr=on>,<sip:193.22.119.20;lr=on;ftag=EA0 613171D364A5788BBA175AF8C4F4C>..Content-Disposition: session;handling=required..Content-Type: application/sdp..Content- Length: 326....v=0..o=CiscoSystemsSIP-GW-User Agent 2178 2841 IN IP4 193.22.119.34..s=SIP Call..c=IN IP4 193.22.119.34..t=0 0..m=audio 17108 RTP/AVP 0 101..c=IN IP4 193.22.119.34..a=rtpmap:0 PCMU/8000..a=rtpmap :101 telephone-event/8000..a=fmtp:101 0-15..a=direction:passive..m=video 0 RTP/AVP 31..c=IN IP4 193.22.119.34..a=direction:passive..
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK26f5.76f7d8c3.0..From: sip: 3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..To: sip:647460
197@voztele.com;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c.b..Date : Thu, 15 Mar 2007 10:37:30 GMT..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Ser ver: Cisco-SIPGateway/IOS-12.x..CSeq: 2 INVITE..Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, COMET, REFER, SUBSCRIBE, NOTIFY, INFO, UPDATE, REGISTER..Allow-Even ts: telephone-event..Contact: <sip: 99920010034647460197@193.22.119.34:5060>..Record-Route: <sip: 193.22.119.10;lr=on>,<sip:193.22.119.20;lr=on;ftag=EA0613171D364A578 8BBA175AF8C4F4C>..Content-Type: application/sdp..Content-Length: 326....v=0..o=CiscoSystemsSIP-GW-UserAgent 2178 2841 IN IP4 193.22.119.34..s=SIP Call..c=IN IP4 193 .22.119.34..t=0 0..m=audio 17108 RTP/AVP 0 101..c=IN IP4 193.22.119.34..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephone-event/ 8000..a=fmtp:101 0-15..a=direction:passiv e..m=video 0 RTP/AVP 31..c=IN IP4 193.22.119.34..a=direction:passive..
U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:99920010034647460197@193.22.119.34:5060 SIP/2.0..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..CSeq: 2 ACK..From: <sip:3400000012@voztele.com>;t ag=EA0613171D364A5788BBA175AF8C4F4C..To: <sip: 647460197@voztele.com>;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c. b..Max-Forwards: 70..Proxy-Authorization: Digest
username="3400000012",nonce="45f9231693c9a9c1d3602935cf5bed06ff5801a7" ,cnonce="0a4f113b",nc=00000001,realm="voztele.com",uri="sip: 647460197@voztele.com",response=" 526f5a60cb08e19a19c752fb7cc412e9"..Via: SIP/2.0/UDP 193.22.119.197:5060;branch=z9hG4bK525822650..Route: <sip: 193.22.119.20;lr=on;ftag=EA0613171D364A5788BBA175AF8C4F 4C>,<sip:193.22.119.10;lr=on>..Content-Length: 0....
U 193.22.119.197:5060 -> 193.22.119.20:5060 ACK sip:3400000012@193.22.119.78:5005;transport=udp SIP/2.0..Call- ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..CSeq: 2 ACK..From: <sip:3400000012@voztele.co m>;tag=C2ED946769B0C8CC8D3D3170805C1E11..To: <sip: 3400000012@voztele.com>;tag=4eaa8ed5-4ed1-db11-8547- c725fe65d50d..Max-Forwards: 70..Proxy-Authorization: Digest us
ername="3400000012",nonce="45f9231133cbed8cb14276720dff905025626fd0",c nonce="0a4f113b",nc=00000001,realm="voztele.com",uri="sip: 3400000012@voztele.com",response="5a 993a2e9e6b35f84803b1b8cc5d2789"..Via: SIP/2.0/UDP 193.22.119.197:5060;branch=z9hG4bK525822651..Route: <sip: 193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11
,<sip: 193.22.119.20;lr=on;ftag=C2ED946769B0C8CC8D3D3170805C1E11>..Content-T ype: application/sdp..Content-Length: 326....v=0..o=CiscoSystemsSIP-GW-UserAgent 2178 28 41 IN IP4 193.22.119.34..s=SIP Call..c=IN IP4 193.22.119.34..t=0 0..m=audio 17108 RTP/AVP 0 101..c=IN IP4 193.22.119.34..a=rtpmap:0 PCMU/8000..a=rtpmap:101 telephon e-event/8000..a=fmtp:101 0-15..a=direction:passive..m=video 0 RTP/ AVP 31..c=IN IP4 193.22.119.34..a=direction:passive..
U 193.22.119.20:5060 -> 193.22.119.197:5060 BYE sip:193.22.119.197:5060;transport=udp SIP/2.0..CSeq: 1 BYE..Via: SIP/2.0/UDP 193.22.119.20;branch=z9hG4bK220c.ef532856.0..Via: SIP/2.0/UDP 193.22.119.20;branch= z9hG4bK220c.df532856.0..Via: SIP/2.0/UDP 193.22.119.78:5005;branch=z9hG4bKba4d4ede-4ed1-db11-8547- c725fe65d50d;rport=5005..From: sip:3400000012@voztele.com;tag=4eaa 8ed5-4ed1-db11-8547-c725fe65d50d..Call-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip: 3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..Con tact: <sip:gines@193.22.119.78:5005;transport=udp>..Content- Length: 0..Max-Forwards: 11....
U 193.22.119.197:5060 -> 193.22.119.20:5060 BYE sip:99920010034647460197@193.22.119.34:5060 SIP/2.0..Via: SIP/ 2.0/UDP 193.22.119.197;branch=z9hG4bK36f5.632d3c94.0..To: sip: 647460197@voztele.com;tag=gj-2k5-45f 58af2-00007916-00000dccR99ff1e6c.b..From: sip: 3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..CSeq: 3 BYE..Call-ID: C51B01C56457BE9C94060359F25C8A18@19 3.22.119.197..Route: <sip: 193.22.119.20;lr=on;ftag=EA0613171D364A5788BBA175AF8C4F4C>,.. <sip:193.22.119.10;lr=on>..Content-Length: 0..Max-Forwards: 70..Contac t: <sip:193.22.119.197:5060;transport=udp>....
U 193.22.119.197:5060 -> 193.22.119.20:5060 SIP/2.0 200 OK..CSeq: 1 BYE..Via: SIP/2.0/UDP 193.22.119.20;branch=z9hG4bK220c.ef532856.0..Via: SIP/2.0/UDP 193.22.119.20;branch=z9hG4bK220c.df532856.0..Via: SIP/2. 0/UDP 193.22.119.78:5005;branch=z9hG4bKba4d4ede-4ed1-db11-8547- c725fe65d50d;rport=5005..From: sip: 3400000012@voztele.com;tag=4eaa8ed5-4ed1-db11-8547-c725fe65d50d..C all-ID: 0581FBA55B7BD15BEDE2253EC472AAF7@193.22.119.197..To: sip: 3400000012@voztele.com;tag=C2ED946769B0C8CC8D3D3170805C1E11..Max- Forwards: 11..Content-Length: 0..W arning: 392 193.22.119.197:5060 "Noisy feedback tells: pid=28352 req_src_ip=193.22.119.20 req_src_port=5060 in_uri=sip: 193.22.119.197:5060;transport=udp out_uri=si p:193.22.119.197:5060;transport=udp via_cnt==4147"....
U 193.22.119.20:5060 -> 193.22.119.197:5060 SIP/2.0 200 OK..Via: SIP/2.0/UDP 193.22.119.197;branch=z9hG4bK36f5.632d3c94.0..From: sip: 3400000012@voztele.com;tag=EA0613171D364A5788BBA175AF8C4F4C..To: sip:647460
197@voztele.com;tag=gj-2k5-45f58af2-00007916-00000dccR99ff1e6c.b..Date : Thu, 15 Mar 2007 10:37:40 GMT..Call-ID: C51B01C56457BE9C94060359F25C8A18@193.22.119.197..Ser ver: Cisco-SIPGateway/IOS-12.x..Content-Length: 0..CSeq: 3 BYE.... _______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch- users http://www.freeswitch.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, is already there ... regards Helmut Brian West schrieb:
Please attach it to the bug report in jira!
/b
On Mar 15, 2007, at 7:26 AM, Helmut Kuper wrote:
Hi,
please find attached a working 3pcc sip flow trace
regards helmut
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF+Xlu4tZeNddg3dwRAsI2AKCs5a2KZftobnKlbFq2DjyVCIsdygCcChXQ jmacrzmRX1LKip4tjma13WM= =i1/q -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I`ve set up now a VoIP environment, with openser as central sip router, wesip as 3pcc application, 2nd openser as presence and messenger stroage and freeswitch as PSTN/mobile gateway. 3pcc is working in general as long as caller (that one which gets an INVITE without SDP) is NOT behind freeswitch. As soon as freeswitch gets that special INVITE freeswitch isn't able to handle it. I hits the dialplan, but then I get a "Temporarily unavailable" before that message I found some NUA errors, dunno what that means. If u r interested in supporting 3pcc and searching for a tester ... ask me :) regards helmut -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGFSNx4tZeNddg3dwRAtVQAKCBICJWFQXRThjlZHk7zWGPpACqKgCgjEPh hGPriUHoebezgS4cpehPKdo= =KiBR -----END PGP SIGNATURE-----
This is awesome.. I would like to offer this for NO CHARGE and for anyone to use in http://TagR.Mobi Can you please share your dial plan? Thanks in advance, -E
participants (4)
-
Anthony Minessale
-
Brian West
-
EdPimentl
-
Helmut Kuper