June 19, 2019, 12:06:05 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: STUN ISSUES...not sure why...  (Read 3699 times)
slicemaster
Newbie
*
Posts: 15


« on: January 08, 2012, 04:57:13 pm »

Well, I have just been blown away by the community's ability to help out so here's another small issue I've been having. Anyways, it relates to the use of stun. I'm not very failure with the technicalities of logs and SIP diagnostic messages but this was more or less the response that call with us sent me in attempting to figure out the issue. Call With Us has always been very helpful and I think their support staff is awesome, however they are not familiar with OBIHAI equipment so hopefully someone here might be able to lend a hand...

The basic issue is that their servers still report that I'm still behind a NAT even with stun enabled...my other devices don't report such issues as the stun service on them seems to be working correctly...

here is a snipit from their log that shows the issue with a local ip being sent rather than the stun discovered address....

Dec 29 20:13:55 west /usr/local/sbin/kamailio[3457]: INFO: <script>: SIP message from udp:173.55.9.115:5060
REGISTER sip:sip.callwithus.com:5060 SIP/2.0
Call-ID: d2ee607b@192.168.1.166
Content-Length: 0
CSeq: 53929 REGISTER
From: "MY NAME" <sip:MYCALLWITHUSACCOUNTNUMBER@sip.callwithus.com>;tag=SP17171c41e6a933bdf
Max-Forwards: 69
To: "MY NAME" <sip:MYCALLWITHUSACCOUNTNUMBER@sip.callwithus.com>
Via: SIP/2.0/UDP 192.168.1.166:5060;branch=z9hG4bK-17a184fd;rport
Authorization: DIGEST algorithm=MD5,nonce="Tv0RYU79EDXpZbUOc3BpVxAj+Ic8eQXZ",realm="sip.callwithus.com",response="a0b4eb
4340695f35eef072ec276d84da",uri="sip:sip.callwithus.com:5060",username="MYCALLWITHUSACCOUNTNUMBER"
User-Agent: OBIHAI/OBi110-1.3.0.2651
Contact: "MY NAME" <sip:MYCALLWITHUSACCONTNUMBER@173.55.9.115:5060>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9c
adef0074f0>"
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER
Supported: replaces


not sure what all this means but as you can see there's some local ip addresses in there... namely the 192.168.1.166 address...


Any ideas on how I can resolve this issue?

thanks,
Slice
Logged
hwittenb
Sr. Member
****
Posts: 332


« Reply #1 on: January 08, 2012, 08:15:54 pm »

The Contact: field in the Register request you posted does show your external ip address. 

The Call-ID field is not the caller-id.  It is a message identifier. 

RFC 3261 for the sip protocol discusses the Call-ID field
http://tools.ietf.org/html/rfc3261
Logged
slicemaster
Newbie
*
Posts: 15


« Reply #2 on: January 08, 2012, 11:21:47 pm »

Well, I'm no expert with SIP or stun so I'm not going to argue...however the caller id field is not the only location the local address is used... notice about halfway down...to the right of via...

Logged
slicemaster
Newbie
*
Posts: 15


« Reply #3 on: January 09, 2012, 12:53:44 am »

NOTE: I've been bumming around the forums and have found some people referencing the need to tell the obi to send the wan address that is obtained... what setting is this that people are talking about?

note: the only setting I took off of default pertaining to stun is the:
STUNEnable
STUNServer
X_STUNServerPort

is there anything else that needs to be set so that the obi makes good use of the stun information?

note: my stun server is stun.callwithus.com
Logged
Pages: [1]
  Print  
 
Jump to:  

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