Yealink T-22P with Obi110
ikonos:
Quote from: QBZappy on March 26, 2014, 11:50:52 am
Quote from: ikonos on March 26, 2014, 09:10:47 am
...I am starting to think one of the three SIP accounts on yealink has to be registered before I can setup the remaining ones to talk to Obi. I will give it a try soon.
In that case test your theory by setting up a free account wit sip2sip or some other free sip service.
https://mdns.sipthor.net/register_sip_account.phtml
I configured an Anveo account on the second line and it registered fine and even was able to make calls.
This is strange and I can't figure out what setting to use to get it to talk to Obi. May be because I am using Obi100 to test it and not Obi110, I might be doing something wrong. At this point I am primarily testing calling out from yealink though Obi100 (configured GV on SP1 or Anveo on SP2). I will worry about the incoming call later.
azrobert:
Your Yealink must be configured to dial out without registration to work with an OBi.
You can post a question at the Yealink forum here:
http://forum.yealink.com/forum/index.php
drgeoff:
Quote from: azrobert on March 26, 2014, 02:13:11 pm
Your Yealink must be configured to dial out without registration to work with an OBi.
You can post a question at the Yealink forum here:
http://forum.yealink.com/forum/index.php
Not applicable here in the context of OBi100/110 but "an OBi" is too general. A SIP phone can register to an OBi202.
ikonos:
Its strange. I reset the factory image on the Yealink and used default 5060 port on it as well as on the Obi, then it said Registration Failed but the call went through. If I use any port other than 5060 on the X_UserAgentPort (I think that's the correct name) on the Obi then the call is not going through. However I still have couple of issues.
1) When the number is being dialed, I dont here any ring from the otherside except on the diaplay that it is dialing or something like that.
2) When the other use picks up, I cant hear anything and they cant hear what I say. Is this a codec problem?
3) If I add {yealink_ip>(Mli):li},{ph} in the X_InboundCallRoute for Voice Service 1, the call goes out but if I add
{(Mtsc)>(<*1:>(Msp1)),(Mtsc)>(<**1:>(Msp1)):sp1},{(Mtsc)>(<*2:>(Msp2)),(Mtsc)>(<**2:>(Msp2)):sp2},{(Mtsc)>(<*8:>(Mli)),(Mtsc)>(<**8:>(Mli)):li},{(Mtsc)>**0:aa},{(Mtsc)>***:aa2},{(Mtsc)>(Mp2p):sp1},{(Mtsc)>(Mtg1):tg1},{(Mtsc)>0:ph},{(Mtsc):},{ph}
as recommended in the single stage dialing the call is not going through and dials the phone port. I have the yealink_ip added as tsc in the user defined settings.
Appreciate any suggestions.
Thanks
Ik.
azrobert:
Do you have audio when the Yealink rings the phone port on the OBi? I looked at the Yealink manual and it looks like it uses the same codecs as the OBi.
Add the following to the beginning of the current X_InboundCallRoute to be able to route calls out SP1 from the Yealink.
{yealink_ip>(1xxxxxxxxxx):sp1},
Using the Yealink, I assume you will want to access the remote OBi over the Obitalk network.
I do not code like RonR and I have no desire to spend any time on figuring out what this code is doing, so I will not attempt to fix it.
After you get the audio problem fixed and you still haven't fixed the routing problem, I can show you how I would configure the OBi's.
Navigation
[0] Message Index
[#] Next page
[*] Previous page