|
|
Joined: Jan 2011
Posts: 81
Member
|
|
Member
Joined: Jan 2011
Posts: 81 |
I've got an issue with SIP trunking on outgoing call in os7030 .
I have OS 7030 V4.53b , The pbx behind Linksys router,with following license :
2 MGI license
2 SIP trunk license
The following ports are forwarded
to the ip of the pbx:
30000--30031
5060
9000
9001
6100
In Incoming call on the SIP trunk,I can receive call successfully
without any problem with voice .
But when i try to make outgoing call on the SIP trunk, The
"opposite hangup " Message appears on the Digital phone screen .
Note that, I can make outgoing call successfully When i use same account with ATA .
I need your help to solve this problem?
|
|
|
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: Jan 2011
Posts: 81
Member
|
|
Member
Joined: Jan 2011
Posts: 81 |
|
|
|
|
|
Joined: Aug 2009
Posts: 75
Member
|
|
Member
Joined: Aug 2009
Posts: 75 |
I'd check what CLI you are sending out on those extn ports dialling over the SIP Trunks
Have you run a trace using Wireshark?
|
|
|
|
|
Joined: Jun 2006
Posts: 3,004 Likes: 4
Moderator-Samsung
|
|
Moderator-Samsung
Joined: Jun 2006
Posts: 3,004 Likes: 4 |
Opposite hang up is usually todo with CLI as badger2003 has said.
Check with your carrier as to what you need to send (account number, indial number, etc)
|
|
|
|
|
Joined: May 2011
Posts: 14
Member
|
|
Member
Joined: May 2011
Posts: 14 |
We forward port 6000 (udp) as well. Then make sure on the CLI as stated above.
|
|
|
|
|
Joined: Sep 2007
Posts: 1,173
Member
|
|
Member
Joined: Sep 2007
Posts: 1,173 |
Add 40000-40031 in the mix for MPS channel use.
|
|
|
|
|
Joined: Jul 2009
Posts: 157
Member
|
|
Member
Joined: Jul 2009
Posts: 157 |
I would also add ports 5003, 5090 and 443 to give you remote access...
But I also agree with the CLI sending. Depending on the configuration required by the SIP provider of course, but I usually set the SIP carrier details to send CLI table 2, then in CLI table 2 either set each number for each SIP trunk, or, set the main number for all ports, or direct indial for each extension etc.
If the CLI fields are blank for a particular extension and trunk, then it will send the number recorded in the trunk data section.
With no number set (or the default extension numbers in the CLI table for example) it will usually fail the call attempt as its telling the SIP carrier the wrong user details and will give the opposite hangup message.
Cheers, Dave. Eco Communications Selling and installing Ericsson BP150/50/250 from 1996 to 2005 Samsung selling and installing since 2000 Toshiba selling and installing since 2004 Microsoft NT and SQL certified (10 years ago...)
|
|
|
|
|
Joined: Jan 2011
Posts: 81
Member
|
|
Member
Joined: Jan 2011
Posts: 81 |
The same problem still appear Although
I added following ports to forward list :
6000 udp
40000-40031 (Although I dont use the MPS Channel )
Note that, The SIP provider does not have information about The CLI which should I send to him
|
|
|
|
|
Joined: May 2011
Posts: 14
Member
|
|
Member
Joined: May 2011
Posts: 14 |
Try sending the client's number in international format to the SIP provider.
|
|
|
|
|
Joined: May 2011
Posts: 14
Member
|
|
Member
Joined: May 2011
Posts: 14 |
Just had a look at the ports again:
TCP 5060,5070, 5080, 1024-4999
UDP 5060,5061, 30000-3012
Try that and let us know.
|
|
|
|
Forums84
Topics94,512
Posts639,933
Members49,844
| |
Most Online5,661
May 23rd, 2018
|
|
|
0 members (),
114
guests, and
34
robots. |
|
Key:
Admin,
Global Mod,
Mod
|
|
|
|
