Can Brekeke modify the contents of a REFER?

Discuss any topic about Brekeke SIP Server.

Moderator: Brekeke Support Team

Post Reply
lperezu
Posts: 26
Joined: Mon Aug 19, 2013 10:44 am
Location: Lima

Can Brekeke modify the contents of a REFER?

Post by lperezu »

1. Brekeke Product Name and Version: 3.2.4.3/367

2. Java version: 1.7.0_25

3. OS type and the version: Linux

4. UA (phone), gateway or other hardware/software involved:

5. Your problem:

Can Brekeke modify the contents of a REFER?
I Need Alter the Header Refer-to like this:


Refer-To: <sip:45901@192.168.20.3>

to

Refer-To: <sip:45901@192.168.20.3?Add_a_String>
Tata
Posts: 223
Joined: Sun Jan 27, 2008 1:03 pm

Post by Tata »

Is it a REFER sent in a dialog created with an INVITE?
lperezu
Posts: 26
Joined: Mon Aug 19, 2013 10:44 am
Location: Lima

Post by lperezu »

Yes.
davi
Posts: 34
Joined: Wed Jan 26, 2011 4:34 pm

Post by davi »

Add the following in the [Configuration]->[Advanced] page once, and restart the SIP Server.

Code: Select all

&net.sip.outside.dialog.pattern = ^REFER|^NOTIFY 
Now you can catch REFER with DialPlan even if it is sent in existing dialog.
Let you write DialPlan rule to catch REFER and modify it as you want.
epascual
Posts: 22
Joined: Thu Sep 03, 2015 2:31 am
Location: Spain

Post by epascual »

Now I have the same problem but this solution does not work. Do I need to do anything else?
Haddas
Posts: 170
Joined: Thu Jan 17, 2008 11:55 am

Post by Haddas »

Does REFER share same Call-ID with INVITE?
epascual
Posts: 22
Joined: Thu Sep 03, 2015 2:31 am
Location: Spain

Post by epascual »

Yes.
This is the INVITE

INVITE sip:314006@192.168.1.206:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.4:5060;branch=z9hG4bK1e3cdc3befa6-30-17c7e5
From: "314035" <sip:314035@192.168.1.4>;tag=b3b821584p
To: <sip:314006@192.168.1.4>
Max-Forwards: 18
Contact: <sip:314035@192.168.1.4:5060>
Call-ID: b40aef08-63ff4164-52318c58-6b2461f
User-Agent: Brekeke PBX
CSeq: 1 INVITE
Allow: INVITE,ACK,BYE,CANCEL,INFO,MESSAGE,REFER,NOTIFY,SUBSCRIBE,UPDATE,PRACK
Subject: DA/IDA call
Priority: non-urgent
Content-Type: application/sdp
Content-Length: 141

v=0
o=bk 914 1 IN IP4 192.168.1.4
s=-
c=IN IP4 192.168.1.4
t=0 0
m=audio 30110 RTP/AVP 0
a=sendrecv
a=rtpmap:0 PCMU/8000
a=ptime:20

This is REFER

REFER sip:314035@192.168.1.4:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.206:5060;rport;branch=z9hG4bKPj0976bf2ab5d74cf28d424081063cb468
Max-Forwards: 19
From: <sip:314006@192.168.1.4>;tag=683869a866f54f4896a3ba79041ee27f
To: "314035" <sip:314035@192.168.1.4>;tag=b3b821584p
Contact: <sip:314006@192.168.1.206:5060>
Call-ID: b40aef08-63ff4164-52318c58-6b2461f
CSeq: 15351 REFER
Event: refer
Expires: 600
Accept: message/sipfrag;version=2.0
Allow-Events: presence, message-summary, refer, conference
Refer-To: <sip:314004@192.168.1.204?Require=replaces&Replaces=3519d734a73b4f8e91d10d9fe67e2f1a%3Bto-tag%3Ddb53012c28d34f4e9045cfc953fc4221%3Bfrom-tag%3D7fba56d3304e4d63bb25bfeb517655a1>
Referred-By: <sip:314006@192.168.1.4>
User-Agent: U5K-UA/1.0.0
Content-Length: 0
Post Reply