- Joined
- Sep 22, 2020
- Messages
- 44
- Reaction score
- 3
Hi,
We are using BT Wholesale SIP (BT HSIPT) trying to get CLI passthrough working for calls forwarded to mobile/external number. I have read the numerous threads about this subject but have not found anything relating specifically to this SIP provider.
To confirm:
From : Display Name
From : User Part
Remote Party ID - Calling Party : User Part
P-Asserted Identity : User Part
The above have been tried in every possible configuration.. The result is that all calls to the SIP will fail
So I sent a pcap to BT who responded with the following
Unfortunately this is beyond the scope of my knowledge or understanding.
Can anyone advise or have experience with this provider?
We are using BT Wholesale SIP (BT HSIPT) trying to get CLI passthrough working for calls forwarded to mobile/external number. I have read the numerous threads about this subject but have not found anything relating specifically to this SIP provider.
To confirm:
- Clip no screening is supported
- CLI passthrough is supported and enabled on the trunk
- I have tried changing the various outbound parameters to "OriginatorCallerID"
From : Display Name
From : User Part
Remote Party ID - Calling Party : User Part
P-Asserted Identity : User Part
The above have been tried in every possible configuration.. The result is that all calls to the SIP will fail
So I sent a pcap to BT who responded with the following
having retraced the call I can see that you are getting a 404 user not found due to the PBX not be configured correctly. directly in relation to the number in the "Display Info part" of the PAI header. To: From: "number_redacted";tag=b78c3b0d Call-ID: HreSYSk1pfRf9LbfLsGCCQ.. CSeq: 1 INVITE Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE Content-Type: application/sdp Supported: replaces, timer User-Agent: 3CXPhoneSystem 18.0.3.461 (461) P-Asserted-Identity: "44number_redacted" Remote-Party-ID: ;party=calling Content-Length: 314 it needed to go in the actual user part, i.e. the bit before the @ sign this is causing the rooting problems you describe. what you are requesting is a level 4 CLI and our platform supports a level 5 CLI pass through. for further configuration support on the PBX you should consult your provider
Unfortunately this is beyond the scope of my knowledge or understanding.
Can anyone advise or have experience with this provider?
Last edited: