How to force a specific billing or charged to number with SIP

csmith5660 · ‎05-15-2013

I have a customer who's SIP carrier (First Communications) is not using digest authentincation or SIP registration for their trunks. Because they have no method of authentication or identificaiton they bill calls based on the caller ID or the (billing/charged number). Because the CUBE gateway isn't populating the charged to field in the SIP message they currently use caller ID to identify the customer and bill them.

The problem with this is when forwarding calls, the customer would like the caller ID of a forwarded call to be the original calling party, but when the carrier recieves that call on the SIP trunk they reject it because the caller ID of the originating caller could be anything and odds are its not in their range. I spoke to the carrier tech and he asked if there is a way to set the charged to number in our SIP messages.

I've looked around and can't find anything, has anyone ever had to update this charged to or billing number before?

Thanks fo the help in advance.

paolo bevilacqua · ‎05-15-2013

Start mentioned system and version of everything you have in the call path.

Jonathan Schulenberg · ‎05-17-2013

What header is the carrier looking for then? Perhaps they can supply a sample INVITE with this "charge" header highlighted. CUBE can use a 'voice class sip-profiles' to add a header to an outgoing INVITE (request INVITE sip-header) but we would need to see what it should look like to provide a sample config.

http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a0080982499.shtml

Please remember to rate helpful responses and identify helpful or correct answers.

csmith5660 · ‎05-17-2013

CallManager is 8.6(2a)
The 2900 CUBE router is on a version of IOS 15. (I'll get the specific one later)
I'll reach out to the carrier and see if I can get some more details on what header they are looking for. I was hoping there was a simple command for this lol. Thanks for your help - I'll update this on Monday.

Sent from Cisco Technical Support iPhone App