You are not logged in.

#1 2018-12-13 09:14:16

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 1,992
Website

[solved] Debugging SIP connection

I want to use a soft phone on my Arch Linux workstation.
So far I've been trying ekiga since it integrates well with my Gnome IDE.
Unfortunately it does not connect with the credentials from my provider.
The console does not show any interesting debug outut:

$ LANG=C ekiga -d

(ekiga:30747): GLib-CRITICAL **: 10:09:05.463: Source ID 606 was not found when attempting to remove it

The GUI fails with the message

ekiga wrote:

Could not register (Remote party host is offline)

which is not very helpful.
How can I debug the SIP connection - preferably using the console?
The Wiki page only suggests GUI clients.
Since you might be suggesting it: My TSP unfortunately does not provide support for soft phones apart from issuing the login details.

Last edited by schard (2018-12-13 15:27:51)


macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

Offline

#2 2018-12-13 09:24:31

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,764

Re: [solved] Debugging SIP connection

Moving to Networking

Offline

#3 2018-12-13 10:22:38

jsoy9pQbYVNu5nfU
Member
Registered: 2013-04-19
Posts: 108

Re: [solved] Debugging SIP connection

tcpdump -vvv -i $iface will prettyprint SIP packages for you. If you can make sense of a SIP conversation, this will tell you everything you need, including SDP if any. SIP packets are usually not encrypted in most SIP systems so this should work. When using SIPS, sipcmd as a complete client may be an option. Naturally, wireshark/tshark can also help.

Last edited by jsoy9pQbYVNu5nfU (2018-12-13 10:27:06)

Offline

#4 2018-12-13 15:27:39

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 1,992
Website

Re: [solved] Debugging SIP connection

@2ion Thank you.
I used tcpdump in combitation with ekiga -d 4 and pjsua to find the problem.
With pjsua I can reveice but not make calls, with ekiga I can make but not receive calls.
In debug mode, ekiga prints a lot of "400 BadRequest" error messages presumably coming from the SIP server of my TSP.
I tried some other phone clients and yate is the only one that's working perfectly fine.
So I suspect that ekiga is doing something wrong regarding the SIP protocol, which I am not willing to investigate further.
Solution → Use yate.


macro_rules! yolo { { $($tokens:tt)* } => { unsafe { $($tokens)* } }; }

Offline

Board footer

Powered by FluxBB