Verizon WCTP stopped cold

[CLingle]

Hello,

Our connection to the Verizon WCTP service stopped dead mid December. The Verizon folks tell me that "there was a small outage resulting from maintenance that was performed Friday [12/16/2005] morning. This has been corrected and WCTP is now working."

It seems that NotePager is no longer able to authenticate and transmit pages. The error message reported by NotePager is "Message rejected: Invalid SenderID or securityCode 401".

Ok, so I setup a brand-new account with Verizon via their Web site, thinking that their outage hosed our WCTP account. Still having authentication (I believe) issues.

Comments?

Thanks!

- Curt

[CLingle]

Verizon recommended that I setup yet another WCTP account via their Web site at:

http://wctp.myairmail.com/wctpRegistration/

Having done so, I still receive the "Invalid SenderID or securityCode 401" error as the log below indicates:


1/12/2006 11:03:56 AM ====================================
1/12/2006 11:03:56 AM Start connection to carrier: Verizon
1/12/2006 11:03:56 AM Send using WCTP protocol
1/12/2006 11:03:56 AM ------------------------------------------------
1/12/2006 11:03:56 AM Working on message to: John Doe from: myuserid
1/12/2006 11:03:56 AM Formatting message
1/12/2006 11:03:56 AM Message contained in single packet
1/12/2006 11:03:57 AM Sending message
1/12/2006 11:03:57 AM Sent:
1/12/2006 11:03:57 AM <?xml version="1.0"?>
1/12/2006 11:03:57 AM <!DOCTYPE wctp-Operation SYSTEM "http://dtd.wctp.org/wctp-dtd-v1r1.dtd">
1/12/2006 11:03:57 AM <wctp-Operation wctpVersion="wctp-dtd-v1r1">
1/12/2006 11:03:57 AM <wctp-SubmitClientMessage>
1/12/2006 11:03:57 AM <wctp-SubmitClientHeader submitTimestamp="2006-01-12T18:03:57">
1/12/2006 11:03:57 AM <wctp-ClientOriginator senderID="myuserid@" miscInfo="mypassword" />
1/12/2006 11:03:57 AM <wctp-ClientMessageControl preformatted="true" />
1/12/2006 11:03:57 AM <wctp-Recipient recipientID="3035551212" />
1/12/2006 11:03:57 AM </wctp-SubmitClientHeader>
1/12/2006 11:03:57 AM <wctp-Payload>
1/12/2006 11:03:57 AM <wctp-Alphanumeric>dispatch4:TEST MESSAGE</wctp-Alphanumeric>
1/12/2006 11:03:57 AM </wctp-Payload>
1/12/2006 11:03:57 AM </wctp-SubmitClientMessage>
1/12/2006 11:03:57 AM </wctp-Operation>
1/12/2006 11:03:57 AM Recieved:
1/12/2006 11:03:57 AM <?xml version="1.0" encoding="UTF-8"?>
1/12/2006 11:03:57 AM <!DOCTYPE wctp-Operation SYSTEM "http://wctp.myairmail.com/wctp/wctp-dtd-v1r1.dtd">
1/12/2006 11:03:57 AM <wctp-Operation wctpVersion="wctp-dtd-v1r1.dtd" wctpToken="x226"><wctp-SubmitClientResponse><wctp-Failure errorText="Invalid senderID or securityCode" errorCode="401"/></wctp-SubmitClientResponse></wctp-Operation>
1/12/2006 11:03:57 AM Message rejected: Invalid senderID or securityCode 401
1/12/2006 11:03:57 AM Permanent failure. Message will not be retried
1/12/2006 11:03:57 AM FAILED To:John Doe Frm:myuserid Msg:TEST MESSAGE
1/12/2006 11:04:22 AM Dialer Stopped

Anyone else having Verizon troubles?

- Curt

[Tech Support]

When you signed up for the WCTP account via their website, did they send you any information regarding what your Sender's information needed to be when sending via their WCTP terminal?

The message you're getting isn't that the message is being rejected, it's that the information you have in the Sender portion of the program isn't recognized. If you can find out what your Sender's ID should be, you can to go Tools - Settings - General and enter that in.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[CLingle]

Hello,

Thanks for the feedback. Here is what Verizon states when you activate (verify) the User ID via email:

-----

Congratulations, you have confirmed the Tech Email field on your Registration Form and your WCTP account is ready for immediate use.

Remember, in a wctp-SubmitRequest your username is placed in the wctp-Originator senderID attribute and your password should be in the wctp-Originator securityCode attribute.

Here is an sample line from a valid WCTP <wctp-SubmitRequest> request:

<wctp-Originator senderID="myUserName" securityCode="myPassWord"/>

Likewise, when you submit a wctp-SubmitClientMessage request, your username should be in the wctp-ClientOriginator senderID attribute, and your password in the wctp-ClientOriginator miscInfo attribute.

Here is an sample line from a valid WCTP <wctp-SubmitClientMessage> request:

<wctp-ClientOriginator senderID="myUserName" miscInfo="myPassWord"/>

Thanks for using WCTP.

-----

It looks like Notepager Pro is tacking on "@" at the end of the user name, perhaps this is the problem?

Thanks,

- Curt

[Tech Support]

Check the Sender's Name setion in Tools - Settings - General. Make sure that is set to what it needs to be, I would imagine that's where the connection sequence is pulling the information from, though I don't know where that @ symbol is coming from.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[CLingle]

Setup looks good. NotePager Pro is definitely inserting the "@" after the user ID. I edited the log above to remove private information. Can I email some unedited screen shots directly to you?

Thanks,

- Curt

[Tech Support]

Sure, the email address you want to send information to is support@notepage.com - if you would, also email me your npp.mdb file. I'd like to have a look at a few things in how you have it configured to try and figure this out.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[CLingle]

This was resolved by a patch from the NotePager Pro folks. The "@" symbol was removed from the ID field.

Thanks!

- Curt