Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

PhonePower.com SIP - Diversion Headers - Twinned Call - Caller ID

Status
Not open for further replies.

dmaderi1

MIS
Jan 11, 2012
25
US
I was wondering if anyone has had any success using diversion headers with phonepower.com to display the originating caller-id for a twinned call? Or has anyone had any luck with other internet based SIP providers and diversion headers for twinned calls? I'm am not extremely attached to phonepower, so if someone else has a provider they've been happy with, I would like to know!
Thanks!
 
have you turned off "Send original calling party information for Mobile Twinning" in the System / Twinning TAB?

This needs to be off when using Diversion header in the SIP Line feature to send caller ID.

ACSS - SME
General Geek



1832163.png
 
I did, and that's a great tip because I've seen a lot of people miss that! I have verified that I can see it in the SIP trace. This is from the trace, minus the #'s :

Diversion: "Cell Phone NY" <sip:315380####@208.64.##.##:5060>;reason=unknown

 
It is, I have 1 trunk with them and 10 channels.
 
OK, would need to see more of a trace from the inbound call to the twinned call. Not all vendors have this feature on - perhaps they are overriding it with your lead number?

ACSS - SME
General Geek



1832163.png
 
Thanks, even though they said including the diversion header should work they still only show the FROM: address as the CID. When I show them the trace they complain about 2 things. 1) The number on the diversion header is not a number associate with my SIP trunk (of course not it is the originating party CID, the FROM: is a number associated with the trunk 2) the reason is "unknown"
 
INVITE sip:4122478@208.64.8.13 SIP/2.0
Via: SIP/2.0/UDP 208.105.xxx.xxx:5060;rport;branch=z9hG4bKfb0524076fdeb5c09fc81a3c6baed37e
From: "315214xxxx" <sip:315214xxxx@208.64.xx.xx>;tag=33545ad141346254
To: <sip:412xxxx@208.64.xx.xx>
Call-ID: d8f60e48e6957b3310788d3192ef31b8@208.105.xxx.xxx
CSeq: 1967141805 INVITE
Contact: "315214xxxx" <sip:315214xxxx@208.105.xxx.xxx:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Content-Type: application/sdp
Supported: timer
Diversion: "Cell Phone NY" <sip:315380xxxx@208.64.xx.xx:5060>;reason=unknown
Content-Length: 210

v=0
o=UserA 1919903843 1214720867 IN IP4 208.105.xxx.xxx
s=Session SDP
c=IN IP4 208.105.xxx.xxx
t=0 0
m=audio 49160 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
 
So maybe this helps, but I am not sure if the IP office if capable of doing what they are requesting. From phonepower tech support:

A proper call with the behavior you are trying for would include a diversion header including a valid reason and a number you have with us, and would have an RPID or PAI header including the original calling number that you are trying to have displayed to the recipient of the call an it too would have a valid reason. I have included a sample below. A call sent with the correct format will behave like you ask, but it must meet the requirements. Please consult your user manual for those requirements if they are not outlined in our discussion so far. Thanks.


Remote-Party-ID: "<<Calling Number Here>>" <sip:<<Original Calling Number Here>>@192.168.22.50>;privacy=off;screen=yes
Diversion: "Cell Phone NY" <sip:<<DID on your trunk>>@208.64.8.13:5060>;reason=unconditional;privacy=off;screen=yes
 
I do this with nexVortex. Some problems can be the terminating carrier and some can be the SIP trunk provider. With nexVortex the settings that work for me are:

Send original calling party information for Mobile Twinning - off
Send Caller ID - Diversion Header
Outbound Trunk SIP URI - PAI - none
Outbound Trunk registration is set.

According to nV if you set the PAI many cell carriers will use that as the Caller ID info.

Steve

 
I know this thread is a little stale, but I wanted to update it in case someone is searching for an answer. I do have this resolved with PhonePower.com. I upgraded the firmware on the IP 500 V2 to 7.0 (36) and it changed the diversion header reason from unknown to direct. This allows the caller ID to flow through to the cell phone when twinning.

Before Upgrade (not working):
Diversion: "Cell Phone NY" <sip:315380xxxx@208.64.xx.xx:5060>;reason=unknown

After Upgrade (working):
Diversion: "Cell Phone NY" <sip:315380xxxx@208.64.xx.xx:5060>;reason=direct

So as a review:

Line -> SIP Line tab
Send Caller ID = Diversion Header
System -> Twinning tab
Send originating calling party information is left unchecked
Calling party information is left blank

User -> Each user SIP tab
The appropriate Name/Alias/Contact info is populated
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top