07-18-2020 01:00 PM
Hello Guys,
I'm trying to make SIP REFER work on CUBE but no luck. What am I missing?
When CUBE receives the REFER message, it sends "SIP/2.0 400 Bad Request"
The goal is to get the CUBE to send an INVITE to the address in the REFER-TO header.
I do have the following commands on the inbound dial-peer:
-no supplementary-service sip refer
-refer consume
This is the REFER message received:
REFER sip:5167@10.154.25.50:5060 SIP/2.0
Via: SIP/2.0/UDP 10.140.175.244;rport;branch=z9hG4bKr2cKN3g0FS8Xp
Max-Forwards: 70
From: <sip:1418@10.140.175.244>;tag=aZ3mB0cXp7m0K
To: "Softnet." <sip:5167@10.154.25.50>;tag=C0AB0034-1EEA
Call-ID: 6E76D4A3-C85B11EA-8838EA6E-8E8920FA@10.154.25.50
CSeq: 22994694 REFER
Contact: <sip:1418@10.140.175.244:5060;transport=udp>
User-Agent: FreeSWITCH-mod_sofia/1.8.6~64bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Refer-To: <3711346@10.154.25.50>
Referred-By: <sip:10.140.175.244>
Content-Length: 0
X-Route: ad_reset
And CUBE responds with this:
SIP/2.0 400 Bad Request
Via: SIP/2.0/UDP 10.140.175.244;rport;branch=z9hG4bKr2cKN3g0FS8Xp
From: <sip:1418@10.140.175.244>;tag=aZ3mB0cXp7m0K
To: "Softnet" <sip:5167@10.154.25.50>;tag=C0AB0034-1EEA
Date: Sat, 18 Jul 2020 18:29:32 GMT
Call-ID: 6E76D4A3-C85B11EA-8838EA6E-8E8920FA@10.154.25.50
Server: Cisco-SIPGateway/IOS-15.4.3.M3
CSeq: 22994694 REFER
Content-Length: 0
Contact: <sip:5167@10.154.25.50:5060>
07-18-2020 03:22 PM
If memory serves, REFER handling is off by default. You need to enable it with supplementary-service sip refer.
07-18-2020 07:32 PM
07-19-2020 10:38 AM
07-20-2020 05:49 PM
07-24-2020 06:10 AM
By default CUBE will only consume the user/LHS of that URI and route it like any other numeric destination. The outbound dial-peer would need to be destination-pattern 3711346
If you really want to route the full URI you'll need to turn on requri-passing.
07-24-2020 09:38 PM
07-24-2020 09:46 PM
I have a dial-peer for 3711346, I'm not trying to use URI dialing. Here it is:
07-25-2020 06:05 AM
Yeah, I noticed the Request URI, FROM, To, and Cseq but I don’t spend enough time staring at REFERs to say that’s wrong.
What caught my eye however is the Refer-to header from your trace: the IPv4 address in the RHS is illegal. Is that legit what the trace contained or were you trying to mask/obscure some of the IPs?
Refer-To: <3711346@10.10.140.150.101>
07-25-2020 08:05 PM
Not sure what happened, probably when I was cleaning the file and removing other calls from the trace.
I just took a fresh new logs, it is attached.
When I bypass the CUBE and use a direct SIP trunk from CUCM, the SIP REFER works.
1 thing missing when using CUCM, it doesn't pass the custom header: X-Route: ad_reset
I'm looking into SIP Normalization script to copy the header from the SIP REFER and add it to the INVITE. Any idea how to make this work?
I appreciate all your help on this. Thank you
10-23-2021 09:19 PM
hello, may I know how you solve the issue?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide