Yes
Looks like sipX sends the itspusern...@itsp Address in the FROM header...

And PAID has the individual users User Id as follows use...@a.b.c.d (or 
1...@1.2.3.4 in my example below) where a.b.c.d is the IP of the sipX server 
itself.

I want PAID to look like use...@itsp-provider-address(Like in FROM header 
above) populated in the ITSP server address.

BW platform uses the whole sip URI in the PAID to determine individual users to 
identify individual SIP trunk users for billing...

Ideally ; I would like the contents of the FROM and PAID reversed - i.e. FROM 
header should have the individual use...@itsp-address and PAID should have the 
main Pilot usern...@itsp-address...


-----Original Message-----
From: Tony Graziano [mailto:tgrazi...@myitdepartment.net] 
Sent: Tuesday, August 10, 2010 5:19 PM
To: Ujjval Karihaloo; sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] P-Asserted ID

I'm guessing this is to capture detail for a billing platform running
on a switch?


On 8/10/10, Ujjval Karihaloo <ujj...@simplesignal.com> wrote:
> Can I send P-Assert-ID over the SIP trunk so that which ever extension is
> calling their username gets send over the user portion of u...@domain in the
> PAID.
> So that would mean wild carding the user portion of the PAID
> E.g.
>
> I have extention with username - 1234
>
> In the SIP Trunk ITSP setting under P_Asserted ID filed I send a customer
> one and do something like $usern...@mydommain.com
>
> So if 1234 make a outbound call over the SIP trunk, sipX sends PAID in the
> INVIT as following 1...@mydomain.com
>
>

-- 
Sent from my mobile device

======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.984.8431

Email: tgrazi...@myitdepartment.net

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: helpd...@voice.myitdepartment.net
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to