Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Gamma SIP Trunk IPDC 6.1 no calls in or out

Status
Not open for further replies.
bonus99

bonus99

Technical User
Apr 9, 2003
55
GB
Please, I beg of you, some help to avoid driving my car over a cliff in sheer desperation!
This is not an urgent issue (or was not when I started), I am now tearing my hair out.

I have had two engineers look at this as well as me.

I/c calls get a couple of beeps in the callers ear and then clear down, this is the message:

808160mS SIP Rx: UDP xx.245.6.81:5060 -> xxx.231.216.140:5060
INVITE sip:02080901280@xxx.231.216.140 SIP/2.0
Max-Forwards: 69
Session-Expires: 3600;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:02080901280@xx.245.6.81:5060>
From: <sip:07973673265@xx.245.6.81>;tag=3517057571-578992
Remote-Party-Id: <sip:7973673265@xx.245.6.81>;screen=yes;privacy=off
Call-ID: 1291655-3517057571-578987@MSX11.test.com
CSeq: 1 INVITE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Via: SIP/2.0/UDP 83.245.6.81:5060;x-route-tag="tgrp:test-INGRESS-TRKGRP";branch=z9hG4bK84c47011c63d2022d41708c4fea692b3
Contact: <sip:07973673265@83.xxx.6.81:5060>
Expires: 180
Call-Info: <sip:xx.245.6.81>;method="NOTIFY;Event=telephone-event;Duration=1000"
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 260

v=0
o=MSX11 5577 7987 IN IP4 xx.245.6.81
s=sip call
c=IN IP4 xx.245.6.82
t=0 0
m=audio 36202 RTP/AVP 18 100 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
808663mS SIP Rx: UDP xx.245.6.81:5060 -> xx.231.216.140:5060
INVITE sip:02080901280@xxx.231.216.140 SIP/2.0
Max-Forwards: 69
Session-Expires: 3600;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:02080901280@xx.245.6.81:5060>
From: <sip:07973673265@xx.245.6.81>;tag=3517057571-578992
Remote-Party-Id: <sip:7973673265@xx.245.6.81>;screen=yes;privacy=off
Call-ID: 1291655-3517057571-578987@MSX11.test.com
CSeq: 1 INVITE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Via: SIP/2.0/UDP xx.245.6.81:5060;x-route-tag="tgrp:test-INGRESS-TRKGRP";branch=z9hG4bK84c47011c63d2022d41708c4fea692b3
Contact: <sip:07973673265@xx.245.6.81:5060>
Expires: 180
Call-Info: <sip:xx.245.6.81>;method="NOTIFY;Event=telephone-event;Duration=1000"
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 260

v=0
o=MSX11 5577 7987 IN IP4 xx.245.6.81
s=sip call
c=IN IP4 xx.245.6.82
t=0 0
m=audio 36202 RTP/AVP 18 100 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
809663mS SIP Rx: UDP xx.245.6.81:5060 -> xxx.231.216.140:5060
INVITE sip:02080901280@xxx.231.216.140 SIP/2.0
Max-Forwards: 69
Session-Expires: 3600;refresher=uac
Min-SE: 600
Supported: timer, 100rel
To: <sip:02080901280@xx.245.6.81:5060>
From: <sip:07973673265@xx.245.6.81>;tag=3517057571-578992
Remote-Party-Id: <sip:7973673265@xx.245.6.81>;screen=yes;privacy=off
Call-ID: 1291655-3517057571-578987@MSX11.test.com
CSeq: 1 INVITE
Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH
Via: SIP/2.0/UDP xx.245.6.81:5060;x-route-tag="tgrp:test-INGRESS-TRKGRP";branch=z9hG4bK84c47011c63d2022d41708c4fea692b3
Contact: <sip:07973673265@xx.245.6.81:5060>
Expires: 180
Call-Info: <sip:xx.245.6.81>;method="NOTIFY;Event=telephone-event;Duration=1000"
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Length: 260

v=0
o=MSX11 5577 7987 IN IP4 xx.245.6.81
s=sip call
c=IN IP4 xx.245.6.82
t=0 0
m=audio 36202 RTP/AVP 18 100 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16

Trunk says out of service.

Have configured as per this document as well:


It just will not work, there have been issues with them but they say that all is well their end.

Any help would be greatly appreciated.

Many thanks

Desperate Dan
 
Sort by date Sort by votes
After a long sleep, hair pulling and all round breakdown, I have not managed to solve this issue.

So, I changed my attack and tried outgoing.

This fails at the ARS due to the trunk out of service.

Now this may seem a really silly question, what on earth can I do to get this trunk to display in service?

I have gone through everything.

If my question means that you lock me in the stocks and pound me with e-coli vegetables for a week then so be it but, please put me out of my misery.

Many thanks as always

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I don't think I know anything.
I am never able to help anyone!
 
Upvote 0 Downvote
Did STUN work from that address? Did the fields populate ?(takes under 1 min)
Did Gamma provide a username and password or is it authenticated via IP?
What sits between IPO and the leased line? (this is probably where the issue is if all else is OK) :)

ACSS - SME
APSS - SME


"I'm just off to Hartlepool, to buy some exploding trousers
 
Upvote 0 Downvote
I also see an IP mismatch here.

o=MSX11 5577 7987 IN IP4 83.245.6.81 <<---???
s=sip call
c=IN IP4 83.245.6.82 <<---???
t=0 0
m=audio 36202 RTP/AVP 18 100 101
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
809663mS SIP Rx: UDP 83.245.6.81:5060 -> 109.231.216.140:5060

And If you are on a leased line at least you could do is run it on G711!!!

ACSS - SME
General Geek

CallUsOn.png


1832163.png
 
Upvote 0 Downvote
post your config (with rapid share or similar) remove any sensitive information, and also explain what router you are using with the correct ports open!

ACSS - SME
General Geek

CallUsOn.png


1832163.png
 
Upvote 0 Downvote
To those all saying you have to have STUN for Gamma IPDC trunks to work - I have generally found the reverse to be true and we have to have STUN turned off for Gamma trunks to work (especially if we have gamma and voiceflex trunks on the same phone system).

I had a problem with Gamma yesterday (after they migrated some Assured 5 broadband connections) which meant several conference calls with Gamma and the firewall provider for one customer just to get them working again.

Whilst on this call the Gamma engineer even asked about STUN and I said we never use it with Gamma Trunks and he said that was generally correct yes.

| ACSS SME |
 
Upvote 0 Downvote
Well, every single Gamma SIP install ive had the pleasure of doing required a STUN server when traversing NAT.....

ACSS - SME
General Geek

CallUsOn.png


1832163.png
 
Upvote 0 Downvote
Ditto, I have Hipcom (BT) and Gamma trunks on our Demo kit, the Gamma trunks never work unless we run STUN, the Hipcom trunks work just via the IP routes every time. Gamma recommend you open/forward a huge port range to get their SIP trunks to register, this is complete bollocks and is not required, Gamma talk a lot of rubbish a lot of the time :)

ACSS - SME
APSS - SME


"I'm just off to Hartlepool, to buy some exploding trousers
 
Upvote 0 Downvote
Cheers guys, I really appreciate your help and I am trying to get this going amongst a load of other work as well and it takes back seat a bit.

I ran STUN but it did not populate.

The IPO is connected direct to the Gamma EDD, there is no firewall.

I will go through your suggestions above and let you know how I get on.

Cheers
Bruce

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I don't think I know anything.
I am never able to help anyone!
 
Upvote 0 Downvote
Yes, I can ping OK

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I don't think I know anything.
I am never able to help anyone!
 
Upvote 0 Downvote
STUN trace from monitor:

155172mS Stun: Creating STUNClient for xxx.xxx.xxx.xxx:5060, server 217.10.68.152:10000
155172mS Stun: Creating STUNUdpClient port 5060 address f5646460
280173mS Stun: StunClient: SendNAT Configuration, 0.0.0.0:0
280173mS Stun: NAT config is UDP blocked: 0
280173mS Stun: StunClient: SendNAT Configuration result:0 ip:0.0.0.0
280173mS Stun: Discovery on LAN 2 completed, updating
280173mS Stun: ~STUNClient xxx.xxx.xxx.xxx:5060

Does not look good to me, any ideas?

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I don't think I know anything.
I am never able to help anyone!
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

rsv23
  • Locked
  • Question
SIP Trunk Routing
Replies
3
Views
402
rsv23
rsv23
DiyFrea
  • Locked
  • Question
SIP trunk - no audio
Replies
9
Views
1K
derfloh
derfloh
phoneDTC
  • Locked
  • Question
SIP Trunk Question
Replies
5
Views
541
phoneDTC
phoneDTC
claudiotele
  • Question
Sip Trunk over TLS not working
Replies
7
Views
458
Mo. Abdullah
Mo. Abdullah
sheldoom
  • Locked
  • Question
H.323 Trunk to SIP Trunk
Replies
4
Views
608
Menniss
Menniss

Part and Inventory Search

Sponsor

Back
Top