SIP connect and RFC 6140

Hello All,

We're trying to figure out how sipconnect v1.1 plus rfc6140 mass registration should be provisioned on the Acme 4500, since we're building a service provider sip trunking proof of concept. In our current concept we initially use:

• IP-PBX (Aastra) with 10 extensions in the access.
• Acme 4500 SCX 6.3.7 with transcoding NIU at the border.
• SIP Softswitch in the core.

Configuration-wise:

• We use the policy-based-realm-bridging architecture.
• We've provisioned the SBC according to a BCP, so amongst others; option 'sipconnect-pbx-reg' in the realm, the option "reg-via-key" in the sip interface and registration caching enabled.

If we use 'normal' registration, so the PBX sends its 'main number' in one register message (cached in the Acme and in the core softswitch), all seems to work fine