I have to get more information for the case at Patton. It does not happen on sup trunks. It only happened after moving from 4.2 firmware to 5.x.
I am ordering another small truckload of gateways Monday from them. My suspicion is they (Patton) "fixed" a bug for one vendor that made this one occur. I've pointed this out to them and they have assigned it to the lab in Europe. If they say its the proxy/media server I have no hopes to see it fixed in 2012 as call park is "way down" on the priority list and is not scheduled yet. On Feb 24, 2012 7:25 PM, "Todd Hodgen" <[email protected]> wrote: > Hey Tony, Didn’t want to highjack Dave’s thread, so I have renamed it and > kept the past emails in it. You have gotten my interest here with your > last response – have you proven that the issue with parked calls not being > returned was related to the Patton Gateway? I’ve seen that issue, but had > not considered it related to the Gateway. Can you share any other details > on this? Inquiring minds want to know……**** > > ** ** > > I know it existed in 4.2.1, and there was a Jira report and fixed for > 4.4. I think it might still be happening in 4.4, have not gotten out to > test it though. But, if it is related to the Patton, that would change > things considerably.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Tony Graziano > *Sent:* Friday, February 24, 2012 3:52 PM > *To:* sipXecs developer discussions > *Subject:* Re: [sipx-dev] Issue picking up a parked call**** > > ** ** > > I have not had issues with retrieving a parked call, just having call park > auto return work with those gateways. I am mostly running the 6.x firmware > though.**** > > On Fri, Feb 24, 2012 at 6:39 PM, Dave Deutschman < > [email protected]> wrote:**** > > Tony, **** > > **** > > I do not have access to the device but in the INVITE it contains a header > of**** > > **** > > Server: Patton SN4940 1E24V …R5.T 2011-01-17 … SIP Stack/4.0.30.30**** > > **** > > However, I don’t think it is an issue with the gateway because I would > have thought that in the REFER from the park server to extension, the Refer > To: should have been the original Contact of the parked caller from the > Patton gateway, however it contains the contact for extension 202. That > does not seem correct to me.**** > > **** > > DD **** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Tony Graziano > *Sent:* Friday, February 24, 2012 3:15 PM > *To:* sipXecs developer discussions > *Subject:* Re: [sipx-dev] Issue picking up a parked call**** > > **** > > what version of patton firmware?**** > > On Fri, Feb 24, 2012 at 6:10 PM, Dave Deutschman < > [email protected]> wrote:**** > > We had a customer who reported a failed attempt to pick-up a parked call. > The call was inbound from a Patton gateway and was answered on extension > 202. That person parked the call on extension 220. When they attempted to > pick-up the parked call using *4220, the attempt ended in a fat busy.**** > > **** > > The attached file contains a trace of the call flow of the pickup attempt > of the call from park extension 220 by extension 202 who had parked the > call. The message sequence looks fine until the REFER is sent back to the > phone provisioned with extension 202. At frame 34, the Polycom phone > issues an INVITE with no SDP. I believe that is to signify that the park > server should stop MoH and prepare to transfer the call. However, what we > see is a series of INVITEs where sipXproxy is sending the INVITE to itself > and sipregistrar and ends up with the proxy issuing 482 Loop Detected and > 483 Too Many Hops.**** > > **** > > Could someone please tell me what is wrong with the pickup sequence or the > INVITE at frame 34 from the Polycom phone that would send the flow into a > “tail spin”?**** > > **** > > This is an intermittent issue as the vast majority of attempts to pick-up > a parked call works on this system.**** > > **** > > Sincerely, **** > > **** > > Dave Deutschman**** > > Managing Partner**** > > Innovational IP Solutions, LLC**** > > **** > > PO Box 983**** > > Bothell, WA 98041**** > > **** > > 206.965.9586 x 301 (o)**** > > 425.478.9642 (m)**** > > [email protected] (s)**** > > **** > > www.innovational.net**** > > **** > > "The information transmitted is intended only for the person or entity to > which it is addressed and may contain proprietary, confidential and/or > legally privileged material. Any review, retransmission, dissemination or > other use of, or taking of any action in reliance upon, this information by > persons or entities other than the intended recipient is prohibited. If you > received this in error, please contact the sender and delete the material > from all computers." **** > > **** > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/**** > > > > **** > > **** > > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager**** > > Telephone: 434.984.8430**** > > > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~**** > > LAN/Telephony/Security and Control Systems Helpdesk:**** > > Telephone: 434.984.8426**** > > sip: [email protected]**** > > **** > > Helpdesk Customers: http://myhelp.myitdepartment.net**** > > Blog: http://blog.myitdepartment.net**** > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2012.0.1913 / Virus Database: 2114/4829 - Release Date: 02/24/12* > *** > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/**** > > > > **** > > ** ** > > -- > ~~~~~~~~~~~~~~~~~~ > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.465.6833 > ~~~~~~~~~~~~~~~~~~ > Linked-In Profile: > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > Ask about our Internet Fax services! > ~~~~~~~~~~~~~~~~~~**** > > LAN/Telephony/Security and Control Systems Helpdesk:**** > > Telephone: 434.984.8426**** > > sip: [email protected]**** > > ** ** > > Helpdesk Customers: http://myhelp.myitdepartment.net**** > > Blog: http://blog.myitdepartment.net**** > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
