By the way, it appears that the "**<extension>" ringing call pickup feature is intermittent. Sometimes it works, sometimes not. I posted two traces of the following scenario: 1) 1059 calls 5381 2) 5381 rings 3) 5402 dials "**5381" In the bad case (http://pastebin.freeswitch.org/12325), all calls disconnect following above scenario. In the good case (http://pastebin.freeswitch.org/12326), 5402 connects to 1059. Best Regards, Jerry -----Original Message----- From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Thursday, March 04, 2010 12:20 PM To: 'freeswitch-users@lists.freeswitch.org' Subject: Dialing **<extension> I used to be able to dial "**<extension>" to pickup a ringing call (v. 1.0.5pre9) from a different extension. Since I upgraded to 1.0.5-20100223, this no longer works the same. Is this feature still available under some other star-code? Best Regards, Jerry
On Thu, Mar 4, 2010 at 2:14 PM, Jerry Richards <jerry.richards@teotech.com>wrote:
By the way, it appears that the "**<extension>" ringing call pickup feature is intermittent. Sometimes it works, sometimes not. I posted two traces of the following scenario:
1) 1059 calls 5381 2) 5381 rings 3) 5402 dials "**5381"
In the bad case (http://pastebin.freeswitch.org/12325), all calls disconnect following above scenario. In the good case (http://pastebin.freeswitch.org/12326), 5402 connects to 1059.
Best Regards, Jerry
I'd suggest turning off the sofia debug stuff cuz that's just line noise unless you know all that stuff. You need to compare the two traces and look for differences. I'd start by looking at only the fs console output of each call and see if there's anything different between the two. See if there's a point where they diverge and work your way back from there. Look at the corresponding SIP dialogs and see if there are any clues as well. You may also want to capture the SIP traffic with tcpdump and analyze it in Wireshark which is easier on the eyes than having it buried in with the sofia and console logs. FWIW, I just updated to latest and I can't make this feature *NOT* work. I'm on 32-bit CentOS using Polycom 550 and Snom 320 phones. -MC
What I see in the log where they first differ is just after FS sends the CANCEL to the original ringing phone. FS logs a cause: PICKED_OFF when it didn't work. Do you know what PICKED_OFF means? In the good case, FS logs: tport_pend(0x88348e8): pending 0x8942cc0 for udp/192.168.72.141:5060 (already 1) 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: ORIGINATOR_CANCEL 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1161 Session 177 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities In the bad case, FS logs: tport_pend(0x88348e8): pending 0xb6dd6468 for udp/192.168.72.141:5060 (already 1) 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:333 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_HANGUP -> CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:314 (sofia/internal/sip:5381@192.168.72.58:5060) Running State Change CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: PICKED_OFF 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1161 Session 199 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal <mailto:sofia/internal/1059@192.168.72.141:5060> sofia/internal/1059@192.168.72.141:5060 [BREAK] 2010-03-04 12:33:45.001563 [NOTICE] switch_ivr_bridge.c:740 Hangup <mailto:sofia/internal/5402@192.168.72.141:5060> sofia/internal/5402@192.168.72.141:5060 [CS_SOFT_EXECUTE] [ORIGINATOR_CANCEL] Best Regards, Jerry _____ From: Michael Collins [mailto:msc@freeswitch.org] Sent: Thursday, March 04, 2010 2:59 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Dialing **<extension> On Thu, Mar 4, 2010 at 2:14 PM, Jerry Richards <jerry.richards@teotech.com> wrote: By the way, it appears that the "**<extension>" ringing call pickup feature is intermittent. Sometimes it works, sometimes not. I posted two traces of the following scenario: 1) 1059 calls 5381 2) 5381 rings 3) 5402 dials "**5381" In the bad case (http://pastebin.freeswitch.org/12325), all calls disconnect following above scenario. In the good case (http://pastebin.freeswitch.org/12326), 5402 connects to 1059. Best Regards, Jerry I'd suggest turning off the sofia debug stuff cuz that's just line noise unless you know all that stuff. You need to compare the two traces and look for differences. I'd start by looking at only the fs console output of each call and see if there's anything different between the two. See if there's a point where they diverge and work your way back from there. Look at the corresponding SIP dialogs and see if there are any clues as well. You may also want to capture the SIP traffic with tcpdump and analyze it in Wireshark which is easier on the eyes than having it buried in with the sofia and console logs. FWIW, I just updated to latest and I can't make this feature *NOT* work. I'm on 32-bit CentOS using Polycom 550 and Snom 320 phones. -MC
Did you totally ignore my instructions? Do you want help or not? On Thu, Mar 4, 2010 at 6:01 PM, Jerry Richards <jerry.richards@teotech.com>wrote:
What I see in the log where they first differ is just after FS sends the CANCEL to the original ringing phone. FS logs a cause: PICKED_OFF when it didn't work. Do you know what PICKED_OFF means?
In the good case, FS logs:
tport_pend(0x88348e8): pending 0x8942cc0 for udp/192.168.72.141:5060(already 1) 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: ORIGINATOR_CANCEL 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1161 Session 177 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities In the bad case, FS logs:
tport_pend(0x88348e8): pending 0xb6dd6468 for udp/192.168.72.141:5060(already 1) 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:333 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_HANGUP -> CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:314 (sofia/internal/sip:5381@192.168.72.58:5060) Running State Change CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: PICKED_OFF 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1161 Session 199 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/1059@192.168.72.141:5060 [BREAK] 2010-03-04 12:33:45.001563 [NOTICE] switch_ivr_bridge.c:740 Hangup sofia/internal/5402@192.168.72.141:5060 [CS_SOFT_EXECUTE] [ORIGINATOR_CANCEL] Best Regards, Jerry
------------------------------ *From:* Michael Collins [mailto:msc@freeswitch.org] *Sent:* Thursday, March 04, 2010 2:59 PM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] Dialing **<extension>
On Thu, Mar 4, 2010 at 2:14 PM, Jerry Richards <jerry.richards@teotech.com
wrote:
By the way, it appears that the "**<extension>" ringing call pickup feature is intermittent. Sometimes it works, sometimes not. I posted two traces of the following scenario:
1) 1059 calls 5381 2) 5381 rings 3) 5402 dials "**5381"
In the bad case (http://pastebin.freeswitch.org/12325), all calls disconnect following above scenario. In the good case (http://pastebin.freeswitch.org/12326), 5402 connects to 1059.
Best Regards, Jerry
I'd suggest turning off the sofia debug stuff cuz that's just line noise unless you know all that stuff. You need to compare the two traces and look for differences. I'd start by looking at only the fs console output of each call and see if there's anything different between the two. See if there's a point where they diverge and work your way back from there. Look at the corresponding SIP dialogs and see if there are any clues as well. You may also want to capture the SIP traffic with tcpdump and analyze it in Wireshark which is easier on the eyes than having it buried in with the sofia and console logs.
FWIW, I just updated to latest and I can't make this feature *NOT* work. I'm on 32-bit CentOS using Polycom 550 and Snom 320 phones.
-MC
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Sorry, I just looked for diffs in the logs I had. Thank you for all of your good advice. I do appreciate it! I did try a snom 360 phone (but not a polycomm) and it behaved the same, however, I did find that one of my servers (with a 2-day newer FS version and different config) does not have this problem. So I will isolate the issue between my config or just upgrade to the newer FS. Thank You and Best Regards, Jerry _____ From: Anthony Minessale [mailto:anthony.minessale@gmail.com] Sent: Thursday, March 04, 2010 4:14 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Dialing **<extension> Did you totally ignore my instructions? Do you want help or not? On Thu, Mar 4, 2010 at 6:01 PM, Jerry Richards <jerry.richards@teotech.com> wrote: What I see in the log where they first differ is just after FS sends the CANCEL to the original ringing phone. FS logs a cause: PICKED_OFF when it didn't work. Do you know what PICKED_OFF means? In the good case, FS logs: tport_pend(0x88348e8): pending 0x8942cc0 for udp/192.168.72.141:5060 (already 1) 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: ORIGINATOR_CANCEL 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1161 Session 177 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities In the bad case, FS logs: tport_pend(0x88348e8): pending 0xb6dd6468 for udp/192.168.72.141:5060 (already 1) 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:333 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_HANGUP -> CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:314 (sofia/internal/sip:5381@192.168.72.58:5060) Running State Change CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: PICKED_OFF 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1161 Session 199 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal <mailto:sofia/internal/1059@192.168.72.141:5060> sofia/internal/1059@192.168.72.141:5060 [BREAK] 2010-03-04 12:33:45.001563 [NOTICE] switch_ivr_bridge.c:740 Hangup <mailto:sofia/internal/5402@192.168.72.141:5060> sofia/internal/5402@192.168.72.141:5060 [CS_SOFT_EXECUTE] [ORIGINATOR_CANCEL] Best Regards, Jerry _____ From: Michael Collins [mailto:msc@freeswitch.org] Sent: Thursday, March 04, 2010 2:59 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] Dialing **<extension> On Thu, Mar 4, 2010 at 2:14 PM, Jerry Richards <jerry.richards@teotech.com> wrote: By the way, it appears that the "**<extension>" ringing call pickup feature is intermittent. Sometimes it works, sometimes not. I posted two traces of the following scenario: 1) 1059 calls 5381 2) 5381 rings 3) 5402 dials "**5381" In the bad case (http://pastebin.freeswitch.org/12325), all calls disconnect following above scenario. In the good case (http://pastebin.freeswitch.org/12326), 5402 connects to 1059. Best Regards, Jerry I'd suggest turning off the sofia debug stuff cuz that's just line noise unless you know all that stuff. You need to compare the two traces and look for differences. I'd start by looking at only the fs console output of each call and see if there's anything different between the two. See if there's a point where they diverge and work your way back from there. Look at the corresponding SIP dialogs and see if there are any clues as well. You may also want to capture the SIP traffic with tcpdump and analyze it in Wireshark which is easier on the eyes than having it buried in with the sofia and console logs. FWIW, I just updated to latest and I can't make this feature *NOT* work. I'm on 32-bit CentOS using Polycom 550 and Snom 320 phones. -MC _______________________________________________ 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 -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com <mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <mailto:sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org <mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
What I am trying to tell you going forward is to open issues on jira not the mailing list I have to say it 4-10 times a day to people. We cant follow issues over email, we get literally 100+ emails a day some days. It's for your own good. We need proper workflow.... On Fri, Mar 5, 2010 at 4:57 PM, Jerry Richards <jerry.richards@teotech.com>wrote:
Sorry, I just looked for diffs in the logs I had. Thank you for all of your good advice. I do appreciate it! I did try a snom 360 phone (but not a polycomm) and it behaved the same, however, I did find that one of my servers (with a 2-day newer FS version and different config) does not have this problem. So I will isolate the issue between my config or just upgrade to the newer FS.
Thank You and Best Regards, Jerry
------------------------------ *From:* Anthony Minessale [mailto:anthony.minessale@gmail.com] *Sent:* Thursday, March 04, 2010 4:14 PM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] Dialing **<extension>
Did you totally ignore my instructions? Do you want help or not?
On Thu, Mar 4, 2010 at 6:01 PM, Jerry Richards <jerry.richards@teotech.com
wrote:
What I see in the log where they first differ is just after FS sends the CANCEL to the original ringing phone. FS logs a cause: PICKED_OFF when it didn't work. Do you know what PICKED_OFF means?
In the good case, FS logs:
tport_pend(0x88348e8): pending 0x8942cc0 for udp/192.168.72.141:5060(already 1) 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: ORIGINATOR_CANCEL 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:13:04.772196 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:13:04.772196 [DEBUG] switch_core_session.c:1161 Session 177 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities In the bad case, FS logs:
tport_pend(0x88348e8): pending 0xb6dd6468 for udp/192.168.72.141:5060(already 1) 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:333 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_HANGUP -> CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:314 (sofia/internal/sip:5381@192.168.72.58:5060) Running State Change CS_REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:53 sofia/internal/sip:5381@192.168.72.58:5060 Standard REPORTING, cause: PICKED_OFF 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/sip:5381@192.168.72.58:5060) State REPORTING going to sleep 2010-03-04 12:33:45.001563 [DEBUG] switch_core_state_machine.c:327 (sofia/internal/sip:5381@192.168.72.58:5060) State Change CS_REPORTING -> CS_DESTROY 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/sip:5381@192.168.72.58:5060 [BREAK] 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1161 Session 199 (sofia/internal/sip:5381@192.168.72.58:5060) Locked, Waiting on external entities 2010-03-04 12:33:45.001563 [DEBUG] switch_core_session.c:1019 Send signal sofia/internal/1059@192.168.72.141:5060 [BREAK] 2010-03-04 12:33:45.001563 [NOTICE] switch_ivr_bridge.c:740 Hangup sofia/internal/5402@192.168.72.141:5060 [CS_SOFT_EXECUTE] [ORIGINATOR_CANCEL] Best Regards, Jerry
------------------------------ *From:* Michael Collins [mailto:msc@freeswitch.org] *Sent:* Thursday, March 04, 2010 2:59 PM
*To:* freeswitch-users@lists.freeswitch.org *Subject:* Re: [Freeswitch-users] Dialing **<extension>
On Thu, Mar 4, 2010 at 2:14 PM, Jerry Richards < jerry.richards@teotech.com> wrote:
By the way, it appears that the "**<extension>" ringing call pickup feature is intermittent. Sometimes it works, sometimes not. I posted two traces of the following scenario:
1) 1059 calls 5381 2) 5381 rings 3) 5402 dials "**5381"
In the bad case (http://pastebin.freeswitch.org/12325), all calls disconnect following above scenario. In the good case (http://pastebin.freeswitch.org/12326), 5402 connects to 1059.
Best Regards, Jerry
I'd suggest turning off the sofia debug stuff cuz that's just line noise unless you know all that stuff. You need to compare the two traces and look for differences. I'd start by looking at only the fs console output of each call and see if there's anything different between the two. See if there's a point where they diverge and work your way back from there. Look at the corresponding SIP dialogs and see if there are any clues as well. You may also want to capture the SIP traffic with tcpdump and analyze it in Wireshark which is easier on the eyes than having it buried in with the sofia and console logs.
FWIW, I just updated to latest and I can't make this feature *NOT* work. I'm on 32-bit CentOS using Polycom 550 and Snom 320 phones.
-MC
_______________________________________________ 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
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
1) You are supposed to report bugs to jira http://jira.freeswitch.org 2) You are not using svn trunk so the line numbers don't match for debugging. 3) #2 is a prerequisite for #1 On Thu, Mar 4, 2010 at 4:14 PM, Jerry Richards <jerry.richards@teotech.com>wrote:
By the way, it appears that the "**<extension>" ringing call pickup feature is intermittent. Sometimes it works, sometimes not. I posted two traces of the following scenario:
1) 1059 calls 5381 2) 5381 rings 3) 5402 dials "**5381"
In the bad case (http://pastebin.freeswitch.org/12325), all calls disconnect following above scenario. In the good case (http://pastebin.freeswitch.org/12326), 5402 connects to 1059.
Best Regards, Jerry
-----Original Message----- From: Jerry Richards [mailto:jerry.richards@teotech.com] Sent: Thursday, March 04, 2010 12:20 PM To: 'freeswitch-users@lists.freeswitch.org' Subject: Dialing **<extension>
I used to be able to dial "**<extension>" to pickup a ringing call (v. 1.0.5pre9) from a different extension. Since I upgraded to 1.0.5-20100223, this no longer works the same.
Is this feature still available under some other star-code?
Best Regards, Jerry
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
participants (3)
-
Anthony Minessale
-
Jerry Richards
-
Michael Collins