thread940-1734544
Hi all,
I'm new to the IP-Office world
Like the thread Iàm referring to, I have some problems to manage incoming calls when the caller is sending the digits in overlap instead of enbloc.
I replaced an Avaya CM with an IPO 9.1 with a PRI card, and some incoming calls are rejected.
In the Incoming Call Route I specified all the destinations.
After a lot of tests I figure out that the problem occurs when I receive from the provider an ISDN "Setup" message with only the first part of the called number.
Then I should receive the remaining digits inside the "Information" messages, but the IPO does not accept these messages.
For example the full number is 0123456789, but I receive the setup with the Called number: 0123456 and the IPO immediatelly looks for a match without waiting for the remaining digits.
With all the other PBXs I can manage the incoming calls in overlap, but I cannot find out if IPO can manage this type of calls.
I already contacted the provider, but they cannot change their configuration, this is an accepted configuration in the ISDN standard.
Has anyone ever managed to fix this problem ?
Thanks
Obi
Hi all,
I'm new to the IP-Office world
Like the thread Iàm referring to, I have some problems to manage incoming calls when the caller is sending the digits in overlap instead of enbloc.
I replaced an Avaya CM with an IPO 9.1 with a PRI card, and some incoming calls are rejected.
In the Incoming Call Route I specified all the destinations.
After a lot of tests I figure out that the problem occurs when I receive from the provider an ISDN "Setup" message with only the first part of the called number.
Then I should receive the remaining digits inside the "Information" messages, but the IPO does not accept these messages.
For example the full number is 0123456789, but I receive the setup with the Called number: 0123456 and the IPO immediatelly looks for a match without waiting for the remaining digits.
With all the other PBXs I can manage the incoming calls in overlap, but I cannot find out if IPO can manage this type of calls.
I already contacted the provider, but they cannot change their configuration, this is an accepted configuration in the ISDN standard.
Has anyone ever managed to fix this problem ?
Thanks
Obi