TB30s SIP Administrator Guide v1.3 Page 140 of 259
Comverse: Redirecting identity and name presentation
Currently, the TB30 do not support the "display-name" string of the
Diversion header.
With working in Comverse environment, the feature of redirecting identity
and name presentation allows its displays on the terminating phone. And the
redirecting identity and name information is received on the initial INVITE
request.
Therefore, this section is to address the implementation of the redirecting
identity in TB30.
Let see the below example:
A (calling): 84000532 "Alice"
B (redirecting): 81000541 "Bob the Manager"
C (called): 84000531 "Assistant"
For a basic incoming call, TB30 will receive the following SIP INVITE
message:
Initial INVITE from NETWORK received by C:
There are three states need to be considered:
INVITE sip:84000531@10.165.2.31:5060 SIP/2.0
Via: SIP/2.0/UDP 10.165.2.200:5060;branch=z9hG4bK4901036f-6756-5198
Call-Id: CI_375_84000531_120
From: "Alice" <sip:84000532@10.165.2.200:5060>;tag=10.165.2.200-6745-8537
To: <sip:84000531@10.165.2.31:5060>
Max-Forwards: 70
Allow: REGISTER, INVITE, BYE, ACK, CANCEL, REFER, INFO, OPTIONS, SUBSCRIBE
Session-Expires: 120
CSeq: 375 INVITE
Contact: <sip:84000532@10.165.2.200:5060>
Supported: timer
Diversion: "Bob the Manager" <sip:81000541@10.165.2.200:5060>
Content-Type: application/sdp
Content-Length: 217
SDP
To Next Page
Loading...
Need help?
General