Jump to content
Vodia PBX forum
ndemou

History info issue

Recommended Posts

In v60 & v61 when History info is enabled in a trunk the system sends the "History:" field in all calls, even those that are not forwarded where history info doesn't make sense. In order to comply with the interconnection agreements we have with major national carriers the History Info should only be present in forwarded calls. This is serious because they reject such calls.  

Share this post


Link to post
Share on other sites

Hmm I think the easiest solution would be to add another option to the history info so what we can say how long the history has to be to be included in the request.

Share this post


Link to post
Share on other sites

I would be happy even with check box "[ ] don't include history info if history is empty" but you'll be the judge.

Can you implement anything within the next few days? A workaround for either v.60 or v.61 maybe (ugly ones are fine too)?

Share this post


Link to post
Share on other sites

We have made 61.1 builds for CentOS64 and Debian64 ("Latest and Greatest" builds, not a release) that includes this. Maybe we can also get a Win64 build done in the next few days.

Share this post


Link to post
Share on other sites

BTW during these tests I noticed that restarting the pbxctrl still takes quite a lot of time (~2mins). Shouldn't v60 and 61 be restarting a lot faster?

Share this post


Link to post
Share on other sites

Thanks for the beta. Unfortunately we didn't get it right with the first try. Here are the results of our tests. We are sending more details and traces in the support mail.

  1. We observe that both forwarded and non-forwarded calls have 2 levels of history-info. This is definetely not OK.

  2. In the case of the non forwarded call as stated above our peer agrements mandate that we transmit no history-info at all.

  3. In the case of the forwarded call where A calls B and is forwarded to C all was fine in v60. However in v61.1 we have a regression: the history-info is still OK but the P-Asserted-Identity field is wrong: it has the B-number instead of the A-number.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×