SIP registration problems - please help!
Stewart:
At this point, I don't know whether this might be an ALG problem -- it's still possible that e.g. field length or header order might be making the difference. With luck, the Wireshark traces will show what's happening.
If you are using ASAHI Net just for incoming and for calling free 050 numbers, the cost is only a few yen, so I hope we can make it work -- anything else would cost more, or have significant limitations. For example, an Anveo Tokyo DID (Value plan) is $6.45/mo. A free solution that would work only for specific contacts is Rebtel, set up to ring a free Callcentric (or other) iNum. A caller who is not a contact could still reach you, but it would require two-stage dialing. For example, if you call a SIPBroker access number such as 06-45604000, and at the prompt enter *4621777xxxxxxx (use the last 7 digits of your Callcentric number), your OBi phone should ring.
ichigo:
Yes, the other options are either more complicated or costlier - usually both. So I would be relieved if this worked! I sent you a PM with a few more details. Let me know if you need anything else.
Stewart:
In the Airport Express, try forwarding UDP port 5061 to the OBi. Because of a number of factors, it appears that a contact header with a bad port number is being generated. I am hoping that with the forwarding in place, the AE won't translate the source port on the REGISTER requests.
If no luck, please post captures in the OBi ASAHI case, with at least 5 SIP packets (initial REGISTER attempt, 401 response, REGISTER with Authorization, ??? response and ??? next request).
ichigo:
Sorry, I had forgotten to mention that during my initial run-in with this problem, even before I made my first post in this forum, I had come across something on the web and had made the changes suggested. You can check out the post here:
http://forums.counterpath.com/viewtopic.php?f=1&t=3820
As suggested in that post, I forwarded UDP (and TCP) ports 5060-5061 to the OBi. I also disabled the X_UseRport option in Service Providers > ITSP Profile B > SIP (option not available in OBi Expert config - only when you login to the device directly).
Earlier (before the port forwarding and the rport setting), the OBi status kept showing "Waiting for server response". After the changes, I got the 401. If I enable rport and keep the port forwarding, I keep getting a 400 error.
Anyway, since the earlier logs I forwarded were with the ports forwarded already, here's the rest of the response to the REGISTER with Authorization and the next request:
Response to the REGISTER with Authorization
SIP/2.0 401 Unauthorized
Call-ID: 3ffdeaaa@192.168.0.3
l: 0
CSeq: 36720 REGISTER
From: <sip:050xxxxxxxx@asahi-net.or.jp>;tag=SP2246066421cf1cc74
To: <sip:050xxxxxxxx@asahi-net.or.jp>
v: SIP/2.0/UDP 192.168.0.3:5061;received=118.xx.xx.xx;branch=z9hG4bK-64466080
User-Agent: OBIHAI/OBi100-1.3.0.2690
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER
Supported: replaces
Date: Sat, 17 Mar 2012 06:38:10 GMT
WWW-Authenticate: Digest realm="ocn.ne.jp", domain="sip:210.227.109.205", nonce="1331964245", opaque="", stale=FALSE, algorithm=MD5
Next request
REGISTER sip:asahi-net.or.jp:5060 SIP/2.0
Call-ID: 3ffdeaaa@192.168.0.3
Content-Length: 0
CSeq: 36721 REGISTER
From: <sip:050xxxxxxxx@asahi-net.or.jp>;tag=SP2246066421cf1cc74
Max-Forwards: 70
To: <sip:050xxxxxxxx@asahi-net.or.jp>
Via: SIP/2.0/UDP 192.168.0.3:5061;branch=z9hG4bK-9bad5b4
Authorization: DIGEST algorithm=MD5,nonce="1331964245",opaque="",realm="ocn.ne.jp",response="fd261e8e81c87398d84af2d8322d346f",uri="sip:asahi-net.or.jp:5060",username="XXXXXXXX"
User-Agent: OBIHAI/OBi100-1.3.0.2690
Contact: <sip:050xxxxxxxx@118.xx.xx.xx:5061>;expires=60;+sip.instance="<urn:uuid:00000000-0000-0000-0000-9cadef1035b2>"
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,OPTIONS,REFER
Supported: replaces
Stewart:
It appears that there are a combination of three constraints (any two of which would not be a problem).
1. The OBi insists on processing the Via received parameter, even when rport is turned off.
2. The AE insists on translating the source port number, even with the port forwarded.
3. ASAHI refuses to accept an rport parameter.
At this point, I have few suggestions remaining. If you haven't yet tried this, test with X_UserAgentPort set to 5060, with port 5060 forwarded to the OBi. (To avoid a conflict, you may need to change X_UserAgentPort for SP1 to something else, even though your SP1 is not SIP.)
A second possibility is connecting the Mac directly to the modem, setting up PPPoE on the Mac. Then, set up sharing to share the PPP connection via Wi-Fi and configure the Time Capsule to connect to the Mac.
Possibly, you can "launder" the connection through a free PBXes account, though I don't know whether you'll have an rport issue there. (I'll give you suggested settings for the trunk, if you want to try.)
There might be another free PBX that you could relay through, but I'm not familiar with any. Perhaps another member can chime in here.
You could almost certainly fix the problem by running e.g. FreeSWITCH on your Mac, but that would be a lot of work.
Can you take the OBi over to another site (friend, neighbor, work) and see whether a different router helps?
Navigation
[0] Message Index
[#] Next page
[*] Previous page