P-Asserted-Identity of Callee ID on A leg? (in 183 packet)

Status
Not open for further replies.

djzort

Member
Feb 28, 2018
76
5
8
41
Sydney, Australia
bytefoundry.com.au
setting sip_cid_type=pid and/or caller-id-type=pid seems to only affect the B-leg (the person being called i.e. the callee)

the A leg seems to always receive remote-party-id in 183 responses. the above two settings seem to have no impact. The sip_cid_in_1xx variable turns remote-party-id off/on in the 183, but its still rpid not pid.

any suggestions on how a P-Asserted-Identity (pid) might be provided to the A leg (caller)
 

djzort

Member
Feb 28, 2018
76
5
8
41
Sydney, Australia
bytefoundry.com.au
My expectation was that setting sip_cid_type=pid and/or caller-id-type=pid - would impact both A and B leg. Thats not the case.

Also sip_cid_in_1xx is entirely independant of the above.

On reflection is probably for the best that they only impact on leg, as you may have different handsets, so different requirements, on either leg.

The downside is that this isnt well documented (rather, isnt at all documented) and that generally speaking these control variables probably arent subtle enough.
 
Status
Not open for further replies.