Twilio SIP trunk setup on Avaya IP Office 9.0

[chavz7796]

Hello Guys,

I'm trying to setup a Twilio Elastic SIP Trunk on an Avaya IP Office 500v2 on release 9.0. I dont have NAT Type One to One available. I am using Full Cone NAT, but the calls continue to drop after 30 seconds. Here is what it I'm getting on the PCAP.

Call-ID: 3de1f30082909fd918fd851bbca8b559@0.0.0.0
CSeq: 704170 BYE
Contact: <sip:+19153368933@internal IP:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer,100rel
Reason: Q.850;cause=16;text="Normal call clearing"

Any suggestions?

Thanks ahead of time.

 

[derfloh]

Without details... No!

Who is sending the Bye?

 

[chavz7796]

It is from the PBX from what I can tell.

BYE sip:+19157607169@172.25.41.188:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 192.168.16.9:5060;rport;branch=z9hG4bKe7a205392537c066b6303b04269d2f12
Route: <sip:54.172.60.2;lr>
From: <sip:+19153368933@public ip;edge=ashburn>;tag=a64ff6a248e21104
To: <sip:+19157607169@cavalier-sip-makios-cloud.pstn.twilio.com>;tag=61801498_c3356d0b_05ad9c30-b214-4c07-8fef-7b1ecdbc011e
Call-ID: 3de1f30082909fd918fd851bbca8b559@0.0.0.0
CSeq: 704170 BYE
Contact: <sip:+19153368933@internal ip:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer,100rel
Reason: Q.850;cause=16;text="Normal call clearing"
User-Agent: IP Office 9.0.1.0 build 845
Content-Length: 0


SIP/2.0 200 OK
CSeq: 704170 BYE
Call-ID: 3de1f30082909fd918fd851bbca8b559@0.0.0.0
From: <sip:+19153368933@public ip;edge=ashburn>;tag=a64ff6a248e21104
To: <sip:+19157607169@cavalier-sip-makios-cloud.pstn.twilio.com>;tag=61801498_c3356d0b_05ad9c30-b214-4c07-8fef-7b1ecdbc011e
Via: SIP/2.0/UDP 192.168.16.9:5060;received=public ip;rport=5060;branch=z9hG4bKe7a205392537c066b6303b04269d2f12
Server: Twilio
X-Twilio-CallSid: CA49f493228432414eb4b79d4ee72d00a9
Content-Length: 0

 

[sizbut]

30 seconds is the normal timeout for SIP call setup not being completed. Some expected response has not been received. You would need to go through a full trace pairing off the invites and responses.