Mark, Thanks -- the receiving device is a Genband C15, which we're chasing down. Frank -----Original Message----- From: Mark Lindsey [mailto:lindsey at e-c-group.com] Sent: Tuesday, October 04, 2016 8:58 AM To: frnkblk at iname.com Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] Adding CIC on Acme SBC Yes, but doing so depends on the receiving device caring about your concept of carrier. There are several ways this is commonly done in the signaling; in the Acme Packet SBC, you'd use a sip-manipulation rule to modify the Request URI. So INVITE sip:12293160013 at 4.1.2.3;user=phone SIP/2.0 might need to become RFC4694... INVITE sip:12293160013;cic=0123 at 4.1.2.3;user=phone SIP/2.0 (Dialogic has a nice page about this: http://www.dialogic.com/webhelp/img1010/10.3.3er2/webhelp/Description/Interw orking/SIP_Carrier_Identification_Code.htm) or... INVITE sip:12293160013;cic=0123;csel=sub at 4.1.2.3;user=phone SIP/2.0 or, also not uncommon if the call is going into a US-based telephone switch configured for carrier-equal-access dialing: INVITE sip:101023412293160013 at 4.1.2.3;user=phone SIP/2.0 or, even, INVITE sip:12293160013 at 4.1.2.3;user=phone;dtg=0123 SIP/2.0 ...when the dtg URI parameter is mapped to a carrier. It really depends on what the receiving device can interpret. Mark R Lindsey, SMTS +1-229-316-0013 mark at ecg.co http://ecg.co/lindsey/

On Oct 4, 2016, at 09:39 , frnkblk at iname.com wrote:

Is it possible to add a CIC code to an outgoing call on an Acme SBC?

Frank

_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops