Need help bridging two OBIs on internal network
Taoman:
Must be doing something wrong. I've tried both with an SPx already configured (X_DiscoverPublicAddress unchecked) and also with just a dummy trunk. Incoming calls never make it to the OBi200.
In call history on OBi110 the calls come in fine and are being forked to:
taoman@192.168.1.200:5063
I am currently using SP4 on OBi200 as dummy SIP trunk. Nothing shows up in call history on OBi200.
hwittenb:
If the phone doesn't ring and there is no call history, then the OBi200 is either rejecting the incoming SIP INVITE or the SIP INVITE doesn't make it to the OBi200.
I would try matching the userid in the OBi110 Line Port InboundCallRoute with the AuthUserName setup on SP2 or SP4. In other words, for SP4 I would try setting up SP4 AuthUserName with taoman, matching the userid you have in the OBi110 Line Port InboundCallRoute (taoman@192.168.1.200:5063).
Taoman:
Quote from: hwittenb on October 07, 2014, 11:46:09 am
I would try matching the userid in the OBi110 Line Port InboundCallRoute with the AuthUserName setup on SP2 or SP4. In other words, for SP4 I would try setting up SP4 AuthUserName with taoman, matching the userid you have in the OBi110 Line Port InboundCallRoute (taoman@192.168.1.200:5063).
Unfortunately, that's the way I've had it from the beginning with no joy.
hwittenb:
Just to see if it makes any difference, disable OBiTalk and test the call again. With some previous tests, I saw my adapter sending the call to the OBi server instead of the specified location and disabling OBiTalk fixed the problem, however now it doesn't do that and I'm not sure what caused sending the sip uri there.
Taoman:
So is the only way to disable Obitalk is to remove the device from the OBi portal?
Navigation
[0] Message Index
[#] Next page
[*] Previous page