[cisco-voip] SIP: route incoming INVITE on To header?

[Mark Holloway]

Cool, I'll give it a shot. I just loaded 15.1(3)T 

> Mark,
> 
> A colleague here offers:
> <quote>
> Sure can.  You need 15.1(3)T and you can do conditional SIP normalization:
> 
> http://www.cisco.com/en/US/docs/ios/voice/cube/configuration/guide/vb-gw-sipsip.html#wp1462605
> 
> Here is a sample that takes the number in the diversion header and puts it in the request URI:
> 
> voice class sip-profiles 100
>  request INVITE sip-header Diversion copy "<sip:(.*)@.*>;" u01
>  request INVITE sip-header To modify "(.*)" "To: <sip:\u01 at 192.168.3.3:5060>"
> </quote>
> 
> Regards,
> Wes
> 
> On 3/22/2011 1:47 PM, Mark Holloway wrote:
>> Unfortunately I can't find a way to extract the information from the To header and add it to the Request URI.  It looks like SIP Profiles allows you to add or modify an existing header, but I do not see a way to use a variable of one header to assign to another.
>> 
>> On Mar 21, 2011, at 12:03 PM, Wes Sisk wrote:
>> 
>>> Would SIP normalization also work for this?
>>> http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a0080982499.shtml
>>> 
>>> Regards,
>>> Wes
>>> 
>>> On 3/21/2011 1:23 PM, Sinisa Djokic wrote:
>>>> yup..
>>>> 
>>>> you could use tcl script on incoming dial-peer to pull content of TO header and based on that create an outgoing call leg to whatever you need ( CUCM or something else )..
>>>> 
>>>> 
>>>> regards..
>>>> 
>>>> Sinisa Djokic
>>>> System Engineer
>>>> CCIE #25996 Voice
>>>> 
>>>> 
>>>> 
>>>> MDS Informaticki inzenjering
>>>> Bul. Milutina Milankovica 7d
>>>> 11070 Novi Beograd, Serbia
>>>> Tel:  +381 11 2015 200  +381 11 2015 200 , 2015 273
>>>> Fax: +381 11 3194 954
>>>> www.mds.rs
>>>> sdjokic at mds.rs
>>>> Please kindly consider the environment before printing this e-mail and any attachments
>>>> Ova e-mail poruka i bilo koji njeni dodaci namenjeni su isključivo imenovanom primaocu. Može sadržati poverljive informacije koje mogu biti zaštićene čuvanjem poslovne tajne. Ukoliko niste imenovani primaoc (ili ovlašćeni u ime primaoca), ne smete kopirati ili koristiti ovu poruku ili bilo koji dodatak poruci te otkriti sadržaj poruke bilo kome drugome. U slučaju da Vam je ovaj e-mail poslan greškom, molimo da odmah obavestite pošiljaoca i izbrišete ovaj e-mail.
>>>> This e-mail message and any attachment are intended exclusively for the named addressee. They may contain confidential information which may also be protected by professional secrecy. Unless you are the named addressee (or authorised to receive for the addressee) you may not copy or use this message or any attachment or disclose the contents to anyone else. If this e-mail was sent to you by mistake please notify the sender immediately and delete this e-mail.
>>>> 
>>>> 
>>>> -----Original Message-----
>>>> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Mark Holloway
>>>> Sent: Monday, March 21, 2011 6:04 PM
>>>> To: Cisco VOIP
>>>> Subject: [cisco-voip] SIP: route incoming INVITE on To header?
>>>> 
>>>> 
>>>> I've got CUBE registered via a SIP Trunk to a SIP registrar.  When a call (INVITE) comes from the SIP registrar towards CUBE, the request URI from the registrar is the main trunking number which is different than the number in the To header.   For example, if my main Pilot number is 4805551000 (same number used in sip-ua credentials and authentication) but CUCM's DN block is 4805551000 - 1099, and a call comes in from the registrar destined for 4805551009, the INVITE request-uri from the registrar contain 4805551000 but the To header contains 4805551009.  Is there a way to force CUBE to route incoming INVITES based on the To header instead of the request-uri?  Normally on the Service Provider side the SBC would re-write to request-uri to match the To header (for sip connect) but in my case I don't have an SBC in the network.
>>>> 
>>>> 
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> cisco-voip mailing list
>>>> cisco-voip at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-voip