'Double' transfer failing with 403 error.
Moderator: Brekeke Support Team
'Double' transfer failing with 403 error.
1. Brekeke Product Name and version:
Brekeke PBX, Version 2.2.6.2 , Pro Evaluation
2. Java version:
3. OS type and the version:
XP SP 3
4. UA (phone), gateway or other hardware/software involved:
X-lite and LinkSys SPA942
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html : pattern 1
6. Your problem:
A caller on 4031 dials 4070. 4070 does not answer and is transferred to Voicemail (our own software that we are porting to VoIP) If the user does not make a selection from the 'front end' menu the VMS will transfer them to an operator extension.
This second transfer (VMS transfeering 4031 to operator) fails with a 403 error.
All extension involved are setup as UAs under the SIP server and as Users under the PBX.
Any help would be appreciated.
TIA
Brekeke PBX, Version 2.2.6.2 , Pro Evaluation
2. Java version:
3. OS type and the version:
XP SP 3
4. UA (phone), gateway or other hardware/software involved:
X-lite and LinkSys SPA942
5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html : pattern 1
6. Your problem:
A caller on 4031 dials 4070. 4070 does not answer and is transferred to Voicemail (our own software that we are porting to VoIP) If the user does not make a selection from the 'front end' menu the VMS will transfer them to an operator extension.
This second transfer (VMS transfeering 4031 to operator) fails with a 403 error.
All extension involved are setup as UAs under the SIP server and as Users under the PBX.
Any help would be appreciated.
TIA
Below are two WireShark captures.
This is a successful REFER.
REFER sip:4031@10.1.0.159:5060 SIP/2.0
From: "4000"<sip:4000@10.1.0.159>;tag=67b2550-7900010a-1b76-50022-2997f-5d3797c9-2997f
To: "4031"<sip:4031@10.1.0.159:5060>;tag=bbd7fe4f7p
Call-ID: 3608be7b-7be1932e-19db9c47-e9842525@10.1.0.159
CSeq: 1 REFER
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29992-a27e5bb-4dfea27d
Refer-To: <sip:1001@10.1.0.159>
Referred-By: <sip:10.1.0.121:7030>
Max-Forwards: 70
Supported: replaces
Route: <sip:10.1.0.159:5060;lr>
Contact: <sip:10.1.0.121:7030>
Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, REFER, NOTIFY
Allow-Events: refer
Content-Length: 0
This is a failed REFER
REFER sip:4031@10.1.0.159:5060 SIP/2.0
From: <sip:4000@10.1.0.159:5060>;tag=67b20a0-7900010a-1b76-50022-29715-6aaa490e-29715
To: "4031"<sip:4031@10.1.0.159:5060>;tag=b441f227ep
Call-ID: 357671f7-8721d7a9-65bcc1ec-7a3d17eb@10.1.0.159
CSeq: 1 REFER
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29728-a1e7700-d63ec0d
Refer-To: <sip:1001@10.1.0.159>
Referred-By: <sip:10.1.0.121:7030>
Max-Forwards: 70
Supported: replaces
Route: <sip:10.1.0.159:5060;lr>
Contact: <sip:10.1.0.121:7030>
Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, REFER, NOTIFY
Allow-Events: refer
Content-Length: 0
This is a successful REFER.
REFER sip:4031@10.1.0.159:5060 SIP/2.0
From: "4000"<sip:4000@10.1.0.159>;tag=67b2550-7900010a-1b76-50022-2997f-5d3797c9-2997f
To: "4031"<sip:4031@10.1.0.159:5060>;tag=bbd7fe4f7p
Call-ID: 3608be7b-7be1932e-19db9c47-e9842525@10.1.0.159
CSeq: 1 REFER
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29992-a27e5bb-4dfea27d
Refer-To: <sip:1001@10.1.0.159>
Referred-By: <sip:10.1.0.121:7030>
Max-Forwards: 70
Supported: replaces
Route: <sip:10.1.0.159:5060;lr>
Contact: <sip:10.1.0.121:7030>
Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, REFER, NOTIFY
Allow-Events: refer
Content-Length: 0
This is a failed REFER
REFER sip:4031@10.1.0.159:5060 SIP/2.0
From: <sip:4000@10.1.0.159:5060>;tag=67b20a0-7900010a-1b76-50022-29715-6aaa490e-29715
To: "4031"<sip:4031@10.1.0.159:5060>;tag=b441f227ep
Call-ID: 357671f7-8721d7a9-65bcc1ec-7a3d17eb@10.1.0.159
CSeq: 1 REFER
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29728-a1e7700-d63ec0d
Refer-To: <sip:1001@10.1.0.159>
Referred-By: <sip:10.1.0.121:7030>
Max-Forwards: 70
Supported: replaces
Route: <sip:10.1.0.159:5060;lr>
Contact: <sip:10.1.0.121:7030>
Allow: INVITE, CANCEL, ACK, BYE, OPTIONS, REFER, NOTIFY
Allow-Events: refer
Content-Length: 0
This is the 403 response packet
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29728-a1e7700-d63ec0d
From: <sip:734070@10.1.0.159:5060>;tag=67b20a0-7900010a-1b76-50022-29715-6aaa490e-29715
To: "4031"<sip:4031@10.1.0.159>;tag=b441f227ep
Call-ID: 357671f7-8721d7a9-65bcc1ec-7a3d17eb@10.1.0.159
CSeq: 1 REFER
Content-Length: 0
The reason for the 73 prefix on the 4070 'extension' number is because I have setup each user to divert to 73xxxx on no answer. I then have a dialplan that looks for the 73 prefix and patches the SIP header to provide my VMS with divert cpi. As far as I can tell this is something that the Brekeke IPPBX does not provide.
I have added 734070 as a UA (the test that I refered to above) and this has made no difference.
Below is the sucessful transfer response packet.
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29992-a27e5bb-4dfea27d
Record-Route: <sip:10.1.0.159:5060;lr>
From: "4000"<sip:4000@10.1.0.159>;tag=67b2550-7900010a-1b76-50022-2997f-5d3797c9-2997f
To: "4031"<sip:4031@10.1.0.159:5060>;tag=bbd7fe4f7p
Call-ID: 3608be7b-7be1932e-19db9c47-e9842525@10.1.0.159
CSeq: 1 REFER
Contact: <sip:4031@10.1.0.159:5060>
Content-Length: 0
Any help with this would be very much appreciated.
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29728-a1e7700-d63ec0d
From: <sip:734070@10.1.0.159:5060>;tag=67b20a0-7900010a-1b76-50022-29715-6aaa490e-29715
To: "4031"<sip:4031@10.1.0.159>;tag=b441f227ep
Call-ID: 357671f7-8721d7a9-65bcc1ec-7a3d17eb@10.1.0.159
CSeq: 1 REFER
Content-Length: 0
The reason for the 73 prefix on the 4070 'extension' number is because I have setup each user to divert to 73xxxx on no answer. I then have a dialplan that looks for the 73 prefix and patches the SIP header to provide my VMS with divert cpi. As far as I can tell this is something that the Brekeke IPPBX does not provide.
I have added 734070 as a UA (the test that I refered to above) and this has made no difference.
Below is the sucessful transfer response packet.
SIP/2.0 202 Accepted
Via: SIP/2.0/UDP 10.1.0.121:7030;branch=z9hG4bK-29992-a27e5bb-4dfea27d
Record-Route: <sip:10.1.0.159:5060;lr>
From: "4000"<sip:4000@10.1.0.159>;tag=67b2550-7900010a-1b76-50022-2997f-5d3797c9-2997f
To: "4031"<sip:4031@10.1.0.159:5060>;tag=bbd7fe4f7p
Call-ID: 3608be7b-7be1932e-19db9c47-e9842525@10.1.0.159
CSeq: 1 REFER
Contact: <sip:4031@10.1.0.159:5060>
Content-Length: 0
Any help with this would be very much appreciated.
This topic refers (pardon the pun) to the dial plan issue that I mentioned above.