Issue with incoming on particular trunk

Hello iptel ( itel moderator )

I have an issue , with one one trunk "itworld "
The outgoing calls through this trunk go fine , but incoming calls timeout .

The reason being told out by support is that i should talk to you for following reason

here is message i have got
============
" The problem is that the switch at 76.191.104.53 is sending its responses to
the wrong port at our switch.
All RESPONSES must be sent to port 5062. However, the
TRYING message is sent to port 5060. Therefore, our switch does not register any response from the switch at 76.191.104.53 and times
the call out. I suggest you discuss this with the vendor of the switch.

=============================

there is no issue of incoming or outgoing by using same settings on ata or any softphone .
Also help me settingup keepalive for same .

Please help

=====================

Still waiting for Moderator to look into the issue , as it has to be done at pbx end.

This post has been edited 1 time(s), it was last edited by gag on 10.07.2012 at 13:17.

RE: Issue with incoming on particular trunk

Please enable SIP trace in System Log. Then make an incoming call. I would like to see the incoming INVITE message to answer your request.

RE: Issue with incoming on particular trunk

Hello
i enabled Sip trace and made a few test incoming calls , which were timed out

Regards

RE: Issue with incoming on particular trunk

Please share the generated log here.

Thanks

RE: Issue with incoming on particular trunk

hello
i was not aware that duplicate posts are not allowed.

Anyhow i will continue it here

i have had fresh sip trace here

To: <sip:100071@173.44.36.218>;tag=as681b41e7
Contact: <sip:100071@173.44.36.218:28670>
CANCEL sip:100071@173.44.36.218 SIP/2.0
To: <sip:100071@173.44.36.218>
To: <sip:100071@173.44.36.218>;tag=as681b41e7
Contact: <sip:100071@173.44.36.218:28670>
To: <sip:100071@173.44.36.218>;tag=as681b41e7
Contact: <sip:100071@173.44.36.218:28670>
To: <sip:100071@173.44.36.218>;tag=as681b41e7
Contact: <sip:100071@173.44.36.218:28670>
To: <sip:100071@173.44.36.218>;tag=as681b41e7
Contact: <sip:100071@173.44.36.218:28670>
To: <sip:100071@173.44.36.218>;tag=as681b41e7
Contact: <sip:100071@173.44.36.218:28670>
To: <sip:100071@173.44.36.218>;tag=as681b41e7

=============================

Further i have been told that all responses must be sent to port 5062 and this is also in contact header of INVITE but pbxes is ignoring it and sending it to 5060

i have on of contact headers from other end
==========
Via: SIP/2.0/UDP 95.154.218.17:5062;branch=z9hG4bK-1000001782342-1
From: <sip:100085@95.154.218.17>;tag=1000001782342
To: <sip:100071@76.191.104.53>
Call-ID: 1000001782342@95.154.218.17
CSeq: 1 INVITE
Contact: <sip:100016@95.154.218.17:5062>

=======================
if we stick to Port in contact header and responses are sent accordingly , the issue wont arise .

Looks like what is happening is port on Contact header is being ignored and it is set to sent responses at 5060 in all cases.

Iptel MODERATOR kindly follow it up

Thanks

This post has been edited 7 time(s), it was last edited by gag on 17.08.2012 at 02:15.

RE: Issue with incoming on particular trunk

It would be nice to have a SIP trace that shows complete messages. The incoming INVITE and the answer from PBXes.

RE: Issue with incoming on particular trunk

Hello
i have the old sip trace which i received from other end last time round
, you can find it below

What i have been told is that calls from our device are being sent from port 5060 as usual which is correct but all responses must be sent to port 5062

frame 6 includes a CONTACT header
that specifies that all responses must be sent to port 5062. However, the
TRYING message frame 7 is sent to port 5060.

therefore the switch fails to recognize it and times out the call
============
Frame 6 (678 bytes on wire, 678 bytes captured)
Ethernet II, Src: Dell_2a:67:cd (00:26:b9:2a:67:cd), Dst: c8:9c:1d:60:73:7f
(c8:9c:1d:60:73:7f)
Internet Protocol, Src: 95.154.218.17 (95.154.218.17), Dst: 76.191.104.53
(76.191.104.53)
User Datagram Protocol, Src Port: sip (5060), Dst Port: 29951 (29951)
Session Initiation Protocol
Request-Line: INVITE sip:100071@76.191.104.53 SIP/2.0
Message Header
Via: SIP/2.0/UDP 95.154.218.17:5062;branch=z9hG4bK-1000001782342-1
From: <sip:100085@95.154.218.17>;tag=1000001782342
To: <sip:100071@76.191.104.53>
Call-ID: 1000001782342@95.154.218.17
CSeq: 1 INVITE
Contact: <sip:100085@95.154.218.17:5062>
Content-Type: application/sdp
Content-Length: 258
Message Body


No. Time Source Destination Protocol
Info
7 0.238870 76.191.104.53 95.154.218.17 SIP
Status: 100 Trying
-------------
Frame 7 (440 bytes on wire, 440 bytes captured)
Ethernet II, Src: c8:9c:1d:60:73:7f (c8:9c:1d:60:73:7f), Dst: Dell_2a:67:cd
(00:26:b9:2a:67:cd)
Internet Protocol, Src: 76.191.104.53 (76.191.104.53), Dst: 95.154.218.17
(95.154.218.17)
User Datagram Protocol, Src Port: 29951 (29951), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 100 Trying
Message Header
Via: SIP/2.0/UDP
95.154.218.17:5062;branch=z9hG4bK-1000001782342-1;received=95.154.218.17
From: <sip:100085@95.154.218.17>;tag=1000001782342
To: <sip:100071@76.191.104.53>
Call-ID: 1000001782342@95.154.218.17
CSeq: 1 INVITE
User-Agent: PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Contact: <sip:100071@76.191.104.53:29951>
Content-Length: 0

================

i hope this helps


>>>IPTEL / Moderator Please update

This post has been edited 1 time(s), it was last edited by gag on 23.08.2012 at 20:03.

RE: Issue with incoming on particular trunk

Hello iptel, I have a similar issue with Vitelity.net, the PBX is registered, I can make outgoing calls... but incoming calls are passed through to PBXES, and immediately "hung up"... the siptrace from Vitelity shows the issue...

any recommendations??

vitelity siptrace

This is a courtesy message from Vitelity Communications, LLC regarding an active Trouble Ticket you have in our system for the account xxxx

Your Trouble Ticket has been updated with a response/resolution to your problem.

Posted by vcmfs on 2012-10-05 10:46:39
We see that calls are routing to your device but your device is hanging up.

Oct 5 10:45:35.514 AM 66.241.96.164 > 67.231.245.210 INVITE sip:3215496380@67.231.245.210:27292 SIP/2.0
Oct 5 10:45:35.569 AM 66.241.96.164 < 67.231.245.210 SIP/2.0 100 Trying
Oct 5 10:45:35.570 AM 66.241.96.164 < 67.231.245.210 SIP/2.0 200 OK
Oct 5 10:45:35.571 AM 66.241.96.164 > 67.231.245.210 ACK sip:3215496380@67.231.245.210:27292 SIP/2.0
Oct 5 10:45:36.595 AM 66.241.96.164 < 67.231.245.210 BYE sip:3034753030@66.241.96.164 SIP/2.0
Oct 5 10:45:36.595 AM 66.241.96.164 > 67.231.245.210 SIP/2.0 200 OK

Please check your inbound route.

RE: Issue with incoming on particular trunk

Hello

i have also raised personal support ticket 2 days back .. though it is a BUG ........atleast now please look into it

Thank you

This post has been edited 1 time(s), it was last edited by gag on 09.11.2012 at 08:27.

RE: Issue with incoming on particular trunk

In Source View please add "nat=never" to the SIP options of your particular trunk. This should make it answer to the other port number.

RE: Issue with incoming on particular trunk

Thank you.. it worked

I wish had someone pointed it out earlier .. as it is not documented anywhere ... i had to wait for months with no response here .
I am sad that i was forced to purchase support for non documented part .

RE: Issue with incoming on particular trunk

Great that it works now.

This is a very rare case as your provider uses different port numbers at the various stages of a call. As this is very unusual only PRO users can set the option, as it can have other side effects where not needed. No PBXes user ever needed it. We had to research the option for you.