Author |
|
tompinuk Intermediate
Joined: February 22 2012 Location: United Kingdom Posts: 1
|
Posted: February 22 2012 at 6:30am | IP Logged
|
|
|
Hi, I'm new to this forum and Centrex proxy.
We are placing the proxy between a Yealink T26 phone and
a 3CX PBX.
When Yealink is configured to a 3CX listening on port
5060 it does not add the port number into the REGISTER
Request-Line. The registration fails as proxy does not
forward the REGISTER to the 3CX.
==================================================
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From:
10.158.202.206:5062) <<<<
REGISTER sip:10.158.202.203 SIP/2.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1258652967
From: "1000" <sip:1000@10.158.202.203>;tag=27124254
To: "1000" <sip:1000@10.158.202.203>
Call-ID: 93466183@10.158.202.206
CSeq: 794 REGISTER
Contact: <sip:1000@10.158.202.206:5062>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS,
NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE,
MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.61.23.1 00:15:65:22:02:b9
Expires: 0
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To:
10.158.202.206:5062) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1258652967;rport=5062;r
eceived=10.158.202.206
From: "1000" <sip:1000@10.158.202.203>;tag=27124254
To: "1000" <sip:1000@10.158.202.203>;tag=41
Call-ID: 93466183@10.158.202.206
CSeq: 794 REGISTER
Contact: <sip:1000@10.158.202.206:5062>;expires=0
Expires: 0
Server: LanScape Centrex Proxy/3.42.2.12
(www.LanScapeCorp.com)
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From:
10.158.202.206:5062) <<<<
SUBSCRIBE sip:1000@10.158.202.203 SIP/2.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK541787898
From: "1000" <sip:1000@10.158.202.203>;tag=1248032973
To: "1000" <sip:1000@10.158.202.203>
Call-ID: 1839474047@10.158.202.206
CSeq: 1 SUBSCRIBE
Contact: <sip:1000@10.158.202.206:5062>
Accept: application/simple-message-summary
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.61.23.1 00:15:65:22:02:b9
Expires: 3600
Event: message-summary
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To:
10.158.202.206:5062) >>>>
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK541787898;rport=5062;re
ceived=10.158.202.206
From: "1000" <sip:1000@10.158.202.203>;tag=1248032973
To: "1000" <sip:1000@10.158.202.203>
Call-ID: 1839474047@10.158.202.206
CSeq: 1 SUBSCRIBE
Server: LanScape Centrex Proxy/3.42.2.12
(www.LanScapeCorp.com)
Content-Length: 0
==================================================
When Yealink is configured to a 3CX listening on another
port (say 6500) it does add the port number into the
REGISTER Request-Line. The registration is fine as the
REGISTER is forwarded correctly to the 3CX.
==================================================
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From:
10.158.202.206:5062) <<<<
REGISTER sip:10.158.202.203:6500 SIP/2.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1756516630
From: "1000"
<sip:1000@10.158.202.203:6500>;tag=1075307390
To: "1000" <sip:1000@10.158.202.203:6500>
Call-ID: 319703284@10.158.202.206
CSeq: 1 REGISTER
Contact: <sip:1000@10.158.202.206:5062>
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS,
NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE,
MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.61.23.1 00:15:65:22:02:b9
Expires: 900
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To:
10.158.202.203:6500) >>>>
REGISTER sip:10.158.202.203:6500 SIP/2.0
Via: SIP/2.0/UDP
10.158.202.203:6000;branch=z9hG4bKfbb9e6b022c11b70d45998d
1d275a1f51.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1756516630;rport=5062;r
eceived=10.158.202.206
From: "1000"
<sip:1000@10.158.202.203:6500>;tag=1075307390
To: "1000" <sip:1000@10.158.202.203:6500>
Call-ID: 319703284@10.158.202.206
CSeq: 1 REGISTER
Contact: <sip:1000@10.158.202.206:5062>
max-forwards: 69
expires: 900
Server: LanScape Centrex Proxy/3.42.2.12
(www.LanScapeCorp.com)
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS,
NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE,
MESSAGE
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From:
10.158.202.203:6500) <<<<
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
10.158.202.203:6000;branch=z9hG4bKfbb9e6b022c11b70d45998d
1d275a1f51.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1756516630;rport=5062;r
eceived=10.158.202.206
Proxy-Authenticate: Digest
nonce="414d535c055553f815:d84a3bc1d3ead56a7286dde475d5bbb
b",algorithm=MD5,realm="3CXPhoneSystem"
To: "1000"<sip:1000@10.158.202.203:6500>;tag=c239a420
From: "1000"<sip:1000@10.158.202.203:6500>;tag=1075307390
Call-ID: 319703284@10.158.202.206
CSeq: 1 REGISTER
User-Agent: 3CXPhoneSystem 10.0.23053.0
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To:
10.158.202.206:5062) >>>>
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1756516630;rport=5062;r
eceived=10.158.202.206
From: "1000"
<sip:1000@10.158.202.203:6500>;tag=1075307390
To: "1000" <sip:1000@10.158.202.203:6500>;tag=c239a420
Call-ID: 319703284@10.158.202.206
CSeq: 1 REGISTER
Proxy-Authenticate: Digest realm="3CXPhoneSystem",
nonce="414d535c055553f815:d84a3bc1d3ead56a7286dde475d5bbb
b", algorithm=MD5
Server: LanScape Centrex Proxy/3.42.2.12
(www.LanScapeCorp.com)
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From:
10.158.202.206:5062) <<<<
REGISTER sip:10.158.202.203:6500 SIP/2.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1140695155
From: "1000"
<sip:1000@10.158.202.203:6500>;tag=1075307390
To: "1000" <sip:1000@10.158.202.203:6500>
Call-ID: 319703284@10.158.202.206
CSeq: 2 REGISTER
Contact: <sip:1000@10.158.202.206:5062>
Proxy-Authorization: Digest username="1000",
realm="3CXPhoneSystem",
nonce="414d535c055553f815:d84a3bc1d3ead56a7286dde475d5bbb
b", uri="sip:10.158.202.203:6500",
response="138811e197fc97f6a27010c13ddf5219",
algorithm=MD5
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS,
NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE,
MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T26P 6.61.23.1 00:15:65:22:02:b9
Expires: 900
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To:
10.158.202.203:6500) >>>>
REGISTER sip:10.158.202.203:6500 SIP/2.0
Via: SIP/2.0/UDP
10.158.202.203:6000;branch=z9hG4bKf4b0c2441e60f3c28b8e2db
11e25a6842.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1140695155;rport=5062;r
eceived=10.158.202.206
From: "1000"
<sip:1000@10.158.202.203:6500>;tag=1075307390
To: "1000" <sip:1000@10.158.202.203:6500>
Call-ID: 319703284@10.158.202.206
CSeq: 2 REGISTER
Contact: <sip:1000@10.158.202.206:5062>
Proxy-Authorization: Digest username="1000",
realm="3CXPhoneSystem",
nonce="414d535c055553f815:d84a3bc1d3ead56a7286dde475d5bbb
b", uri="sip:10.158.202.203:6500",
response="138811e197fc97f6a27010c13ddf5219",
algorithm=MD5
max-forwards: 69
expires: 900
Server: LanScape Centrex Proxy/3.42.2.12
(www.LanScapeCorp.com)
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS,
NOTIFY, REGISTER, SUBSCRIBE, REFER, PUBLISH, UPDATE,
MESSAGE
Content-Length: 0
<<<< (PROXY) RxRxRxRxRxRxRxRxRxRxRxRxRxRxRx (From:
10.158.202.203:6500) <<<<
SIP/2.0 200 OK
Via: SIP/2.0/UDP
10.158.202.203:6000;branch=z9hG4bKf4b0c2441e60f3c28b8e2db
11e25a6842.0
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1140695155;rport=5062;r
eceived=10.158.202.206
Contact: <sip:1000@10.158.202.206:5062>;expires=900
To: "1000"<sip:1000@10.158.202.203:6500>;tag=e1174c76
From: "1000"<sip:1000@10.158.202.203:6500>;tag=1075307390
Call-ID: 319703284@10.158.202.206
CSeq: 2 REGISTER
User-Agent: 3CXPhoneSystem 10.0.23053.0
Content-Length: 0
>>>> (PROXY) TxTxTxTxTxTxTxTxTxTxTxTxTxTxTx (To:
10.158.202.206:5062) >>>>
SIP/2.0 200 OK
Via: SIP/2.0/UDP
10.158.202.206:5062;branch=z9hG4bK1140695155;rport=5062;r
eceived=10.158.202.206
From: "1000"
<sip:1000@10.158.202.203:6500>;tag=1075307390
To: "1000" <sip:1000@10.158.202.203:6500>;tag=e1174c76
Call-ID: 319703284@10.158.202.206
CSeq: 2 REGISTER
Contact: <sip:1000@10.158.202.206:5062>;expires=900
Expires: 900
Server: LanScape Centrex Proxy/3.42.2.12
(www.LanScapeCorp.com)
Content-Length: 0
==================================================
I have posted 2 PDFs with some environmental info and
screenshots to the insperix FTP area on your FTP servers.
Do I have a config error somewhere?
Regards, Tom
|
Back to Top |
|
|
support Administrator
Joined: January 26 2005 Location: United States Posts: 1666
|
Posted: February 23 2012 at 6:03am | IP Logged
|
|
|
Hi Tom,
Everything in the SIP looks normal from what I see.
If you have your LanScape SIP proxy using port 5060, change that to another port and see if registrations from the phones using port 5060 are then forwarded to the 3CX pbx. I would have to look into the code and run fake REGISTER scenarios based on your SIP to see why this may be occurring.
When we spoke on the phone, I mentioned that SIP interoperability issues could arise. If there are SIP interoperability issues, we can eventually address them in order to get all the REGISTER and call flow scenarios working as we like.
For now, get as much of your deployed scenario working as possible. We can keep track of any issues that we may eventually want to address.
Free support:
I am sure you already know this…
Please note that free support is limited. Free support is for helping customers with simple questions regarding our software products and for basic configuration issues. Only with paid support do we get involved with investigating SIP interoperability issues. Customers who do not require paid support handle all their own issues as required.
Thanks,
RJ
|
Back to Top |
|
|
|
|