Quote:
Originally Posted by martin
The reason it does not show up as registered is because the provider changes the port from 5060 to some other value during registration.
So when our system tries to reconcile the status information it does not match.
We have an item in our problem tracking system to look at alternate ways to perform this reconciliation.
|
I'm afraid i can't wok out what your problem is from the brief description you gave ...
Our platform responds to REGISTERs exactly as defined in RFC 3261 - or at least should! If you have any problems then feel free to email me directly (theo@voip.co.uk) and we can work out any interop issues.
PS: a quick trace shows nothing wrong other than the fact your client is showing the same pathologically broken symptoms asterisk exhibits (see the notes about asterisk & SRV on
products:asterisk [wiki.VoIP.co.uk]
REGISTER sip
roxy.voip.co.uk:6060 SIP/2.0
[snip]
Contact: <sip:XXXXXX@85.17.19.194:5061>
SIP/2.0 200 OK
[snip]
Contact: <sip:XXXXXX@85.17.19.194:5061>;expires=120
Content-Length: 0