December 10, 2017, 04:28:12 pm *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: ObiApp with Jitsi  (Read 60038 times)
Officespaced
Newbie
*
Posts: 4


« on: October 09, 2012, 06:36:18 am »

Has anyone setup Jitsi with ObiApp successfully? I've had issues with X-Lite locking up so I've moved on.  I've been successfully using NCH Express Talk for a bit, but then I found Jitsi and for me the feature set works better.  I find I can make outgoing calls just fine, but the Jitsi client does not recognize inbound calls.  The Jitsi client just doesn't ring. 

The ObiApp, is receiving the inbound ring in the Status tab, but not the Jitsi client.  Not sure where I could have gone wrong as the setup for Jitsi and Express Talk should be about the same.
Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2322



« Reply #1 on: October 09, 2012, 08:20:32 am »

Works for me. Here is how I configured Jitsi:
Registrar: 127.0.0.1
Port: use the same SIP port you used in the OBiAPP
Authorization name:  290xxxxxx (Replace with your own number)


Uncheck configure proxy automatically (Must be configured manually)
Proxy: 127.0.0.1
Port: Same as above
Preferred transport: UDP
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
Officespaced
Newbie
*
Posts: 4


« Reply #2 on: October 12, 2012, 01:54:38 pm »

Thanks for the insight.  I configured my Jitsi the same way, but still No Joy.  Outgoing calls work great, but incoming calls just don't ring in Jitsi.  Oh well, guess it's back to Express Talk  Sad
Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2322



« Reply #3 on: October 12, 2012, 02:01:52 pm »

Officespaced,

One way calls are usually a result of NAT issues. Try port forwarding the RTP ports to your computer. It might work.
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
Officespaced
Newbie
*
Posts: 4


« Reply #4 on: October 20, 2012, 06:53:34 am »

I don't think that's the issue, as it works fine with X-Lite and Express Talk. The local  ObiTalk app itself is getting the ring signal, I can see that in the Status tab, it's just not passing it to Jitsi or Jitsi's not listening on the right port.  I'm sure it's a config issue or bad Jitsi build.
Logged
Smee
Jr. Member
**
Posts: 51



« Reply #5 on: November 20, 2013, 09:54:51 am »

I don't think that's the issue, as it works fine with X-Lite and Express Talk. The local  ObiTalk app itself is getting the ring signal, I can see that in the Status tab, it's just not passing it to Jitsi or Jitsi's not listening on the right port.  I'm sure it's a config issue or bad Jitsi build.

I know this is an old thread, but did you ever figure this out?  I have the same symptoms.  Xlite works without issue, but Jitsi simply won't ring on an incoming call even though I can see that ObiApp is passing the ring.

Smee

Update: Rats, I hate following up my own posts.  There is a bug somewhere, I just don't know if it's Jitsi being too strict or if ObiApp is not properly formatting the messages.  If anyone can chime in on what I see, this is the error I am seeing in the Jitsi logs:

12:13:52.718 WARNING: [2649] impl.protocol.sip.SipLogger.logException().85 Exception in the JAIN-SIP stack: From: <sip:3055551212@>;tag=SP133dc0b5e71053c52
: Missing host name
12:13:52.718 INFO: [2649] impl.protocol.sip.SipLogger.logException().87 JAIN-SIP exception stack trace is
java.text.ParseException: From: <sip:3055551212@>;tag=SP133dc0b5e71053c52
: Missing host name
   at gov.nist.core.HostNameParser.host(HostNameParser.java:193)
   at gov.nist.core.HostNameParser.hostPort(HostNameParser.java:266)
   at gov.nist.javax.sip.parser.URLParser.sipURL(URLParser.java:644)
   at gov.nist.javax.sip.parser.URLParser.uriReference(URLParser.java:347)
   at gov.nist.javax.sip.parser.AddressParser.nameAddr(AddressParser.java:58)
   at gov.nist.javax.sip.parser.AddressParser.address(AddressParser.java:112)
   at gov.nist.javax.sip.parser.AddressParametersParser.parse(AddressParametersParser.java:55)
   at gov.nist.javax.sip.parser.FromParser.parse(FromParser.java:59)
   at gov.nist.javax.sip.parser.StringMsgParser.processHeader(StringMsgParser.java:280)
   at gov.nist.javax.sip.parser.StringMsgParser.parseSIPMessage(StringMsgParser.java:170)
   at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:337)
   at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:297)
   at java.lang.Thread.run(Unknown Source)
12:13:52.718 SEVERE: [2649] impl.protocol.sip.SipLogger.logError().122 Error from the JAIN-SIP stack: BAD MESSAGE!
12:13:52.718 SEVERE: [2649] impl.protocol.sip.SipLogger.logError().122 Error from the JAIN-SIP stack: INVITE sip:29000XXXX@127.0.0.1:27383 SIP/2.0
Call-ID: 0f9d617d@172.16.0.95
Content-Length: 256
Cseq: 8001 INVITE
From: <sip:3055551212@>;tag=SP133dc0b5e71053c52
Max-Forwards: 70
To: <sip:290XXXX@127.0.0.1>
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-48316ec8;rport
Contact: "OBiAPP" <sip:unknown@127.0.0.1:5060>
Supported: replaces
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER
Content-Type: application/sdp

v=0
o=- 34720747 1 IN IP4 172.16.0.95
s=-
c=IN IP4 172.16.0.95
t=0 0
m=audio 36018 RTP/AVP 0 8 101 104
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=rtpmap:104 G726-32/8000
a=fmtp:101 0-15
a=sendrecv
a=ptime:20

« Last Edit: November 20, 2013, 10:08:00 am by Smee » Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2322



« Reply #6 on: November 20, 2013, 10:43:15 am »

Contact: "OBiAPP" <sip:unknown@127.0.0.1:5060>

This looks unusual. Can you compare it with another softphone and spot any difference.
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
Smee
Jr. Member
**
Posts: 51



« Reply #7 on: November 26, 2013, 03:25:23 pm »

Contact: "OBiAPP" <sip:unknown@127.0.0.1:5060>

This looks unusual. Can you compare it with another softphone and spot any difference.

I can't find an option in X-Lite to perform a log capture like I can with Jitsi.  Any recommendations?

Smee
Logged
QBZappy
Hero Member & Beta Tester
*****
Posts: 2322



« Reply #8 on: November 26, 2013, 03:39:04 pm »

@Smee

This has a nice debug function as well.

http://www.phonerlite.de/index_en.htm
Logged

Owner of the 1st OBi110/100 units in service in Canada & South America. 1st OBi202 on my street. 1st OBi1032 in Montreal.
HH235
Jr. Member
**
Posts: 43


« Reply #9 on: February 16, 2014, 01:11:24 am »

How do you know which port to use.  I don't remember selecting a port using the obi app.
When i call the soft phone from my obi 100 i just get a busy signal.  dialing from teh Jitsi app just goes to nothing.
Logged
HH235
Jr. Member
**
Posts: 43


« Reply #10 on: February 16, 2014, 01:34:44 am »

OK.  I found the port. 
For user id do you put in the same info as for the Obi app and password?
Logged
HH235
Jr. Member
**
Posts: 43


« Reply #11 on: February 17, 2014, 10:18:15 am »

Jitsi still not working.  Very annoyed.  I've tried XTalk, X3C, and now Jitsi with no success.  ridiculous.
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 3190


« Reply #12 on: February 17, 2014, 02:02:22 pm »

I successfully used Phonerlite and 3CX.

Server is 127.0.0.1
Use the OBitalk app number (290xxxxxx) as the Userid.
You don't need a password.

Does the softphone show registered? 3CX will show "On Hook".

What method are you using to call the Obion App from your OBi?

Please post the following parm setting in your OBi:
Voice Services -> ObiTalk Service -> InboundCallRoute.

Is the softphone running on the same computer as the Obion App?
« Last Edit: February 17, 2014, 02:44:41 pm by azrobert » Logged
HH235
Jr. Member
**
Posts: 43


« Reply #13 on: February 18, 2014, 07:00:52 am »

thanks for the reply.  I will have to get them tomorrow.  Work today/tonight.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC