Jitsi Desktop can't dial out

#1

Hello,

I’m using my own SIP account. Communication works from Zoiper (in any direction) but using jitsi-desktop i’m not able to call a phone.

(I already created a post about Jigasi and sip communication, but I realized Jitsi-Desktop is not able to call phone numbers )

Do you know where does it come from ?

Thank you.

#2

It stays forever in initializing? Check desktop.jitsi.org faq. Common problem with too big udp packets

#3

Changing audio codecs didn’t resolve problem, unfortunately :confused:

#4

It is not just changing audio codecs, just remove everything you don’t need.
Do you see any errors in the logs?

#5

It is what I did. Normally I use " G.711" but missing in jitsi-desktop. So I just removed and tested audio codecs one by one.
I didn’t find logs inside jitsi-desktop app.

#6

Check the faq where to locate logs.

#7

Yes, I have already gone inside %appdata%/Jitsi/

But there is no logs folder inside.

#8

https://desktop.jitsi.org/Documentation/FAQ#logs

#9

Seems to be the same problem here : [jitsi-dev] VOIP Problems

2019-05-16 09:30:14.231 INFOS: [583] impl.protocol.sip.OperationSetBasicTelephonySipImpl.createOutgoingCall().195 Creating outgoing call to sip:numberphone@ip
2019-05-16 09:30:14.246 INFOS: [583] impl.protocol.sip.ProxyRouter.getRouterFor().154 Returning default SIP router, P2P/loose routing
2019-05-16 09:30:14.356 AVERTISSEMENT: [583] impl.protocol.sip.CallPeerMediaHandlerSipImpl.createMediaDescriptions().224 No active device for video was found!
2019-05-16 09:30:14.387 INFOS: [585] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /ip:5060
2019-05-16 09:30:14.402 INFOS: [586] impl.protocol.sip.SipLogger.logInfo().196 Info from the JAIN-SIP stack: Setting SIPMessage peerPacketSource to: /ip:5060
2019-05-16 09:30:14.402 GRAVE: [586] impl.protocol.sip.OperationSetBasicTelephonySipImpl.processResponse().634 Received error: 403 Forbidden
#10

Any idea ?

#11

No idea why the server forbids you dial that numberphone. You should either check on the server or of this is a provider sometimes the reason is in the message that they sent back (if it is not visible in the UI), then you need to find the log folder and open the pcap file using wireshark and find that 403 message and see its headers will something ring a bell what is the problem.

#12

Okay, I’m going to check.