Re: [VoiceOps] Disconnected numbers and SIP

-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ Sent from my BlackBerry.   Original Message   From: Brooks Bridges Sent: Wednesday, October 21, 2015 14:14 To: VoiceOps Subject: Re: [VoiceOps] Disconnected numbers and SIP "6xx

Re: [VoiceOps] Disconnected numbers and SIP

: Re: [VoiceOps] Disconnected numbers and SIP Can't a 404 sometimes be taken as evidence that an intermediate network element (e.g. a wholesale provider's LCR) doesn't have the destination in route? Or do they just return the all-encompassing 503 in those cases? ‎ -- Alex Balashov | Principal

Re: [VoiceOps] Disconnected numbers and SIP

1, 2015 11:04 AM To: Peter E Cc: VoiceOps Subject: Re: [VoiceOps] Disconnected numbers and SIP I see 404 fairly commonly used to indicate "I don't have a route for this". 6xx codes are supposed to be used to indicate definitive knowledge that a number can't be reached by any other mean

Re: [VoiceOps] Disconnected numbers and SIP

lashov Cc: Paul Timmins; VoiceOps Subject: Re: [VoiceOps] Disconnected numbers and SIP ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops ___ VoiceOps mailin

Re: [VoiceOps] Disconnected numbers and SIP

I see 404 fairly commonly used to indicate "I don't have a route for this". 6xx codes are supposed to be used to indicate definitive knowledge that a number can't be reached by any other means globally. -- Alex Balashov | Principal | Evariste Systems LLC 303 Perimeter Center North, Suite 300

Re: [VoiceOps] Disconnected numbers and SIP

We've found 404 to be extremely reliable when received from upstream carriers. It's one of the very few codes that we don't route advance on because we found that calls never compete if someone hands back a 404. JM On Tue, Oct 20, 2015 at 10:48 PM, Alex Balashov

Re: [VoiceOps] Disconnected numbers and SIP

Timmins; VoiceOps Subject: Re: [VoiceOps] Disconnected numbers and SIP ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disconnected numbers and SIP

8.444., Option 2 > email: bbrid...@o1.com | web: www.o1.com > > -Original Message- > From: VoiceOps [mailto:voiceops-boun...@voiceops.org] On Behalf Of Alex > Balashov > Sent: Wednesday, October 21, 2015 11:04 AM > To: Peter E > Cc: VoiceOps > Subject:

Re: [VoiceOps] Disconnected numbers and SIP

id...@o1.com | web: www.o1.com -Original Message- From: Paul Timmins [mailto:p...@timmins.net] Sent: Wednesday, October 21, 2015 12:06 PM To: Brooks Bridges Cc: VoiceOps Subject: Re: [VoiceOps] Disconnected numbers and SIP If this was true, why does ISUP 1 map to 404 by standard? On Oct 21, 2015

Re: [VoiceOps] Disconnected numbers and SIP

October 20, 2015 7:57 PM To: Peter E Cc: VoiceOps Subject: Re: [VoiceOps] Disconnected numbers and 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 | Principa

Re: [VoiceOps] Disconnected numbers and SIP

‎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

Re: [VoiceOps] Disconnected numbers and SIP

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,

Re: [VoiceOps] Disconnected numbers and SIP

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

Re: [VoiceOps] Disconnected numbers and SIP

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

Re: [VoiceOps] Disconnected numbers and SIP

r 20, 2015 22:32 To: Alex Balashov Cc: VoiceOps Subject: Re: [VoiceOps] Disconnected numbers and SIP ___ VoiceOps mailing list VoiceOps@voiceops.org https://puck.nether.net/mailman/listinfo/voiceops

Re: [VoiceOps] Disconnected numbers and SIP

‎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 

Re: [VoiceOps] Disconnected numbers and SIP

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

Re: [VoiceOps] Disconnected numbers and SIP

+1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ Sent from my BlackBerry.   Original Message   From: Peter E Sent: Tuesday, October 20, 2015 22:55 To: Alex Balashov Cc: VoiceOps Subject: Re: [VoiceOps] Disconnected numbe