Does ISUP have a code for this? Is it consistently signalled in the
intermachine world?
What about Q.931?
(Sorry for unintentional off-list replies. This list doesn't send a list
Reply-To seemingly.)
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Agree. 503 has become badly misused.
On Oct 20, 2015, at 22:48, Alex Balashov wrote:
Thanks. And I'm guessing the best one can hope for from a SIP termination
provider is an ambiguous 404, or, more likely, a 503, which seems to have
become misused an opaque,
We struggled with this and eventually integrated our switch with Speedeon Data.
They have a disconnected number scrubbing API. We sell it as an additional
feature to customers who are interested in knowing when numbers are
disconnected.
On Oct 20, 2015, at 7:39 PM, Alex Balashov
Wouldn't is be cause code 1, unallocated number?
http://www.dialogic.com/webhelp/img1010/10.5.2/webhelp/General_Reference/def_sip-ss7_cc.htm
On Oct 20, 2015, at 21:38, Alex Balashov wrote:
Hello,
Are there ISUP cause codes for disconnected numbers? And if so, do
I would have thought 1 means that the number has no entry in a switch
translation table, which is something logically distinct from disconnection. I
suppose it depends on how LECs implement the state of affairs to which
"disconnected" colloquially refers.
--
Alex Balashov | Principal |
Thanks. And I'm guessing the best one can hope for from a SIP termination
provider is an ambiguous 404, or, more likely, a 503, which seems to have
become misused an opaque, catch-all epithet for any and all completion failures?
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter
I would consider anything but 404 (at least as long as the terminating LEC send
a cause code 1 properly) a glaring bug that I would demand a fix for until I
received one, but I have different standards than most (many?) folk it seems.
But I have zero tolerance for exotica on my TDM or SIP
Yeah, looked at that. I meant more from a "de facto" / what vendors actually do
perspective, which, as you know, has tenuous attachment to the RFCs. :-)
--
Alex Balashov | Principal | Evariste Systems LLC
303 Perimeter Center North, Suite 300
Atlanta, GA 30346
United States
Tel: