Hi John.

I did look at the -V output and couldn't see anything different, though I may have missed something. I'll try again, and maybe I'll post the results if I still don't see anything.

The "billion" brand router is the only one I've encountered so far where I'm having this problem. Is it the router? I have no clue, but it's the only thing different from one site to another. I've tried Linksys, Netgear, and a generic no-name brand so far) Is it SER? Again, I'm not sure. I'm hoping someone else out there has seen this problem and knows why it's happening and, maybe, how to fix it.

Unfortunately, I don't have access to sniff the packets at the far end. This isn't the end of the world. I'm working on a fix that will let us handle the alpha-numeric UID's, but it's something I didn't really want to deal with yet, and if this is easily solved, all the better!

I'll let you all know if I come up with anything in the meantime.

Tom

-----Original Message----- From: John Todd [mailto:jtodd@loligo.com] Sent: Wednesday, June 09, 2004 5:19 PM To: Tom Lowe Cc: serusers@lists.iptel.org Subject: Re: [Serusers] Numeric UID's and ATA186's

Tom - I'd suggest running tethereal in "-V" mode for those requests to really look at what's going on.

Also, you're suggesting that the "billion" brand DSL router is the only one that cannot have an all-numeric user ID? The others work fine? Is this an issue that is somehow related to SER?

I would strongly suggest looking at the exact same packets on the "inside" of the DSL box, and then looking at those same packets on the interface on your SER device, and comparing them. It sounds like (from your description) that the billion router has some type of "SIP fixup" trick that is working exactly as unintended (as most "SIP fixup" tricks tend to do.)

JT