IPO R10 sip and twinning users in hunt groups

[keski]

Hi,

We have some problems with IPO R10 software in certain sip trunks. Hunt group calls with twinning users are not receiving the original caller number anymore. If calling straight to twinning user extension the number is correct, but with group calls they see their own extension number instead of original caller.
With another sip trunk provider, we got this resolved by changing the “send caller id” in sip uri to Remote party id. But two other sip trunks won’t work. It needs to be “Diversion header” or forwarded calls won’t work at all. And it worked correctly with IPO releases 7 to 9.1 Have you come across with this situation too? What has changed in hunt group calls in R10? Any suggestions what other settings to test?

[muell61]

Hi, not exactly the same situation, since we had ISDN PRI Trunks, not SIP. But we also had problems with twinned phones seing the wrong number when internal phones called the twinning extension.
There where changes made in a late 9.1 service pack. Finaly we had to put a no-user code and then it worked again. I would suggest you to open a support ticket for this, be pationed an a little bit agreesive, until you made your way to tier 4. They'll be able to help you!
Regards, Rolf

[nduehr]

Also just ran into this after an IPO V10.2 upgrade.

Getting a five digit number sent out CID from extension to extension calls that trigger mobile twinning on the receiving extension.

This used to work on 9.1.12 with the "send originating CID" mobile twinning feature on the ISDN Line page turned on.

External callers into the system DO send correct CID out mobile twinning.

Not quite sure what to make of it. You guys ever find a solution from Avaya?