Hi All,
I did get this Gamma Sip trunk working in the end and thought I'd share the config for anyone who may need help, the incomming call routes for the voiceflex sip trunk are still a bit untidy but this is all about getting the Gamma trunk working :)
Link
The Gamma trunk will only be used for Incoming calls also, it's only on the system as we need to port some numbers from eurobell and voiceflex don't have an agreement in place with them but Gamma do.
I'm not great at looking at these monitor trace's but I can see my call being received on the Gamma trunk 18 and then transmitting back out to the gamma IP addresses, doesn't look like it's trying to go out on Voiceflex but I may well be wrong.
The other Voiceflex trunk is 17 and is used for...
There are 2 sip trunks on the system, The voiceflex trunk has been working for a few months now and I'm now trying to add this 2nd Gamma trunk.
If the call I just made is trying to go out over voiceflex then something is very wrong.
Some data must be getting back to Gamma though as I have 2...
Here you go, call made from my number starting 019086, waited for the call to drop around 40s in and then I hung up my end not long after that.
Again thx for you help guyshttp://dl.dropbox.com/u/23770920/PaveySIPCall.txt
I'm not sure what the sonicwall chap has done but I've now got 2 way speech but the call drops after about 40 seconds and Gamma say they are seeing lots of 200 ok's which is odd as normally they'd only see 1 when the call is first initiated :s
I watched the call on SSA and it just drops around...
oh and regard's to all the incoming call routes, that's not my doing, the IT guy did that after I installed the system, I'm sure most of it can be deleted and tidied up but I'd like to get his SIP trunk working first so I can port some numbers over :)
You should see his other system this is...
Thanks HSM, from your last post I've been able to go back to the Sonicwall chap who has just traced what changes the sonicwall is making to my STUN traffic and is trying to put it right which I'm hoping will fix my problem (fingers crossed)
I'll let you know when he gets back to me.
I normally use voiceflex too and have never had a problem with them. But this config doesn't help me at all, the Gamma trunk I'm using doesn't need to register.
Hairless, are you asking me? I'd try anything at this point to get it up and running, Gamma are telling me there is another option where they can change something at their end which they do for Mitel kit but it'll mean any options I could configure via the portal like failover settings and...
OK the IT guy at the company we are trying to get this working for tells me he might have a spare public IP address we can use.
If we scrap trying to use the STUN and assign this IP to the IPO and get Gamma to point the SIP trunk to the new IP should this work? or is the IPO still going to...
I also have an error showing next to the Firewall/NAT Type saying "Communication is not possible unless the STUN server is supported on the same IP address as the ITSP. :(
Hairless, the sip transformations are turned off (according to the Firewall guy) and when I run the STUN 77.72.169.160 it's coming back and giving me "Port restricted Cone NAT" again and it's not giving me 5060 no, it seems to change every time I reboot the system, this time I have 50053
Monty...
It's a Sonicwall I believe on the site I'm trying to get working, I've been told all the ports I've requested are open in and out, he also said he'd turned off any sip translation on the Sonicwall as in general he found it caused more problems.
I'll try your STUN server address hairless and see...
I also have these ports open as per the Gamma document they sent through but thought this might be helpful if any of you had missed it.
Traffic on the following ports must be forwarded through relevant routers and firewalls on the customer premises to allow access to the Gamma IP Direct...
I've got the exact same problem, I've got all the right ports open in and out, the STUN server I'm using (146.101.248.221) is returning the correct public facing IP reading "Port restricted Cone NAT" and I made sure under the SIP trunk line transport tab I've told it to look at LAN1 network...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.