[Spce-user] Problems with the packets size (MTU)

Raul raul.alonso at tpartner.net
Tue Mar 10 07:36:02 EDT 2015


I have observed that when this happens, an error is generated in the sems
logs.

 

Mar 10 12:34:11 sipproxy01 sems[26723]: [#7f0793dfd700] [send_request,
trans_layer.cpp:935] ERROR: Could not update UAC state for request.

Mar 10 12:34:15 sipproxy01 sems[26723]: [#7f0792ded700] [handleSipMsg,
AmSipDispatcher.cpp:54] WARNING: unhandled SIP reply: INVITE
[code:408;phrase:[Request
Timeout];i:508f8000ed82-54fed69e-54934c3b-35f13440-101f725 at 127.0.0.1;cseq:11
;cseq
meth:INVITE;l-tag:7640C683-54FED69E000D1D8C-92BEB700;r-tag:00E0F5100C4F384DA
B2940BFA1C5;hdr:[Server: Sipwise NGCP Proxy 2.X#015#012];]

 

 

Regards,

Raul

 

De: Spce-user [mailto:spce-user-bounces at lists.sipwise.com] En nombre de Raul
Enviado el: martes, 10 de marzo de 2015 12:12
Para: spce-user at lists.sipwise.com
Asunto: [Spce-user] Problems with the packets size (MTU)

 

Good morning,

 

We are testing a trunk from an Alcatel OXE.

The calls work correctly until we try to make a transfer, when this happens
the SIP frames increase and reach the MTU.

 

>From the proxy I can do a trace and I can see how the frame is cut:

 

U 2015/03/10 12:00:12.888046 62.XXX.XXX.XXX:5060 -> 89.XXX.XXX.XXX:5060

INVITE sip:93XXXXXX at 89.XXX.XXX.XXX:5060 SIP/2.0'

Record-Route:
<sip:62.XXX.XXX.XXX;r2=on;lr=on;ftag=15A7316A-54FECEAD000AF9CE-92CEC700;ngcp
lb=yes;socket=udp:62.XXX.XXX.XXX:5060>'

Record-Route:
<sip:127.0.0.1;r2=on;lr=on;ftag=15A7316A-54FECEAD000AF9CE-92CEC700;ngcplb=ye
s;socket=udp:62.XXX.XXX.XXX:5060>'

Max-Forwards:  9'

Record-Route:
<sip:127.0.0.1:5062;lr=on;ftag=15A7316A-54FECEAD000AF9CE-92CEC700;rtpprx=yes
;ice_caller=strip;ice_callee=strip;mpd=ii>'

Via: SIP/2.0/UDP
62.XXX.XXX.XXX;branch=z9hG4bK96.eb66042fdbc88629319b4efc5fd3bfaa.0'

Via: SIP/2.0/UDP
127.0.0.1:5062;rport=5062;branch=z9hG4bK96.62c804ed30aa5252babc0de6806a6b12.
0'

Via: SIP/2.0/UDP 127.0.0.1:5080;branch=z9hG4bKtctRNa14;rport=5080'

From: <sip:93XXXXXX at 62.XXX.XXX.XXX>;tag=15A7316A-54FECEAD000AF9CE-92CEC700'

To: <sip:93XXXXXX at 89.XXX.XXX.XXX>;tag=00E0F5100C4F384A90FB2D49B279'

CSeq: 10 INVITE'

Call-ID: 508f8000ed82-54fecead-53256c9a-2dc6c000-101e674 at 127.0.0.1
<mailto:508f8000ed82-54fecead-53256c9a-2dc6c000-101e674 at 127.0.0.1> '

Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS,
UPDATE'

Supported: replaces,timer,path,100rel'

User-Agent: OmniPCX Enterprise R10.1.1 j2.603.35'

Content-Type: application/sdp'

Content-Length: 279'

Contact:
<sip:ngcp-lb at 62.XXX.XXX.XXX:5060;ngcpct=7369703a3132372e302e302e313a35303830
>'

'

v=0'

o=OXE 1425985197 1425985198 IN IP4 62.XXX.XXX.XXX'

s=abs'

c=IN IP4 62.XXX.XXX.XXX'

t=0 0'

m=audio 35188 RTP/AVP 8 99'

a=rtpmap:8 PCMA/8000'

a=rtpmap:99 telephone-event/8000'

a=sendonly'

a=ptime:20'

a=maxptime:30'

a=oldmediaip:1 <---------------------------------- trace cut

 

 

I tried filter codec to  PCMA for testing, but i have the same issue.

I can do something more to try solve this problem?

 

Regrads,

Raúl.

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20150310/bd53442a/attachment-0001.html>


More information about the Spce-user mailing list