|
|
Joined: Mar 2013
Posts: 144
Member
|
OP
Member
Joined: Mar 2013
Posts: 144 |
Hi everyone, Im testing Clearfly sip trunks on SL2100 and cant figure out why im unable to change outbound Caller ID.
System sends out number from 10-36-01 or 02 and ignores settings in 21-13, 21-19
what am I missing
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
|
Joined: Sep 2004
Posts: 4,195 Likes: 2
Member
|
|
Member
Joined: Sep 2004
Posts: 4,195 Likes: 2 |
|
|
|
|
|
Joined: Mar 2013
Posts: 144
Member
|
|
OP
Member
Joined: Mar 2013
Posts: 144 |
20-08-13 was checked. just to make sure added my extension to COS 15, didn help.
while trying different settings i lost ability to make outbound calls through sip trunk from my remote extension, but incoming do get through and no isues with voice.
I can make outbound calls from remote extension through CO trunk.
Im ready to wipe everything off and start from scratch
|
|
|
|
|
Joined: Mar 2013
Posts: 144
Member
|
|
OP
Member
Joined: Mar 2013
Posts: 144 |
20-08-13 was checked. just to make sure added my extension to COS 15, didn help.
while trying different settings i lost ability to make outbound calls through sip trunk from my remote extension, but incoming do get through and no isues with voice.
I can make outbound calls from remote extension through CO trunk.
Im ready to wipe everything off and start from scratch Update: Found my mistake and solved an issue with outbound calls Still no luck with outbound CID on sip trunks. Tried every setting one by one and in different combinations. out of ideas
|
|
|
|
|
Joined: Sep 2004
Posts: 4,195 Likes: 2
Member
|
|
Member
Joined: Sep 2004
Posts: 4,195 Likes: 2 |
They also have to allow it.
|
|
|
|
|
Joined: Sep 2004
Posts: 4,195 Likes: 2
Member
|
|
Member
Joined: Sep 2004
Posts: 4,195 Likes: 2 |
Seriously, just wireshark it and see what's going on. I routinely add SIP trunks on NEC systems that aren't white paper.
|
|
|
|
|
Joined: Mar 2013
Posts: 144
Member
|
|
OP
Member
Joined: Mar 2013
Posts: 144 |
Opened the ticket with NEC and after reviewing config file they suggested defaulting 84-39 which solved the problem.
I never touched any settings in 84-39 perhaps there is a note under it in PcPro saying that it is Read Only to observe SIP Trunk information.
Unless while browsing through settings I accidently scrolled a mouth wheel over value setting and changed it when I was actually trying to scroll a page down.
Lesson learned
Coral Tech, Thank you for responding, I did InCapture from WebPro and sent it over to NEC. Is it the same as Wireshark capture?
|
|
|
|
Forums84
Topics94,283
Posts638,765
Members49,764
| |
Most Online5,661
May 23rd, 2018
|
|
|
1 members (Toner),
138
guests, and
182
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
