If your DialPlan rule works correctly, you can see "Diversion" header in a SIP packet which sent from the SIP Server. According to the export from the Wireshark trace I do get the Diversion header INVITE sip:4000@10.1.0.121:7030 SIP/2.0 Via: SIP/2.0/UDP 10.1.0.159:5060;rport;branch ...

Can you paste related DailPlan rules here? My dialplan is in my first post, but here it is again :) Matching Pattern $port=15062 $localhost=true $registered=false $outbound=false $request=^INVITE $getUri(From)=!_ocs To=sip:73(.{4}) Deploy Pattern $transport=udp $auth=false &net.sip.transport.follow ...

OK to clarify IP addresses. 10.1.0.159 is the Brekeke PBX/SIP Server 10.1.0.121 is the VoIP VMS The VMS is registered in the PBX with extension 4000. The dial plan is there to provide the VMS with what is effectively "divert CPI" or in a VoIP world a Diversion field in the SIP header. The Brekeke ...

Because you are using original SIP application, I have no idea about it ... Ask Brekeke to analyze a packets trace. I've tried with the "tag%1" removed but it has made no difference. :( What do you mean by "original SIP application"? I would ask Brekeke to look at the packets, but I suspect that ...

It seems 10.1.0.121 sent REFER. Is it your application too? Yes. 121 is my VMS, 159 is the Brekeke PBX/SIP Server. And, Your DialPlan seems wrong... >> To=sip:4000@10.1.0.159;tag=%1 Why do you need to replace "tag"? I will remove that and test again. I can find very little useful documentation on ...

Which version of Brekeke PBX are you using? Are you using OCS with it? Brekeke PBX, Version 2.2.6.2 , Pro Evaluation. No not using OCS. Using Brekeke PBX and SIP server. Thats it. All phones and VMS 'hook up' to that. Because you are a developer, ask Brekeke to check the packet trace. Does that ...

1. Brekeke Product Name and version: Brekeke PBX and SIP server, Version 2.2.6.2 , Pro Evaluation. 2. Java version: 1.6.0_11 3. OS type and the version: Windows XP 4. UA (phone), gateway or other hardware/software involved: X-Lite and Linksys SPA942 5. Select your network pattern from http://www ...

This topic refers (pardon the pun) to the dial plan issue that I mentioned above.

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 ...

taitan wrote:Can you paste both 202 and 403 response packets here?
I want to look at them.

Sorry for slow response. I have just had the chance to look more closely at my response packets and I think I have seen the problem.

I'll do some more testing and get back to you.

Thanks for your time so far

taitan wrote:who sent REFER request?
and who sent 403 response?

In both sucess and failure examples the REFER is sent by the VMS and the response (either 202 or 403) comes back from Brekeke.

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. 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 ...

Solved the issue. I needed to prefix each extension's forward to for busy and no answer. For example extension 4025 would need to forward on busy or no answer to 734025. Then the Dialplan would pick out "73" as the prefix and insert the Diversion header as 4025. One thing to note is that for ...

1. Brekeke Product Name and version: Brekeke PBX, Version 2.2.6.2 , Pro Evaluation and Brekeke SIP Server for Brekeke PBX, Version 2.2.6.2 2. Java version:Ver 6 Update 11 3. OS type and the version: Windows XP Service pack 3 4. UA (phone), gateway or other hardware/software involved: x-lite version ...