nickofherts
Technical User
Hello all,
We are using Gamma SIP trunks and an IP500 9.0.0.0 build 829.
If we set up the SIP trunk on our WAN and make a call in on the ISDN, forward it out over the SIP, it displays the CLI of the incoming call which is what the end user wants for the out of hours support mobile.
If we load the very same config (the only changes made are to the LAN1 and gateway)on to end users system which is also on 9.0.0.0 build 829, reconfigure the SIP trunk for their WAN, although calls get forwarded they lose the incoming CLI and show the extension number instead. We can see this on Monitor.
so, same firmware level, same configuration, same SIP trunk, different behaviour.
any thoughts as to what might be causing this? at the moment it looks as though we may have to take our CCU to site and physically swap them out...
many thanks
We are using Gamma SIP trunks and an IP500 9.0.0.0 build 829.
If we set up the SIP trunk on our WAN and make a call in on the ISDN, forward it out over the SIP, it displays the CLI of the incoming call which is what the end user wants for the out of hours support mobile.
If we load the very same config (the only changes made are to the LAN1 and gateway)on to end users system which is also on 9.0.0.0 build 829, reconfigure the SIP trunk for their WAN, although calls get forwarded they lose the incoming CLI and show the extension number instead. We can see this on Monitor.
so, same firmware level, same configuration, same SIP trunk, different behaviour.
any thoughts as to what might be causing this? at the moment it looks as though we may have to take our CCU to site and physically swap them out...
many thanks