Solved Problem with PAP2 after upgrading from V15.5 to V16.

[Rob59]

change this for test, in User ID normally this is something alphanumeric and not extension number
View attachment 14105

What should I enter in the User ID field instead? Leave empty?

 

[Rob59]

change this for test, in User ID normally this is something alphanumeric and not extension number
View attachment 14105

What should I enter as User ID? Leave empty?

Sorry for double post, thought it did not go trough...

 

[AWS2P]

not empty, enter what's in ID field from 3CX extension

 

[AWS2P]

this post is about SPA3102 settings but very similar
https://www.3cx.com/community/threads/spa3102-config.65405/#post-279372

 

[AWS2P]

is 10 your 3CX extension ?
perhaps I was wrong, password can be alphanumeric value but ID not, so change this on 3cx extension as per default is like my above capture so enter in 3CX extension the extension number (example 10) and in PAP enter same extension number as ID value

 

[Rob59]

is 10 your 3CX extension ?

Yes, 10 is the extension.

Changing the ID as suggested did not help.

I started the logger and checked the log with the SIP analyzer tool. The PAP is trying to connect. This is the message I found (I manually changed some digits to avoid leaking info)

28.01.2020 21:20:56:365 | 10 | Discarded invalid message: REGISTER sip:10.0.0.16 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.11:5060;branch=z9hG6bK-deea2cdc
From: rdr Trdls 1 <sip:[email protected]>;tag=a652082468611dcco0
To: rdr Trdls 1 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 32490 REGISTER
Max-Forwards: 70
Contact: rdr Trdls 1 <sip:[email protected]:5060>;expires=600
User-Agent: Linksys/PAP2T-3.1.15(LS)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura

Does this help in any way?

Forgot this line:

28.01.2020 21:21:16:364 | 10 | Invalid UTF8 sequence in incoming SIP message: 0xxe7 x64

 

[Rob59]

Yes, 10 is the extension.

Changing the ID as suggested did not help.

I started the logger and checked the log with the SIP analyzer tool. The PAP is trying to connect. This is the message I found (I manually changed some digits to avoid leaking info)

28.01.2020 21:20:56:365 | 10 | Discarded invalid message: REGISTER sip:10.0.0.16 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.11:5060;branch=z9hG6bK-deea2cdc
From: rdr Trdls 1 <sip:[email protected]>;tag=a652082468611dcco0
To: rdr Trdls 1 <sip:[email protected]>
Call-ID: [email protected]
CSeq: 32490 REGISTER
Max-Forwards: 70
Contact: rdr Trdls 1 <sip:[email protected]:5060>;expires=600
User-Agent: Linksys/PAP2T-3.1.15(LS)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura

Does this help in any way?

Forgot this line:

28.01.2020 21:21:16:364 | 10 | Invalid UTF8 sequence in incoming SIP message: 0xxe7 x64

Did some searching and this might have to do with some special characters I used in the extension names. Will do a change and report back.

 

[Rob59]

Did some searching and this might have to do with some special characters I used in the extension names. Will do a change and report back.

Problem solved

I had some scandinavian characters in both extensions on the PAP. This was not a problem up to version 15.5 but in version 16 it is... Removed these characters and the extensions went online immediatly.

Anyway thanks for the help!

 

[AWS2P]

Well done

 

[AWS2P]

Invalid UTF8 sequence in incoming

perhaps letters you used are not encoded in UTF8 and this is not the taste of PAP2.

 

[nb]

aws2p Thank you for helping so much!! I have forwarded an email to the forum admins informing them of your motivation and support on the forums. Keep it up!

Guys - This device is buried already..
Remember that now everything is going mobile. So PAP devices or any analog to sip devices, are forgotten. Keep in mind that many users are also dumping IP phones as well and replacing them with Smartphones.

I personally am very happy to be working with Mobile telecommunications, apps and smartphones. Because if I were in the IP Phone deskphone business, I would be very very very worried by now. Let alone playing about with ancient Linksys pap devices.

SIP never liked special characters. Just like email addresses - the protocols have the same base. If you notice we do not see special characters in email correct? Try and create an email with gmail with a special character and you will see that they won't let you. Some users are stubborn and insist to use mail clients that support emails with special characters only to find out that most of their emails will be bounced back.

So if the device is so old, leave them out in the authentication mechanism.
And leave them out in Caller id display names.

There are phones that allow and support this and 3CX can authenticate with or without special characters. But 3CX is modern and constantly gets updates.
And 3CX pushes and tells other phone manufacturers to update and improve.

But this device is dead so it is what it was a decade ago.