magicJack and magicJack Plus Support, Reviews, FAQs and Tricks

Yes, as I had suspected almost 6 months ago; proxy in the middle solution is the most effective solution for this problem. I personally use MJMD5 and it is working flawlessly since June. But nice to know that there are other solutions. I think we are due for another counter measure from Dan.

OK, I just want to give feedback on my findings and how I got a working prototype with my ATA. For obvious reasons, I will not keep this at "design level". To be very blunt, if anyone reading this is assuming that they will find a cookie cutter solution that they can implement on their end, then ...

OK, I am just getting handle on this counter measure. I do not want to get ahead of myself, but I appreciate the amount of time Dan has put in this counter measure. For shits and grins, I used sipp (sipp.sourceforge.net) as a starting point to replicate the traffic between my computer and MJ servers ...

IPKALL + ATA = Free & unlimited inncoming
For outgoing, I subscribed to www.localphone.com (0.7c US). I don't think anybody can beat that.

Also, I saw the exact same Authorization tag in SIP header from X-lite client (with different nonce field). So I don't think Authorization tag makes any difference.

I am beginning to zero in on the branch field value as what makes authorization successful or not. It seems to me that the branch ...

What I am wondering is how does the branch id change between first call to proxy (unauthorized) and second call to proxy with a differnt branch id - which is authoprized by server. Clearly the last 16 digits for second (successful) call are different. Any ideas on how this branch id was generated?

here is my hypothesis (not proven yet).

STEP 1: MJ dongle makes 1st SIp call to register, with branch # of 32 alphanumerics. First 16 are constant, secong 16 are tied to your dongle.

STEP 2: SIP server responds with a new branch id, as well as message Authorization failed.

STEP 3: Then MH ...

I compared the SIP request/response for both MJ and X-lite. I noticed (among other things) that "Via" Message header (for successful registration through MJ dongle) contains a tring "branch=XXXXXXXXXXXXXXXXYYYYYYYYYYYYYYYY" (32 alphanumerics), where X is a constant, but Y keeps on changing every ...