cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2071
Views
0
Helpful
1
Replies

How to rewrite SIP header containing 603 decline in CUBE

tony loktu
Level 1
Level 1

Hi all

 

I have an issue with a device sending "603 decline" when it rejects an incoming call. This works just fine as long as its an internal call but when the call originates from PSTN then it just dont work.

Since i'm not sure if its CUBE or TSP that dont handle the "603 decline" I thought i might try rewriting the SIP header.

 

What i'm trying is to rewrite the header when a "603 decline" comes in i want it rewriten to "cancel 487 request canceled"

Here is my attempt:

response 603 method CANCEL sip-header SIP-StatusLine modify ", UPDATE" "487 request canceled"

This is my first attempt so i might have misunderstood the whole syntax.

Yes, I know the last thing that happens on a dial-peer is the rewrite and its only outgoing.

 

CUCM 11,5

CUBE 4451 IOS XE Version 16.3.8

 

My reference is:

 

https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-border-element/105624-cube-sip-normalization.html

And here it says:

"The SIP message type cannot be changed with SIP profiles.That is, a 180 Ringing response cannot be changed to a 183 Session Progress response."

Does this mean its not possible to achieve what i want?

 

Im using this for testing:

https://cway.cisco.com/tools/SipProfileTest/

1 Reply 1

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

On the face of it, this does not look like what you should be doing and may not work. A 6XX is a global failure, a 4XX is a user/client failure/ response. I dont see how this will work. A SIP profile does not rewrite the Method but headers within the SIP method.

Secondly, You should be able to tel easily who is not handling the 603 from your SIP traces. 

Please post snapshot of your traces here. Lastly what issue is this causing?

Please rate all useful posts