PBXes (http://www1.pbxes.com/forum/index.php)
- English (http://www1.pbxes.com/forum/board.php?boardid=16)
-- Bugs (http://www1.pbxes.com/forum/board.php?boardid=24)
--- RE: Calls to SIP uri's (another extension) end up with 603 Declined (http://www1.pbxes.com/forum/threadid.php?threadid=1478520817)

Calls to SIP uri's (another extension) end up with 603 Declined

I'm trying to call from one extension to another via SIP URI, within same PBX, i.e. sip:username-NNN@pbxes.org. I do have per-extension incoming routes setup for username-NNN, routing calls properly.

This did work until about 2 weeks ago, but now i'm receiving "603 Declined". Same with the call to sip:username@pbxes.org (or sip:username@pbxes.com), which ended up in the auto-attendant before. Tried restarting PBX via "Submit & Start", no change.Tried varying clients - no difference, this appears to be server-side issue.

Thanks!

p.s. Just found approach which works - calling NNN@username.pbxes.org... Not sure if this legitimate way (i think there is a single wild-carded IP behind it), but at least it works.

--igor

RE: Calls to SIP uri's (another extension) end up with 603 Declined

@username.pbxes.org won't work correctly. If you want to call SIP URIs on PBXes internally, please try to call @pbxes.com.

RE: Calls to SIP uri's (another extension) end up with 603 Declined

Well, in the past (since June until ~4 weeks ago) I'd no problems calling username-xxx@pbxes.com from another extension (Android native SIP); but in the last 3 weeks I'm getting 603 Declined to such calls from multiple devices to multiple extensions. This what i mean by bug :-(