I think the problem is some of the CPE can only handle static IP-to-IP SIP trunks - no UAC capable of answering 407 challenges or doing registration, which often go hand in hand. Also, BYEs and CANCELs should not be authenticated; that's silly, they're already anchored to dialogs for which there is known state. Only initial INVITEs. Can you really not change that in the Metaswitch? anorexicpoodle wrote:
Actually depending on how you have constructed your trunk in Metaswitch you can indeed authenticate the call, just turn on the SIP Authentication required flag in the configured SIP binding for your trunk. Be aware this will force it to authenticate invite, cancel and bye messages so this may be undesirable but it will certainly get you what you need.
Given the scope of your problem though you know who is originating the call since it would be coming from a configured sip binding, are the billing records Metaswitch produces insufficient for this?
-- Alex Balashov - Principal Evariste Systems Web : http://www.evaristesys.com/ Tel : (+1) (678) 954-0670 Direct : (+1) (678) 954-0671