Sorry. VO correctly doesn't set reply-to, and my MUA, Zimbra, doesn't do reply-to lisr.
I typed it by hand, and put in the wrong list name. - jra Adam Rothschild <[email protected]> wrote: >How is this considered even remotely relevant to the NANOG list? > >VoiceOps, I can sort of see... > >On Wed, Jan 22, 2014 at 3:23 PM, Jay Ashworth <[email protected]> wrote: >> ----- Original Message ----- >>> From: "Tim Donahue" <[email protected]> >> >>> We ported this to an underlying carrier (the guilty party shall >remain >>> nameless), and according to their engineers they have no option to >>> disable the SSC. >>> >>> I actually have no idea if the call I am making is blocked at the >local >>> switch for my POTS test line, the LD carrier, or inbound to our ULC >(or any >>> other part of the path it might have crossed). This information was >not >>> provided to me in the response from our ULC, but it would be >interesting to >>> know for future reference where these blocks happen. >> >> Waitaminnit. >> >> The calls are being blocked... well, they'd have to be being blocked >> *before they get to your gaining carrier, I guess, right? >> >> That nearly *requires* the code to be in the LERG, so the originating >CO >> can execute it. We have some people here who know the LERG back and >fro; >> Paul? Anyone else? You ever heard of this? >> >> Can you originate a call to that number from a different carrier via >> PRI, and see which ISDN error you get back? Or have someone else >call >> it that way? >> >> ISDN errors tend to have a bit more data in them. >> >> I'd do it, but I don't have any PRIs laying around anymore. >> >> Cheers, >> -- jra >> -- >> Jay R. Ashworth Baylink >[email protected] >> Designer The Things I Think >RFC 2100 >> Ashworth & Associates http://www.bcp38.info 2000 Land >Rover DII >> St Petersburg FL USA BCP38: Ask For It By Name! +1 727 >647 1274 >> -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
