Need help bridging two OBIs on internal network
Taoman:
Quote from: ianobi on October 08, 2014, 09:45:00 am
I think this problem is that good old "gotcha" the reserved characters, in this case "m".
Try putting taoman within single quotes in the InboundCallRoutes: 'taoman'
I've been caught like this a few times, so I now use mostly numbers as my CallerIDs.
Thanks for the suggestion but still no luck. I tried with quote marks around the userid and also tried an all numerical userid. Both had the same results and eventually times out with:
SIP_TS:INVITE Times out
Taoman:
Quote from: hwittenb on October 07, 2014, 02:33:55 pm
Edit: If the Sip Invite is being sent properly, the Syslog should also show if it is sending inside the Sip Invite the OBi110's local network ip address or an external ip address.
So I set up syslog on my OBi200 to see if the SIP INVITE was actually making it there from my OBi110. It definitely is. I changed my username to 1954. I don't see any obvious errors. Do you? It just seems like I must be missing something simple.
Edit: It seems to me if the syslog on the OBi200 shows the FXO port is "ringing" and there is an incoming call there should be something in the call history on the OBi200. No?
Quote
<7> [CPT] tone compression done - 8242 !!
<7> [DAA]: FXO ring on
<7> [0]Ring On
<7> FXO:NewTermState:ringing
<7> ------ caller id (pcm_id: 1) received! ------------<7> [0]DAA CND 10081356,360XXXXXXX,Cell Phone WA,,,
<7> [0]DAA CND 10081356,360XXXXXXX,Cell Phone WA,,,
<7> XMPP:Updating peer:someone@gmail.com[MessagingA9f799dc] to online
<7> XMPP:Updating peer:someone@gmail.com[MessagingA146656b2] to online
<7> [SLIC] CID to deliver: 'Cell Phone WA' 360XXXXXXX
<7> sendto c0a801c8:5063(877)
INVITE sip:1954@192.168.1.200:5063 SIP/2.0
Call-ID: 6fe09b97@192.168.1.2
Content-Length: 307
CSeq: 8001 INVITE
From: <sip:360XXXXXXX@192.168.1.200>;tag=SP211939d82391f146
Max-Forwards: 70
To: <sip:1954@192.168.1.200>
Via: SIP/2.0/UDP 192.168.1.2:5084;branch=z9hG4bK-24d62743;rport
User-Agent: OBIHAI/OBi110-1.3.0.2872
Contact: <sip:1954@192.168.1.2:5084>
Expires: 60
Supported: replaces
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER,UPDATE
Remote-Party-ID: <sip:360XXXXXXX@192.168.1.200>;party=calling;privacy=off
Content-Type: application/sdp
v=0
o=- 74158 1 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
azrobert:
Does this change make a difference?
OBi200 SP4 Service -> X_InboundCalllRoute: ph
Taoman:
Quote from: azrobert on October 08, 2014, 02:32:15 pm
Does this change make a difference?
OBi200 SP4 Service -> X_InboundCalllRoute: ph
Unfortunately, no. That was one of the first things I tried when it didn't work.
hwittenb:
Quote from: Taoman on October 08, 2014, 02:14:16 pm
Edit: It seems to me if the syslog on the OBi200 shows the FXO port is "ringing" and there is an incoming call there should be something in the call history on the OBi200. No?
Taoman,
The OBi200 does not have an FXO port. I think the syslog you posted is from the OBi110, and you're right there is nothing in there from the OBi200. To be sure you could disable the syslog on the OBi110 and try with just the OBi200 activated.
<7> sendto c0a801c8:5063(877)
That says the INVITE is going to port 5063 at c0a801c8 which is hex for 192.168.1.200
http://www.silisoftware.com/tools/ipconverter.php?convert_from=c0a801c8
Yes, if the sip INVITE makes it to the part of the OBi200 that captures the incoming call it should show in the Syslog.
My guess is something is discarding or diverting it.
As I previously said when I encountered my problem with the OBiTalk it did not show up in the Syslog.
Navigation
[0] Message Index
[#] Next page
[*] Previous page