| Author |
Message |
lperezu
Brekeke Addict
Joined: 19 Aug 2013
Posts: 26
Location: Lima
|
 Posted: Thu Dec 26, 2013 11:24 am Post subject: Can Brekeke modify the contents of a REFER? |
 |
|
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> |
|
| Back to top |
|
Tata
Brekeke Master Guru
Joined: 27 Jan 2008
Posts: 223
|
| Posted: Thu Dec 26, 2013 5:38 pm Post subject: |
|
|
| Is it a REFER sent in a dialog created with an INVITE? |
|
| Back to top |
|
lperezu
Brekeke Addict
Joined: 19 Aug 2013
Posts: 26
Location: Lima
|
| Posted: Fri Dec 27, 2013 12:29 pm Post subject: |
|
|
| Yes. |
|
| Back to top |
|
davi
Brekeke Addict
Joined: 26 Jan 2011
Posts: 34
|
| Posted: Fri Dec 27, 2013 6:53 pm Post subject: |
|
|
Add the following in the [Configuration]->[Advanced] page once, and restart the SIP Server.
| Code: |
| &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. |
|
| Back to top |
|
epascual
Brekeke Member
Joined: 03 Sep 2015
Posts: 22
Location: Spain
|
| Posted: Mon Sep 21, 2015 4:41 am Post subject: |
|
|
| Now I have the same problem but this solution does not work. Do I need to do anything else? |
|
| Back to top |
|
Haddas
Brekeke Guru
Joined: 17 Jan 2008
Posts: 170
|
| Posted: Mon Sep 21, 2015 11:11 am Post subject: |
|
|
| Does REFER share same Call-ID with INVITE? |
|
| Back to top |
|
epascual
Brekeke Member
Joined: 03 Sep 2015
Posts: 22
Location: Spain
|
| Posted: Tue Sep 22, 2015 3:28 am Post subject: |
|
|
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 |
|
| Back to top |
|
|
