[sr-dev] Migration of Open IMS Core to sip-router

[Dragos Vingarzan]

Thanx for the tip! This would work then just fine and move everything to 
the script to do then the actual message modifications. But you know, I 
don't play well with AVPs and would rather write the module code ;-).

Cheers,
-Dragos


Klaus Darilion wrote:
>
>>      >  * enum - support for query on the originating side, useful in 
>> PSTN
>>      >    inbound processing
>>
>>     Could you send this patch to the mailing list and cc Juha?
>>
>>  Attached.... but... this is one of our crazy-experimental stuff. I 
>> mean I haven't yet figured it our what to do with multiple response 
>> or what is the final list of things to change in the message, so it 
>> looks a bit messy to be merged in the master now.
>>
>> As a bit of background info, this thing is useful when you have some 
>> sort of PSTN access gateway that would proxy all calls towards a SIP 
>> network. The node in charge of deciding the what-next part is called 
>> in IMS related terminology a TRansit Control Function (TRC or TRCF) 
>> and I have also attached a sample cfg for such a node. The advantage 
>> of doing also enum_orig() is that this node can decide, based on ENUM 
>> configuration, whether to trigger or not an originating leg 
>> processing in an originating domain proxy. Or putting it in another 
>> way, this provides the glue to have originating SIP services for PSTN 
>> UEs.
>
>
> If you just want to make ENUM lookups on the caller's number you can 
> also use K's enum module:
> http://www.kamailio.org/docs/modules/1.5.x/enum.html#id2467740
>
> It is very flexible and allows you to make ENUM lookup with a pseudo 
> variable - which can be anything.
>
> regards
> klaus
>


-- 
Best Regards,
Dragos Vingarzan