Hello All,
I recently configured 3300 Rls 8.0 with one of the service providers using the SIP trunks. It was victory and very easy to do it. The service provider is using asterisk base system to provide the services.
Since I heard a lot about failures of using the SIP trunks with so many vendors like quality issues, and not able to make conference calls.
I start testing by making several calls every time with different feature. When it comes to External conference it was perfectly fine but the second party gets the CLI of the first party not the system pilot number. For example if the main number for 3300 is CCCC number, first I will make a call to the first party which is AAAA number then press Transfer/Conf and dial the second party which is BBBB number, the display screen for the second party shows AAAA number instead of CCCC number.
I did network sniff using wireshark, I found that 3300 is sending an invite message for the second call with first party CLI.
I didn't play much with the SIP parameter, but any idea that might help. Because every time when I escalate an issue the answer is upgrade the system software.
I recently configured 3300 Rls 8.0 with one of the service providers using the SIP trunks. It was victory and very easy to do it. The service provider is using asterisk base system to provide the services.
Since I heard a lot about failures of using the SIP trunks with so many vendors like quality issues, and not able to make conference calls.
I start testing by making several calls every time with different feature. When it comes to External conference it was perfectly fine but the second party gets the CLI of the first party not the system pilot number. For example if the main number for 3300 is CCCC number, first I will make a call to the first party which is AAAA number then press Transfer/Conf and dial the second party which is BBBB number, the display screen for the second party shows AAAA number instead of CCCC number.
I did network sniff using wireshark, I found that 3300 is sending an invite message for the second call with first party CLI.
I didn't play much with the SIP parameter, but any idea that might help. Because every time when I escalate an issue the answer is upgrade the system software.