[Spce-user] Missing Max-Forwards Header

Kevin Masse kmasse at questblue.com
Wed Jan 8 16:30:10 EST 2014


Daniel, are you recommending it be added in this location in version 2.8 also?
In the 2.8 I show ngcp.sbcprofile.conf.tt2 vs ngcp.sbcprofile.conf and it is not listed.  Additionally we have never experienced this issue that Larry is reporting.

Kevin



-----Original Message-----
From: Daniel Grotti [mailto:dgrotti at sipwise.com] 
Sent: Wednesday, January 08, 2014 4:23 PM
To: Schaefer, Larry
Cc: Kevin Masse; spce-user at lists.sipwise.com
Subject: Re: [Spce-user] Missing Max-Forwards Header

Hi Larry,
try to enable in the sems whitelist in /etc/ngcp-config/templates/etc/sems/etc/ngcp.sbcprofile.conf the Max-Forwards header, otherwise it will be removed.
 
header_filter=whitelist
header_list=P-D-Uri,P-Asserted-Identity,Privacy,WWW-Authenticate,Proxy-Authenticate,Max-Forwards


Daniel




On Wednesday, January 8, 2014 21:35 CET, "Schaefer, Larry" <Larry.Schaefer at pgi.com> wrote: 
 
> Kevin,
> 
> Thanks for the quick response... That value is listed in the kamailio lb section with a value of 10.  However, in my example, I was not using the load balancer.  I was just testing directly with sending an Invite (from a softphone client) directly to the SBC and watching what came out of the SBC...  I also believe that I am on the 3.1 version.
> 
> kamailio:
>   lb:
>     debug: 'no'
>     extra_sockets: ~
>     max_forwards: 10
>     nattest_exception_ips: ~
>     pkg_mem: 16
>     port: 5080
>     security:
>       dos_ban_enable: 'yes'
>       dos_ban_time: 300
>       dos_reqs_density_per_unit: 50
>       dos_sampling_time_unit: 5
>       dos_whitelisted_ips: ~
>       failed_auth_attempts: 3
>       failed_auth_ban_enable: 'yes'
>       failed_auth_ban_time: 3600
>     shm_mem: 466
>     start: 'yes'
>     tcp_children: 8
>     tcp_max_connections: 2048
>     tls:
>       enable: 'yes'
>       port: 5061
>       sslcertfile: '/etc/kamailio/kamailio-selfsigned.pem'
>       sslcertkeyfile: '/etc/kamailio/kamailio-selfsigned.key'
>     udp_children: 8
> 
> Looking further in that file, I have found the settings for the sems sbc component.  I did chance the bindport and turned off a couple options which I did not need (like conferencing) but see nothing in that section about max-forwards.
> 
> sems:
>   bindport: 5060
>   conference:
>     enable: 'no'
>     max_participants: 10
>   highport: 50000
>   lowport: 40001
>   sbc:
>     calltimer_enable: 'yes'
>     calltimer_max: 21600
>     outbound_timeout: 6000
>     sdp_filter:
>       codecs: PCMA,PCMU,telephone-event
>       enable: 'no'
>       mode: whitelist
>     session_timer:
>       enable: 'yes'
>       max_timer: 7200
>       min_timer: 90
>       session_expires: 300
>   vsc:
>     block_override_code: 80
>     cfb_code: 90
>     cfna_code: 93
>     cft_code: 92
>     cfu_code: 72
>     clir_code: 31
>     enable: 'no'
>     reminder_code: 55
>     speedial_code: 50
>     voicemail_number: 2000
>   xmlrpcport: 8090
> 
> Thanks,
> Larry
> 
> From: Kevin Masse [mailto:kmasse at questblue.com]
> Sent: Wednesday, January 08, 2014 1:20 PM
> To: Schaefer, Larry; spce-user at lists.sipwise.com
> Subject: RE: [Spce-user] Missing Max-Forwards Header
> 
> Good afternoon Larry, take a look in your /etc/ngcp-config/config.yml 
> file around line 60 +
> 
> You should have something like this:   max_forwards=70
> 
> kamailio:
>   lb:
>     b2buas:
>       - sip\:127.0.0.1\:5080
>     extra_sockets: ~
>     max_forwards: 70
>     pkg_mem: 16
>     port: 5060
>     proxies:
>       - sip\:127.0.0.1\:5062
> 
> 
> See if that will do away with the error.  I do see in your example 
> below in RED Max-Forwards: 70 but lets verify the config.yml I should 
> also mention my information is related to 2.8
> 
> Kevin
> 
> 
> 
> From: 
> spce-user-bounces at lists.sipwise.com<mailto:spce-user-bounces at lists.sip
> wise.com> [mailto:spce-user-bounces at lists.sipwise.com] On Behalf Of 
> Schaefer, Larry
> Sent: Wednesday, January 08, 2014 2:22 PM
> To: spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>
> Subject: [Spce-user] Missing Max-Forwards Header
> 
> Hello... I am just getting started using SEMS with SBC application.  I am seeing an issue where after I hang up a call, the BYE being sent to my SIP application server does not contain a Max-Forwards header.  This causes my SIP stack throw the following error:  "Missing a required header : Max-Forwards".
> 
> The BYE message going into the SBC has an Max-Forwards, but when it leaves the SBC, it does not.  The logs below are from the sems.log file that show the messages I am seeing.  The final message is the one that I am having an issue with.
> 
> Original Invite to SBC:
> 
> Jan  8 19:08:13 sipwise sems[12819]: [#7fe230676700] [run, 
> udp_trsp.cpp:213] DEBUG: vv M [|] u recvd msg via UDP 
> vv#012--++--#012INVITE sip:17193860006 at 10.81.224.232 
> SIP/2.0#015#012Via: SIP/2.0/UDP 
> 10.2.62.78:44912;branch=z9hG4bK-d8754z-4058c4102839a274-1---d8754z-;rp
> ort#015#012Max-Forwards: 70#015#012Contact: 
> <sip:3333 at 10.2.62.78:44912>#015#012To: 
> "100"<sip:17193860006 at 10.81.224.232>#015#012From: 
> "3333"<sip:3333 at 10.2.62.78>;tag=d6147351#015#012Call-ID: 
> MjNhZDViYTRmZTdiNWQwODc1NGU4MGU5YTQwOTllZTE.#015#012CSeq: 1 
> INVITE#015#012Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, 
> MESSAGE, SUBSCRIBE, INFO#015#012Content-Type: 
> application/sdp#015#012User-Agent: eyeBeam release 1105z stamp 
> 59031#015#012Content-Length: 180#015#012#015#012v=0#015#012o=- 9 2 IN 
> IP4 10.2.62.78#015#012s=CounterPath eyeBeam 1.5#015#012c=IN IP4 
> 10.2.62.78#015#012t=0 0#015#012m=audio 55426 RTP/AVP 0 
> 101#015#012a=fmtp:101 0-15#015#012a=rtpmap:101 
> telephone-event/8000#015#012a=sendrecv#015#012--++--
> 
> New Invite from SBC to my SIP Server:
> 
> Jan  8 19:08:13 sipwise sems[12819]: [#7fe231c8c700] [send, 
> transport.cpp:98] DEBUG: send  msg#012--++--#012INVITE 
> sip:17193860006 at 10.81.224.232 SIP/2.0#015#012Via: SIP/2.0/UDP 
> 10.81.224.232;branch=z9hG4bKCSNunal9;rport#015#012From: "3333" 
> <sip:3333 at 10.2.62.78>;tag=3221B159-52CDA21D000EE81D-31D8D700#015#012To
> : "100"<sip:17193860006 at 10.81.224.232>#015#012CSeq: 10 
> INVITE#015#012Call-ID: 
> MjNhZDViYTRmZTdiNWQwODc1NGU4MGU5YTQwOTllZTE._leg2#015#012Contact: 
> <sip:10.81.224.232:5060>#015#012Max-Forwards: 70#015#012Allow: INVITE, 
> ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, 
> INFO#015#012User-Agent: eyeBeam release 1105z stamp 
> 59031#015#012P-Source-IP: 10.2.62.78#015#012P-Source-Port: 
> 44912#015#012Content-Type: application/sdp#015#012Content-Length: 
> 166#015#012#015#012v=0#015#012o=- 9 2 IN IP4 
> 10.2.62.78#015#012s=CounterPath eyeBeam 1.5#015#012c=IN IP4 
> 10.81.224.232#015#012t=0 0#015#012m=audio 40002 RTP/AVP 0 
> 101#015#012a=rtpmap:101 telephone-event/8000#015#012a=sendrec
 v#015#01
 2--++--
> 
> Bye sent to SBC:
> 
> Jan  8 19:08:18 sipwise sems[12819]: [#7fe230676700] [run, 
> udp_trsp.cpp:213] DEBUG: vv M [|] u recvd msg via UDP 
> vv#012--++--#012BYE sip:17193860006 at 10.81.224.232:5060 
> SIP/2.0#015#012Via: SIP/2.0/UDP 
> 10.2.62.78:44912;branch=z9hG4bK-d8754z-7b597f277435f31e-1---d8754z-;rp
> ort#015#012Max-Forwards: 70#015#012Contact: 
> <sip:3333 at 10.2.62.78:44912>#015#012To: 
> "100"<sip:17193860006 at 10.81.224.232>;tag=7E3767AC-52CDA21D000EE063-306
> 76700#015#012From: 
> "3333"<sip:3333 at 10.2.62.78>;tag=d6147351#015#012Call-ID: 
> MjNhZDViYTRmZTdiNWQwODc1NGU4MGU5YTQwOTllZTE.#015#012CSeq: 2 
> BYE#015#012User-Agent: eyeBeam release 1105z stamp 
> 59031#015#012Reason: SIP;description="User Hung 
> Up"#015#012Content-Length: 0#015#012#015#012--++--
> 
> Bye sent to my SIP server (no Max-Forwards header):
> 
> Jan  8 19:08:18 sipwise sems[12819]: [#7fe231c8c700] [send, 
> transport.cpp:98] DEBUG: send  msg#012--++--#012BYE 
> sip:17193860006 at 10.2.62.78 SIP/2.0#015#012Via: SIP/2.0/UDP 
> 10.81.224.232;branch=z9hG4bKBQ3b.aXk;rport#015#012From: "3333" 
> <sip:3333 at 10.2.62.78>;tag=3221B159-52CDA21D000EE81D-31D8D700#015#012To
> : "100"<sip:17193860006 at 10.81.224.232>;tag=367319031#015#012CSeq: 11 
> BYE#015#012Call-ID: 
> MjNhZDViYTRmZTdiNWQwODc1NGU4MGU5YTQwOTllZTE._leg2#015#012Content-Lengt
> h: 0#015#012#015#012--++--
> 
> Is there anything I am doing wrong?  I have been searching, but not found any settings that seem to deal with Max-Forwards.
> 
> Thanks,
> Larry Schaefer
> 
 
 
 
 



More information about the Spce-user mailing list