| Key: |
XCL-137
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Critical
|
| Assignee: |
Unassigned
|
| Reporter: |
shobhit shingla
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
sipXtapi
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
1.
sipXtapi.log (1.99 Mb)
|
|
Environment:
|
Windows
|
|
|
I am facing a major issue with sipXtapi.
My application carshes when i make a call using second instance of sipXtapi after uninitializing the first instance in the same process.
The process followed is;
After creating the first instance i have called sipXconfigSubscribe followed by sipXuninitailize,
I create second insatnce using sipXinitialize and now when i try to make a call using sipXcallcreate and sipXcallconnect my application crashes.
The sequence of calling the API's is as follows --
sipXinitialize
sipXlineadd
sipXConfigSubscribe
sipXconfigUnsubscribe
sipXlineremove
sipXUninitialize
sipXinitialize
sipXlineAdd
sipXcallcreate ---------------- crash here
and sometimes
sipXcallConnect ----------- crash here
|
|
Description
|
I am facing a major issue with sipXtapi.
My application carshes when i make a call using second instance of sipXtapi after uninitializing the first instance in the same process.
The process followed is;
After creating the first instance i have called sipXconfigSubscribe followed by sipXuninitailize,
I create second insatnce using sipXinitialize and now when i try to make a call using sipXcallcreate and sipXcallconnect my application crashes.
The sequence of calling the API's is as follows --
sipXinitialize
sipXlineadd
sipXConfigSubscribe
sipXconfigUnsubscribe
sipXlineremove
sipXUninitialize
sipXinitialize
sipXlineAdd
sipXcallcreate ---------------- crash here
and sometimes
sipXcallConnect ----------- crash here |
Show » |
|
CLONE -sipXcallcreate and sipXcaalconnect problem after calling sipXinitialize second time.
Thanks for your reply on
XCL-136but the issue still remainsBut i have found something new about this issue.
My Test Application does not crash in visual studio but crashes when i run it's executable from cmd prompt.
But in my application i i am first uninitializing the first instance of sipxtapi then creating a new instance in the same process. Second instance is created succesfully and sipxcallcreate is called through the same. As soon as sipxcallconnect is called the application crashes. Please refer the listed bug again and also refer the attached log and code for further analysyis.