Hi,

Jira created http://track.sipfoundry.org/browse/XX-10213 . I attached the
patch to this mail. Let me know if something more is necessary.

Regards
Luciano

2012/6/20 George Niculae <[email protected]>

> On Wed, Jun 20, 2012 at 6:44 PM, Luciano Berardi
> <[email protected]> wrote:
> > Hi,
> >
> > sorry, maybe I didn't completely explained my tests.
> > After you suggestion to update my system version, I did it and today I
> was
> > running on a clean updated version without any change to the code.
> >
> > Starting from this point I have done a deeper analysis of the call park
> > feature to allow transfer back to parker. I found that, using a different
> > log level than DEBUG, a segmentation fault happens. Indeed the sipXpark
> > process crashes.
> >
> > from core dumps:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 0x7fffcbfff700 (LWP 3741)]
> > CpCall::handleMessage (this=0x7fffbc006940, eventMessage=<value optimized
> > out>) at /home/admin/sipxecs/sipXcallLib/src/cp/CpCall.cpp:695
> > 695                                    OsStatus res =
> > dtmfEvent->signal((eventData & 0xfffffff0));
> >
> >
> > the "signal" method called on dtmfEvent needs a intptr_t parameter:
> >
> > OsStatus OsQueuedEvent::signal(const intptr_t eventData)
> >
> >
> >
> > So I partially applied the changes used in the
> > patch http://track.sipfoundry.org/browse/XX-10103 by only changing the
> type
> > of the "event" from int to intptr_t. Applying this changes everything
> works
> > fine.
> >
> > Hope this better explains what I did and what I was asking for.
> > It could be the case to apply this changes to main tree.
> >
>
> Ah, ok, now it's clear - thanks for explanations. Would you mind
> opening a JIRA for this?
>
> George
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>

Attachment: 0001-fix-for-call-park.patch
Description: Binary data

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to