[Users] openser and History-Info (RFC 4244) for VM/UM application

[john hess]

hi Bogdan,

i will first see what i can do within the script using the 
textops-exported functions.  failing that, do you sense there would be 
wider interest in having the openser parser include support for HI hdrs? 

thanks,

john

Bogdan-Andrei Iancu wrote:
> Hi John,
>
> there is no such support in openser as nobody found any need for it :).
>
> you can try doing the translation between HI and Diversion hdrs 
> directly from script via reg exp  (if the differences as body are 
> minor). Other options will be to write your one module to do this 
> translation.
>
> regards,
> bogdan
>
> john hess wrote:
>
>> hi,
>>
>> does anyone have experience in using openser in processing 
>> call-forwarding/redirection signaled in the History-Info section (as 
>> per RFC 4244)?
>> the application context is openser as a means to interpolate 
>> signaling between an IP PBX and a SIP-speaking VM/UM platform (I^3 
>> Communite -- v2.3.1).  the problem i am trying to solve (at least in 
>> the near-term) is that the Avaya is using History-Info to signal 
>> call-forwarding events (ex: CFNA, CFB) while Communite is expecting 
>> call-forwarding to be signaled via Diversion.  until the platforms 
>> support have a call-forwarding signaling method in common, i would 
>> like to be able to insert openser into the signaling path -- more or 
>> less as a translator between the two platforms.
>>
>> tia,
>>
>> john
>>
>> john hess <jhess at berkeley.edu>
>> nocman
>> ist, uc berkeley
>> 510 643-6401
>>
>> _______________________________________________
>> Users mailing list
>> Users at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/users
>>
>
>