cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
841
Views
3
Helpful
5
Replies

How to manipulate FROM/Contact header in Blind transfer without "Refer-To" and "Referred-From"

I am in dire need of the SIP-histicated people on this forum manipulating the unknown eye closed

 

I hope for some guidance from the SIP output below, my challenge here is that I do not see a Refer-To or Referred-By header when the contact center agent does a Blind Transfer to an external caller. How do I know manipulate the FROM and Contact field with acceptable FROM and Contact information which they allow over their SIP trunk. 

So from the messages below 93569000 is allowed by the ISP to make calls, but now 93569000 does BLIND transfer and the FROM field changes to 92689000 which is an external number not authorized to make a call over the ISP SIP trunk.

What field or header do I look at to Copy and modify the FROM and Contact field in the blind transfer INVITE?

 

Contact center agent dialing out to external party: (SIP messages follow to show the initial call is successful)

 

Received:
INVITE sip:6492689000@10.37.83.10:5060;transport=tcp;user=phone SIP/2.0
To: "Someone" <sip:6492689000@10.37.83.10;user=phone>
From: "Agent101" <sip:93569000@10.37.250.130;user=phone>;tag=y920KUY
Call-ID: b09129ae-2708-49d9-9a87-15007fc63943
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK3687401649SU5JTi9pM3NpcC4t_179255335_
CSeq: 1 INVITE
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO
Supported: norefersub, timer
Accept: application/sdp, application/dtmf-relay
Contact: "Agent101" <sip:93569000@10.37.250.130:5060;transport=tcp>
x-inin-cnv: 06d1bbb7-1fd1-4905-b798-288c6e4e6098
Content-Type: application/sdp
User-Agent: ININ-EDGE/1.0.0.9458
Content-Length: 270

 

Sent:
INVITE sip:092689000@100.100.254.231:5060 SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA8E2523
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>
Date: Mon, 26 Oct 2020 23:48:57 GMT
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2781633750-0387715563-2973819607-2400695643
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1603756137
Contact: <sip:93569000;tgrp=12345678;trunk-context=isp.com@192.18.146.100:5060>
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-ID: 6427bf1d367557ffa55d20926c5f6bed;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 274

 

Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA8E2523
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
CSeq: 101 INVITE
Timestamp: 1603756137

ACK sip:092689000@100.100.254.231:5060 SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA8E2523
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>;tag=SDrp5dc99-346319880-1603756137354
Date: Mon, 26 Oct 2020 23:48:57 GMT
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: ;remote=
Content-Length: 0

 

Sent:
INVITE sip:092689000@100.100.254.231:5060 SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA8F2464
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>
Date: Mon, 26 Oct 2020 23:48:57 GMT
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2781633750-0387715563-2973819607-2400695643
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1603756137
Contact: <sip:93569000;tgrp=12345678;trunk-context=isp.com@192.18.146.100:5060>
Expires: 180
Allow-Events: telephone-event
Authorization: Digest username="12345678",realm="isp.com",uri="sip:092689000@100.100.254.231:5060",response="1589528b583c45a06e3db46adea04918",nonce="somethingelseXkgr6zvd6Txs3v1fBW",cnonce="C91883FB",qop=auth,algorithm=MD5,nc=00000001
Max-Forwards: 69
Session-ID: 6427bf1d367557ffa55d20926c5f6bed;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 274

 

Received:

SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA8F2464
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
CSeq: 102 INVITE
Timestamp: 1603756137

 

Received:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA8F2464
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>;tag=SDrp5dc99-980776216-1603756137951
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
CSeq: 102 INVITE
Timestamp: 1603756137
Supported:
Contact: <sip:092689000@100.100.254.231:5060;transport=udp>
Call-Info: <sip:122.56.252.6>;appearance-index=1
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY,UPDATE
Content-Length: 0

 

Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK3687401649SU5JTi9pM3NpcC4t_179255335_
From: "Agent101" <sip:93569000@10.37.250.130;user=phone>;tag=y920KUY
To: "Someone" <sip:6492689000@10.37.83.10;user=phone>;tag=94A44C94-D50
Date: Mon, 26 Oct 2020 23:48:57 GMT
Call-ID: b09129ae-2708-49d9-9a87-15007fc63943
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:092689000@10.37.83.10>
Contact: <sip:6492689000@10.37.83.10:5060;transport=tcp>
Server: Cisco-SIPGateway/IOS-15.7.3.M3
Session-ID: 297df0520e6a5ac9bf079ffbea10f0c2;remote=6427bf1d367557ffa55d20926c5f6bed
Content-Length: 0

 

Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA8F2464
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>;tag=SDrp5dc99-980776216-1603756137951
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
CSeq: 102 INVITE
Timestamp: 1603756137
Allow: ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Supported:
Contact: <sip:092689000@100.100.254.231:5060;transport=udp>
Call-Info: <sip:122.56.252.6>;appearance-index=1
Accept: application/media_control+xml,application/sdp
Content-Type: application/sdp
Content-Length: 201

 

Sent:
ACK sip:092689000@100.100.254.231:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA912641
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>;tag=SDrp5dc99-980776216-1603756137951
Date: Mon, 26 Oct 2020 23:48:57 GMT
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
Max-Forwards: 70
CSeq: 102 ACK
Authorization: Digest username="12345678",realm="isp.com",uri="sip:092689000@100.100.254.231:5060",response="1589528b583c45a06e3db46adea04918",nonce="somethingelseXkgr6zvd6Txs3v1fBW",cnonce="C91883FB",qop=auth,algorithm=MD5,nc=00000001
Allow-Events: telephone-event
Content-Length: 0

 

Sent:

SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK3687401649SU5JTi9pM3NpcC4t_179255335_
From: "Agent101" <sip:93569000@10.37.250.130;user=phone>;tag=y920KUY
To: "Someone" <sip:6492689000@10.37.83.10;user=phone>;tag=94A44C94-D50
Date: Mon, 26 Oct 2020 23:48:57 GMT
Call-ID: b09129ae-2708-49d9-9a87-15007fc63943
CSeq: 1 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
P-Asserted-Identity: <sip:092689000@10.37.83.10>
Contact: <sip:6492689000@10.37.83.10:5060;transport=tcp>
Supported: replaces
Supported: sdp-anat
Server: Cisco-SIPGateway/IOS-15.7.3.M3
Session-ID: 297df0520e6a5ac9bf079ffbea10f0c2;remote=6427bf1d367557ffa55d20926c5f6bed
Supported: timer
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 244

 

Received:
ACK sip:6492689000@10.37.83.10:5060;transport=tcp SIP/2.0
To: "Someone" <sip:6492689000@10.37.83.10;user=phone>;tag=94A44C94-D50
From: "Agent101" <sip:93569000@10.37.250.130;user=phone>;tag=y920KUY
CSeq: 1 ACK
Call-ID: b09129ae-2708-49d9-9a87-15007fc63943
Max-Forwards: 70
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK1846900043SU5JTi9pM3NpcC4t_179255335_
x-inin-cnv: 06d1bbb7-1fd1-4905-b798-288c6e4e6098
User-Agent: ININ-EDGE/1.0.0.9458
Content-Length: 0

 

Call is now answered between Agent101 and Someone


Now Agent101 attempts a blind transfer to AnotherSomeone, in other words the call will now be between 2 x external parties with the Agent101 leaving the call.

 

Received:
INVITE sip:64212219000@10.37.83.10:5060;transport=tcp;user=phone SIP/2.0
To: "AnotherSomeone" <sip:64212219000@10.37.83.10;user=phone>
From: "Someone" <sip:92689000@10.37.250.130;user=phone>;tag=T1CZbps <-- How to I change this to say 93569000 using wildcards
Call-ID: 56d87320-20d8-4e57-a800-5d2519152866
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK1882944755SU5JTi9pM3NpcC4t_179255336_
CSeq: 1 INVITE
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO
Supported: norefersub, timer
Accept: application/sdp, application/dtmf-relay
Contact: "Someone" <sip:92689000@10.37.250.130:5060;transport=tcp> <-- How to I change this to say 93569000 using wildcards
x-inin-cnv: 06d1bbb7-1fd1-4905-b798-288c6e4e6098
Content-Type: application/sdp
User-Agent: ININ-EDGE/1.0.0.9458
Content-Length: 270

 

Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK1882944755SU5JTi9pM3NpcC4t_179255336_
From: "Someone" <sip:92689000@10.37.250.130;user=phone>;tag=T1CZbps <-- How to I change this to say 93569000 using wildcards
To: "AnotherSomeone" <sip:64212219000@10.37.83.10;user=phone>
Date: Mon, 26 Oct 2020 23:49:22 GMT
Call-ID: 56d87320-20d8-4e57-a800-5d2519152866
CSeq: 1 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M3
Session-ID: 00000000000000000000000000000000;remote=5dedb117c2bf50408a97888d380776c8
Content-Length: 0

 

Sent:
INVITE sip:0212219000@100.100.254.231:5060 SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA92EDE
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3 <-- How to I change this to say 93569000 using wildcards
To: <sip:0212219000@100.100.254.231>
Date: Mon, 26 Oct 2020 23:49:22 GMT
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3038115653-0387715563-2974343895-2400695643
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1603756162
Contact: <sip:92689000;tgrp=12345678;trunk-context=isp.com@192.18.146.100:5060> <-- How to I change this to say 93569000 using wildcards
Expires: 180
Allow-Events: telephone-event
Max-Forwards: 69
Session-ID: 5dedb117c2bf50408a97888d380776c8;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 274

 

Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA92EDE
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3  <-- How to I change this to say 93569000 using wildcards
To: <sip:0212219000@100.100.254.231>
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
CSeq: 101 INVITE
Timestamp: 1603756162

 

Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA92EDE
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3
To: <sip:0212219000@100.100.254.231>;tag=SDr96jc99-429045001-1603756162991
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
CSeq: 101 INVITE
Timestamp: 1603756162
WWW-Authenticate: DIGEST qop="auth",nonce="somethingelseXkgr70f5bTh55be9BW",realm="isp.com",algorithm=MD5
Content-Length: 0

 

Sent:
ACK sip:0212219000@100.100.254.231:5060 SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA92EDE
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3
To: <sip:0212219000@100.100.254.231>;tag=SDr96jc99-429045001-1603756162991
Date: Mon, 26 Oct 2020 23:49:22 GMT
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Session-ID: ;remote=
Content-Length: 0

 

Sent:
INVITE sip:0212219000@100.100.254.231:5060 SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA931205
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3
To: <sip:0212219000@100.100.254.231>
Date: Mon, 26 Oct 2020 23:49:23 GMT
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 3038115653-0387715563-2974343895-2400695643
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M3
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1603756163
Contact: <sip:92689000;tgrp=12345678;trunk-context=isp.com@192.18.146.100:5060>
Expires: 180
Allow-Events: telephone-event
Authorization: Digest username="12345678",realm="isp.com",uri="sip:0212219000@100.100.254.231:5060",response="e8b94ef083f9a7a65c998ae9564cc3b8",nonce="BroadWorksXkgr70f5bTh55be9BW",cnonce="6DFB5499",qop=auth,algorithm=MD5,nc=00000001
Max-Forwards: 69
Session-ID: 5dedb117c2bf50408a97888d380776c8;remote=00000000000000000000000000000000
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 274

 

Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA931205
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3
To: <sip:0212219000@100.100.254.231>
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
CSeq: 102 INVITE
Timestamp: 1603756163

 

Received:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA931205
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3
To: <sip:0212219000@100.100.254.231>;tag=SDr96jc99-1076407700-1603756163030
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
CSeq: 102 INVITE
Timestamp: 1603756163
Content-Length: 0

 

Sent:
SIP/2.0 403 Forbidden
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK1882944755SU5JTi9pM3NpcC4t_179255336_
From: "Someone" <sip:92689000@10.37.250.130;user=phone>;tag=T1CZbps
To: "AnotherSomeone" <sip:64212219000@10.37.83.10;user=phone>;tag=94A4AE90-1A1
Date: Mon, 26 Oct 2020 23:49:22 GMT
Call-ID: 56d87320-20d8-4e57-a800-5d2519152866
CSeq: 1 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.7.3.M3
Reason: Q.850;cause=57
Session-ID: 00000000000000000000000000000000;remote=5dedb117c2bf50408a97888d380776c8
Content-Length: 0

 

Sent:
ACK sip:0212219000@100.100.254.231:5060 SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA931205
From: "Someone" <sip:92689000@192.18.146.100>;tag=94A4AE44-DC3
To: <sip:0212219000@100.100.254.231>;tag=SDr96jc99-1076407700-1603756163030
Date: Mon, 26 Oct 2020 23:49:23 GMT
Call-ID: B517CC56-171C11EB-B14EE2D7-8F17B55B@192.18.146.100
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0

 

Received:
ACK sip:64212219000@10.37.83.10:5060;transport=tcp;user=phone SIP/2.0
To: "AnotherSomeone" <sip:64212219000@10.37.83.10;user=phone>;tag=94A4AE90-1A1
From: "Someone" <sip:92689000@10.37.250.130;user=phone>;tag=T1CZbps
CSeq: 1 ACK
Call-ID: 56d87320-20d8-4e57-a800-5d2519152866
Max-Forwards: 70
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK1882944755SU5JTi9pM3NpcC4t_179255336_
User-Agent: ININ-EDGE/1.0.0.9458
Content-Length: 0

 

Received:
BYE sip:6492689000@10.37.83.10:5060;transport=tcp SIP/2.0
To: "Someone" <sip:6492689000@10.37.83.10;user=phone>;tag=94A44C94-D50
From: "Agent101" <sip:93569000@10.37.250.130;user=phone>;tag=y920KUY
Call-ID: b09129ae-2708-49d9-9a87-15007fc63943
Max-Forwards: 70
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK889605640SU5JTi9pM3NpcC4t_179255335_
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO
Supported: norefersub, timer
Accept: application/sdp, application/dtmf-relay
Reason: Q.850 ;cause=57 ;text=""
x-inin-cnv: 06d1bbb7-1fd1-4905-b798-288c6e4e6098
CSeq: 2 BYE
User-Agent: ININ-EDGE/1.0.0.9458
Content-Length: 0

 

Sent:
SIP/2.0 200 OK
Via: SIP/2.0/TCP 10.37.250.130:58822;branch=z9hG4bK889605640SU5JTi9pM3NpcC4t_179255335_
From: "Agent101" <sip:93569000@10.37.250.130;user=phone>;tag=y920KUY
To: "Someone" <sip:6492689000@10.37.83.10;user=phone>;tag=94A44C94-D50
Date: Mon, 26 Oct 2020 23:49:23 GMT
Call-ID: b09129ae-2708-49d9-9a87-15007fc63943
Server: Cisco-SIPGateway/IOS-15.7.3.M3
CSeq: 2 BYE
Reason: Q.850;cause=16
P-RTP-Stat: PS=1174,OS=187840,PR=1172,OR=187520,PL=0,JI=0,LA=0,DU=23
Session-ID: 297df0520e6a5ac9bf079ffbea10f0c2;remote=6427bf1d367557ffa55d20926c5f6bed
Content-Length: 0

 

Sent:
BYE sip:092689000@100.100.254.231:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA941E8C
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>;tag=SDrp5dc99-980776216-1603756137951
Date: Mon, 26 Oct 2020 23:48:57 GMT
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
User-Agent: Cisco-SIPGateway/IOS-15.7.3.M3
Max-Forwards: 70
Timestamp: 1603756163
CSeq: 103 BYE
Authorization: Digest username="12345678",realm="isp.com",uri="sip:092689000@100.100.254.231:5060;transport=udp",response="b0b8d953e3cbfb6358abdf456144612f",nonce="somethingelseXkgr6zvd6Txs3v1fBW",cnonce="H0815200",qop=auth,algorithm=MD5,nc=00000002
Reason: Q.850;cause=16
P-RTP-Stat: PS=1172,OS=187520,PR=1176,OR=188160,PL=0,JI=0,LA=0,DU=23
Session-ID: 6427bf1d367557ffa55d20926c5f6bed;remote=297df0520e6a5ac9bf079ffbea10f0c2
Content-Length: 0

 

Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.18.146.100:5060;branch=z9hG4bK31FA941E8C
From: "Agent101" <sip:93569000@192.18.146.100>;tag=94A44A14-197C
To: <sip:092689000@100.100.254.231>;tag=SDrp5dc99-980776216-1603756137951
Call-ID: A5CE314D-171C11EB-B146E2D7-8F17B55B@192.18.146.100
Timestamp: 1603756163
CSeq: 103 BYE
Content-Length: 0

 

Best Regards
5 Replies 5

Vinh Nguyen
Beginner
Beginner

Hi

 

Did you get answer to this?  I have exactly same issue

Copy the From field on the inbound dial peer and use the content of it to make the needed adjustments to the fields in the outbound direction. These documents should help you along the way. SIP Profiles on CUBE Enterprise Common Use Cases In Depth Explanation of Cisco IOS and IOS-XE Call Routing 



Response Signature


b.winter
VIP
VIP

Edit: This post was meant for @Vinh Nguyen

Most providers I have worked with use a different header to authenticate calls, where the FROM number is not one of your DID range. Another example would be when an external calls a phone, which has forward back to external.
Normally then, providers use the PAI or PPI header to authenticate the call. The header should include one of your DID number.

rule 1 request INVITE sip-header P-Asserted-Identity modify "(<sip:).*(@.*)" "\1<DID-number>\2"

In the SIP Trunk on CUCM, you need to check the PAI header.

Unbenanntes Bild.png

And on the router:
voice service voip
 sip
  asserted-id pai

But if you want to be sure, how the provider handles such scenarios, you have to ask them.

We ended up manually manipulating the SIP headers with a pilot number for the contact center that is accepted by the ITSP over the SIP trunk.

I know it is not the cleanest way to do it, but it solved the issue for us at that stage as it came from the same pilot number on the call queue.

voice class sip-profiles 3
request INVITE sip-header P-Asserted-Identity modify "<sip:(.*)@(.*)>" "<sip:93569000@192.18.146.46>"
request INVITE sip-header Diversion modify "<sip:(.*)@(.*)>" "<sip:93569000@192.18.146.46>"
request INVITE sip-header From modify "<sip:(.....)@(.*)>" "<sip:93569000@192.18.146.46>"
request INVITE sip-header Contact modify "<sip:(.*)>" "<sip:93569000@192.18.146.46>"
request INVITE sip-header From modify "\"Anonymous\" <sip:(.*)@(.*)>" "\"93569000\" <sip:93569000@192.18.146.46>"
request INVITE sip-header From modify "\"anonymous\" <sip:anonymous@(.*)>" "\"93569000\" <sip:93569000@192.18.146.46>"
request INVITE sip-header From modify "<sip:\+xx(.*)@(.*)>" "<sip:0\1@192.18.146.46>"
request INVITE sdp-header Session-Owner modify "IP4 172.24.*" "IP4 192.18.146.46"

And this was assigned to the outbound dial-peer towards the ITSP.

I will how ever for future ref maybe look a the suggestion from Roger to copy the inbound dial-peer headers and use it on the transfer call. This is how ever not a need for us anymore. Just came across this post and thought I would give my 5 cents, maybe it can help someone else out there maybe not.

Best Regards

Hi,
probably the first rule in your sip-profile is already enough to please the provider.

As described in my other message, it is completely normal and a valid scenario, that the FROM header doesn't contain a number assigned to your number range.
As described, most providers first check the number in the FROM header. If it's a DID range number --> OK
If not, then they check if a PAI, PPI, or also sometimes if Diversion header is present. And normally one of those, you assign a DID range number.

The rule in my other message is my "default" rule, to assign all outgoing INVITEs a PAI (or PPI) header with one DID range number.
So I don't have to care about copying numbers between dial-peers or don't care about the numbers in the FROM header (as long as they have the correct number format).

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: