daniel, i have a couple of additions to your list, both of which have been discussed earlier:
1) optional string parameter to record_route, which (if present) will be included in RR header as parameter. this is needed, for example, to record NAT information per branch. can also include a parameter from an AVP (if set). 2) it must be possible to pass socket info via fifo to t_uac_dlg. without this, t_uac_dlg doesn't work to SIP UAs behind NAT if ser listens on multiple ports. i suggested backwards compatible syntax for this in an earlier email. -- juha _______________________________________________ Devel mailing list [email protected] http://openser.org/cgi-bin/mailman/listinfo/devel
