[OPEN] pSIP - "Pjsua application starting" continually shows

[ecomoney]

On opening pSIP, the application window displays "Pjsua application starting"...and doesnt actually diappear (tested for ten minutes).

Im not familiar with pSIP, does this mean an important sub-process is not initializing?

Screenie Attached

[gposil]

This is what you get running from console...

# psip
# ./psip2: line 17: /tmp/psip/status-message: No such file or directory
cat: /tmp/psip/buddy-tree: No such file or directory
cat: /tmp/psip/status-message: No such file or directory
ANSWER=""
ANSWER_MENU=""
BUDDYLIST=""
BUDDYLIST_ALL=""
CALL=""
CALL_MENU=""
CHAT=""
CONFERENCE_PRESET=""
GIZMO_VOICEMAIL_PRESET=""
HANGUP_MENU=""
NEWS_PRESET=""
EXIT="exit by menu"
rm: cannot remove `/tmp/psip/buddy-list': No such file or directory
/usr/local/psip/func_startpjsua: line 43: 16014 Broken pipe tail -f $PJSIGNAL >$PJTMP/pjsua-input-pipe
killing pjsua process 15990
killing pjsua process 16016
killing pjsua process 16017
killing pjsua process 17026
/usr/local/psip/func_shutdownpjsua: line 16: kill: (17026) - No such process
I am 16477, I failed to kill pjsua process: 17026

I will investigate more....

[ecomoney]

Apologies for not posting that information myself. Whodo, you are a sip user (according to your sig)...perhaps you will test.

[dogle]

This is not a 4.2.1-specific issue, AFAIK it was always there.

Try configuring to include a buddy or two and it should be happy and proceed past the "starting" message.

I'm glad to see interest in Psip reawakening because I think it stands to be a valuable part of Puppy when we get used to it. I would agree though that the apparently stalled starting message can be very baffling for newcomers ... and oldcomers ... (it was for me) so perhaps, at least, a few words of warning added to Grant's helpful guide would be beneficial.

http://rbcfaqs.co.cc/PSIP/

[ecomoney]

And SIP works even though this subprocess is not starting?