27 Aug
2018
27 Aug
'18
8:06 a.m.
Hello,
I am working with IMS (ZTE vendor), I want to use SBC in front of IMS
network for some security policy (Hide Topology),
I used SEMS as SBC in this regards, (like what we have in IMS/SEMS in
kamailio by Mr Carsten Bock).
When the Sebscriber want to register, The Register request received by
sems and the forward to IMS(ZTE), But the "503 Service Unavailable" is
received from IMS.
I enable "enable_reg_caching=yes" in register.sbcprofile''s
configuration file in sems.
If i use kamailio, instead of SEMS, The Registration request is done
successfully.In Kamailio i just forward the Register request to
IMS.like this:
route {
if (is_method("REGISTER")) {
$du = "sip:172.23.1.1:5080";
route(RELAY);
}
}
Let me know do the issue is from myself or from IMS(ZTE)?
In the fillowing, I paste all SIP Register signalling. First in
kamailio, second with SEMS.
================Kamailio==================
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5e58 ->
0x4193!] UDP, length 787
E../....@.]...............^XREGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
Max-Forwards: 69
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP>
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.114198 IP (tos 0x0, ttl 255, id 25839, offset 0, flags
[none], proto UDP (17), length 685)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 657
E...d......$..............l.SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipTR9m3KdZ*3-5-16648*daei.3
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com",domain="sip:scscf1.r-kh.com",nonce="f42b36e39bdbb33b51599924b304445a",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
08:20:53.120142 IP (tos 0x10, ttl 64, id 48874, offset 0, flags
[none], proto UDP (17), length 1137)
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5f9a ->
0xcc62!] UDP, length 1109
E..q....@.\V.............]_.REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
Max-Forwards: 69
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP>
To: <sip:+985137054518@r-kh.com;transport=UDP>
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518@r-kh.com",realm="r-kh.com",nonce="f42b36e39bdbb33b51599924b304445a",uri="sip:r-kh.com;transport=UDP",response="9469852a06c01efeabf3a7a5dd1a9f3b",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.203871 IP (tos 0x0, ttl 255, id 25842, offset 0, flags
[none], proto UDP (17), length 1118)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 1090
E..^d......p.............J.5SIP/2.0 200 OK
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipjRydzgMa*3-5-16648*daej.3
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Contact:
<sip:+985137054518@192.168.122.1:64407;transport=UDP;rinstance=e664e178fc12691e>;expires=1800
Contact:
<sip:ZTEAGCF000f425704be720000@agcf2.r-kh.com:5079;appid=2-7;UserRegInfo=002-02-00-0b80-04-172.30.48.143;BACaddr=172.30.48.143;BACport=2944>;expires=1800;+sip.instance="<urn:uuid:172.30.35.41-000>";reg-id=1
P-Associated-URI: <tel:+985137054518>
P-Associated-URI: <sip:+985137054518@r-kh.com>
Date: Sat, 25 Aug 2018 12:25:17 GMT
Authentication-Info:
nextnonce="00cfbd64b136c12a4e27b67fd28d19fb",qop=auth,rspauth="91ca956c5eb6ee9f1934e2e770750077",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001
Content-Length: 0
============================SEMS========================
172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5e16 ->
0xe11e!] UDP, length 721
E...C.@.@.................^.
REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bK~0uk0ahN;rport
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
To: <sip:+985137054518@r-kh.com;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.790414 IP (tos 0x0, ttl 255, id 35790, offset 0, flags
[none], proto UDP (17), length 593)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 565
E..Q.....................=..SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bK~0uk0ahN
To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipDEmH2AWT*3-5-16648*egei.3
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
CSeq: 10 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com",domain="sip:scscf1.r-kh.com",nonce="179797f920a09d65b5641e5e87df0d8c",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
08:23:32.855067 IP (tos 0x0, ttl 64, id 17364, offset 0, flags [DF],
proto UDP (17), length 1071)
172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5f58 ->
0xf553!] UDP, length 1043
E../C.@.@................._X
REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bKeAfKkaZa;rport
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
To: <sip:+985137054518@r-kh.com;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518@r-kh.com",realm="r-kh.com",nonce="179797f920a09d65b5641e5e87df0d8c",uri="sip:r-kh.com;transport=UDP",response="017efb986e17506a82bb01e8eb136b90",cnonce="3764fd5eb2ea9539d61ec14196a2bf00",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
Allow-Events: presence, kpml
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.860417 IP (tos 0x0, ttl 255, id 35804, offset 0, flags
[none], proto UDP (17), length 508)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 480
E...........................SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bKeAfKkaZa
To:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipxxsD3FR2VG8e9zxR_1dx*1-1-16648*ihad.1
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
CSeq: 10 REGISTER
X-ZTE-Cause: "CSCF-1.1.BC004016-BC004288-0-0.pcscf1.r-kh.com"
Retry-After: 30
Content-Length: 0
--
--Mojtaba Esfandiari.S
27 Aug
27 Aug
2:09 p.m.
Hello,
It's not directly related to your question but keep in mind that SBC
should be put after vendor's/ZTE p-cscf if possible. Otherwise you will
have QoS issues (if Rx is enabled/used) because of rewritten SDP from
SBC/B2BUA.
Regards,
Ivo
On 08/27/2018 08:06 AM, Mojtaba wrote:
Hello,
I am working with IMS (ZTE vendor), I want to use SBC in front of IMS
network for some security policy (Hide Topology),
I used SEMS as SBC in this regards, (like what we have in IMS/SEMS in
kamailio by Mr Carsten Bock).
When the Sebscriber want to register, The Register request received by
sems and the forward to IMS(ZTE), But the "503 Service Unavailable" is
received from IMS.
I enable "enable_reg_caching=yes" in register.sbcprofile''s
configuration file in sems.
If i use kamailio, instead of SEMS, The Registration request is done
successfully.In Kamailio i just forward the Register request to
IMS.like this:
route {
if (is_method("REGISTER")) {
$du = "sip:172.23.1.1:5080";
route(RELAY);
}
}
Let me know do the issue is from myself or from IMS(ZTE)?
In the fillowing, I paste all SIP Register signalling. First in
kamailio, second with SEMS.
================Kamailio==================
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5e58 ->
0x4193!] UDP, length 787
E../....@.]...............^XREGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
Max-Forwards: 69
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP>
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.114198 IP (tos 0x0, ttl 255, id 25839, offset 0, flags
[none], proto UDP (17), length 685)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 657
E...d......$..............l.SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipTR9m3KdZ*3-5-16648*daei.3
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com",domain="sip:scscf1.r-kh.com",nonce="f42b36e39bdbb33b51599924b304445a",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
08:20:53.120142 IP (tos 0x10, ttl 64, id 48874, offset 0, flags
[none], proto UDP (17), length 1137)
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5f9a ->
0xcc62!] UDP, length 1109
E..q....@.\V.............]_.REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
Max-Forwards: 69
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP>
To: <sip:+985137054518@r-kh.com;transport=UDP>
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518@r-kh.com",realm="r-kh.com",nonce="f42b36e39bdbb33b51599924b304445a",uri="sip:r-kh.com;transport=UDP",response="9469852a06c01efeabf3a7a5dd1a9f3b",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.203871 IP (tos 0x0, ttl 255, id 25842, offset 0, flags
[none], proto UDP (17), length 1118)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 1090
E..^d......p.............J.5SIP/2.0 200 OK
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipjRydzgMa*3-5-16648*daej.3
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Contact:
<sip:+985137054518@192.168.122.1:64407;transport=UDP;rinstance=e664e178fc12691e>;expires=1800
Contact:
<sip:ZTEAGCF000f425704be720000@agcf2.r-kh.com:5079;appid=2-7;UserRegInfo=002-02-00-0b80-04-172.30.48.143;BACaddr=172.30.48.143;BACport=2944>;expires=1800;+sip.instance="<urn:uuid:172.30.35.41-000>";reg-id=1
P-Associated-URI: <tel:+985137054518>
P-Associated-URI: <sip:+985137054518@r-kh.com>
Date: Sat, 25 Aug 2018 12:25:17 GMT
Authentication-Info:
nextnonce="00cfbd64b136c12a4e27b67fd28d19fb",qop=auth,rspauth="91ca956c5eb6ee9f1934e2e770750077",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001
Content-Length: 0
============================SEMS========================
172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5e16 ->
0xe11e!] UDP, length 721
E...C.@.@.................^.
REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bK~0uk0ahN;rport
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
To: <sip:+985137054518@r-kh.com;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.790414 IP (tos 0x0, ttl 255, id 35790, offset 0, flags
[none], proto UDP (17), length 593)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 565
E..Q.....................=..SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bK~0uk0ahN
To: <sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipDEmH2AWT*3-5-16648*egei.3
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
CSeq: 10 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com",domain="sip:scscf1.r-kh.com",nonce="179797f920a09d65b5641e5e87df0d8c",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
08:23:32.855067 IP (tos 0x0, ttl 64, id 17364, offset 0, flags [DF],
proto UDP (17), length 1071)
172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5f58 ->
0xf553!] UDP, length 1043
E../C.@.@................._X
REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bKeAfKkaZa;rport
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
To: <sip:+985137054518@r-kh.com;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer, X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518@r-kh.com",realm="r-kh.com",nonce="179797f920a09d65b5641e5e87df0d8c",uri="sip:r-kh.com;transport=UDP",response="017efb986e17506a82bb01e8eb136b90",cnonce="3764fd5eb2ea9539d61ec14196a2bf00",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
Allow-Events: presence, kpml
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.860417 IP (tos 0x0, ttl 255, id 35804, offset 0, flags
[none], proto UDP (17), length 508)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 480
E...........................SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bKeAfKkaZa
To:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=ztesipxxsD3FR2VG8e9zxR_1dx*1-1-16648*ihad.1
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
CSeq: 10 REGISTER
X-ZTE-Cause: "CSCF-1.1.BC004016-BC004288-0-0.pcscf1.r-kh.com"
Retry-After: 30
Content-Length: 0
4:06 p.m.
Hi, I knew, But i have not access to ZTE's pcscf.
Thank you.
But what about my question?Why the UE could not register via SEMS?
On Mon, 27 Aug 2018 15:40 Ivailo Dobrev, <ivailod(a)telera.eu> wrote:
Hello,
It's not directly related to your question but keep in mind that SBC
should be put after vendor's/ZTE p-cscf if possible. Otherwise you will
have QoS issues (if Rx is enabled/used) because of rewritten SDP from
SBC/B2BUA.
Regards,
Ivo
On 08/27/2018 08:06 AM, Mojtaba wrote:
Hello,
I am working with IMS (ZTE vendor), I want to use SBC in front of IMS
network for some security policy (Hide Topology),
I used SEMS as SBC in this regards, (like what we have in IMS/SEMS in
kamailio by Mr Carsten Bock).
When the Sebscriber want to register, The Register request received by
sems and the forward to IMS(ZTE), But the "503 Service Unavailable" is
received from IMS.
I enable "enable_reg_caching=yes" in register.sbcprofile''s
configuration file in sems.
If i use kamailio, instead of SEMS, The Registration request is done
successfully.In Kamailio i just forward the Register request to
IMS.like this:
route {
if (is_method("REGISTER")) {
$du = "sip:172.23.1.1:5080";
route(RELAY);
}
}
Let me know do the issue is from myself or from IMS(ZTE)?
In the fillowing, I paste all SIP Register signalling. First in
kamailio, second with SEMS.
================Kamailio==================
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5e58 ->
0x4193!] UDP, length 787
E../....@.]...............^XREGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
Max-Forwards: 69
Contact: <sip:+985137054518@192.168.122.1:64407
;rinstance=e664e178fc12691e;transport=UDP>
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.114198 IP (tos 0x0, ttl 255, id 25839, offset 0, flags
[none], proto UDP (17), length 685)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 657
E...d......$..............l.SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
To: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=ztesipTR9m3KdZ*3-5-16648*daei.3
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com",domain="sip:scscf1.r-kh.com
",nonce="f42b36e39bdbb33b51599924b304445a",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
08:20:53.120142 IP (tos 0x10, ttl 64, id 48874, offset 0, flags
[none], proto UDP (17), length 1137)
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5f9a ->
0xcc62!] UDP, length 1109
E..q....@.\V.............]_.REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
Max-Forwards: 69
Contact: <sip:+985137054518@192.168.122.1:64407
;rinstance=e664e178fc12691e;transport=UDP>
To:
<sip:+985137054518@r-kh.com;transport=UDP>
From: <sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518(a)r-kh.com",realm="r-kh.com
",nonce="f42b36e39bdbb33b51599924b304445a",uri="sip:r-kh.com
;transport=UDP",response="9469852a06c01efeabf3a7a5dd1a9f3b",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.203871 IP (tos 0x0, ttl 255, id 25842, offset 0, flags
[none], proto UDP (17), length 1118)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP, length 1090
E..^d......p.............J.5SIP/2.0 200 OK
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
To: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=ztesipjRydzgMa*3-5-16648*daej.3
From:
<sip:+985137054518@r-kh.com;transport=UDP>;tag=5aef0541
Call-ID: ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Contact: <sip:+985137054518@192.168.122.1:64407
;transport=UDP;rinstance=e664e178fc12691e>;expires=1800
Contact:
<sip:ZTEAGCF000f425704be720000@agcf2.r-kh.com:5079
;appid=2-7;UserRegInfo=002-02-00-0b80-04-172.30.48.143;BACaddr=172.30.48.143;BACport=2944>;expires=1800;+sip.instance="<urn:uuid:172.30.35.41-000>";reg-id=1
P-Associated-URI: <tel:+985137054518>
P-Associated-URI: <sip:+985137054518@r-kh.com>
Date: Sat, 25 Aug 2018 12:25:17 GMT
Authentication-Info:
nextnonce="00cfbd64b136c12a4e27b67fd28d19fb",qop=auth,rspauth="91ca956c5eb6ee9f1934e2e770750077",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001
Content-Length: 0
============================SEMS========================
172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5e16 ->
0xe11e!] UDP, length 721
E...C.@.@.................^.
REGISTER sip:r-kh.com SIP/2.0
Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bK~0uk0ahN;rport
From: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
To:
<sip:+985137054518@r-kh.com;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Contact: <sip:+985137054518@192.168.122.1:64407
;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.790414 IP (tos 0x0, ttl 255, id 35790, offset 0, flags
[none], proto UDP (17), length 593)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 565
E..Q.....................=..SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bK~0uk0ahN
To: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=ztesipDEmH2AWT*3-5-16648*egei.3
From: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
CSeq: 10 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com",domain="sip:scscf1.r-kh.com
",nonce="179797f920a09d65b5641e5e87df0d8c",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
>
>
> 08:23:32.855067 IP (tos 0x0, ttl 64, id 17364, offset 0, flags [DF],
> proto UDP (17), length 1071)
> 172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5f58 ->
> 0xf553!] UDP, length 1043
> E../C.@.@................._X
>
> REGISTER sip:r-kh.com SIP/2.0
> Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bKeAfKkaZa;rport
From: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
To:
<sip:+985137054518@r-kh.com;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518(a)r-kh.com",realm="r-kh.com
",nonce="179797f920a09d65b5641e5e87df0d8c",uri="sip:r-kh.com
;transport=UDP",response="017efb986e17506a82bb01e8eb136b90",cnonce="3764fd5eb2ea9539d61ec14196a2bf00",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
Allow-Events: presence, kpml
Contact: <sip:+985137054518@192.168.122.1:64407
;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.860417 IP (tos 0x0, ttl 255, id 35804, offset 0, flags
[none], proto UDP (17), length 508)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP, length 480
E...........................SIP/2.0 503 Service Unavailable
Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bKeAfKkaZa
To: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=ztesipxxsD3FR2VG8e9zxR_1dx*1-1-16648*ihad.1
From: <sip:+985137054518@r-kh.com
;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
CSeq: 10 REGISTER
X-ZTE-Cause: "CSCF-1.1.BC004016-BC004288-0-0.pcscf1.r-kh.com"
Retry-After: 30
Content-Length: 0
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
28 Aug
28 Aug
2:08 p.m.
Maybe it is time to look at ZTE traces/logs.
P.S.
Try to check in docs meaning of X-ZTE-Cause
On 08/27/2018 04:06 PM, Mojtaba wrote:
Hi, I knew, But i have not access to ZTE's pcscf.
Thank you.
But what about my question?Why the UE could not register via SEMS?
On Mon, 27 Aug 2018 15:40 Ivailo Dobrev, <ivailod(a)telera.eu
<mailto:ivailod@telera.eu>> wrote:
Hello,
It's not directly related to your question but keep in mind that SBC
should be put after vendor's/ZTE p-cscf if possible. Otherwise you
will
have QoS issues (if Rx is enabled/used) because of rewritten SDP from
SBC/B2BUA.
Regards,
Ivo
On 08/27/2018 08:06 AM, Mojtaba wrote:
Hello,
I am working with IMS (ZTE vendor), I want to use SBC in front
of IMS
network for some security policy (Hide
Topology),
I used SEMS as SBC in this regards, (like what we have in
IMS/SEMS in
kamailio by Mr Carsten Bock).
When the Sebscriber want to register, The Register request
received by
sems and the forward to IMS(ZTE), But the
"503 Service
Unavailable" is
received from IMS.
I enable "enable_reg_caching=yes" in register.sbcprofile''s
configuration file in sems.
If i use kamailio, instead of SEMS, The Registration request is done
successfully.In Kamailio i just forward the Register request to
IMS.like this:
route {
if (is_method("REGISTER")) {
$du = "sip:172.23.1.1:5080
<http://172.23.1.1:5080>";
route(RELAY);
}
}
Let me know do the issue is from myself or from IMS(ZTE)?
In the fillowing, I paste all SIP Register signalling. First in
kamailio, second with SEMS.
================Kamailio==================
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5e58 ->
0x4193!] UDP, length 787
E../....@.]...............^XREGISTER sip:r-kh.com
<http://r-kh.com>
SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
Max-Forwards: 69
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP>
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=5aef0541
Call-ID:
ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.114198 IP (tos 0x0, ttl 255, id 25839, offset 0, flags
[none], proto UDP (17), length 685)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP,
length 657
> E...d......$..............l.SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bK018b.e091260b1b7395975a2ff1be0b9bec60.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-7c208b9d587de818-1---d8754z-
To: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=ztesipTR9m3KdZ*3-5-16648*daei.3
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=5aef0541
Call-ID:
ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 1 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com <http://r-kh.com>",domain="sip:scscf1.r-kh.com
<http://scscf1.r-kh.com>",nonce="f42b36e39bdbb33b51599924b304445a",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
08:20:53.120142 IP (tos 0x10, ttl 64, id 48874, offset 0, flags
[none], proto UDP (17), length 1137)
172.23.1.252.4080 > 172.23.1.1.5080: [bad udp cksum 0x5f9a ->
0xcc62!] UDP, length 1109
E..q....@.\V.............]_.REGISTER sip:r-kh.com
<http://r-kh.com>
SIP/2.0
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
Max-Forwards: 69
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=e664e178fc12691e;transport=UDP>
To: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=5aef0541
Call-ID:
ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518(a)r-kh.com
<mailto:985137054518@r-kh.com>",realm="r-kh.com
<http://r-kh.com>",nonce="f42b36e39bdbb33b51599924b304445a",uri="sip:r-kh.com
<http://r-kh.com>;transport=UDP",response="9469852a06c01efeabf3a7a5dd1a9f3b",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
Allow-Events: presence, kpml
Content-Length: 0
08:20:53.203871 IP (tos 0x0, ttl 255, id 25842, offset 0, flags
[none], proto UDP (17), length 1118)
172.23.1.1.5080 > 172.23.1.252.4080: [udp sum ok] UDP,
length 1090
> E..^d......p.............J.5SIP/2.0 200 OK
Via: SIP/2.0/UDP
172.23.1.252:4080;branch=z9hG4bKd08b.4d2858f41d496b471c01a28e76190390.0
Via: SIP/2.0/UDP
192.168.122.1:64407;branch=z9hG4bK-d8754z-a4d19146375d56f6-1---d8754z-
To: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=ztesipjRydzgMa*3-5-16648*daej.3
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=5aef0541
Call-ID:
ZWYxMzUzNTQzN2I2MTRiMjE2NWZjMzUzMDFmMDhkOWY.
CSeq: 2 REGISTER
Contact:
<sip:+985137054518@192.168.122.1:64407;transport=UDP;rinstance=e664e178fc12691e>;expires=1800
Contact:
<sip:ZTEAGCF000f425704be720000@agcf2.r-kh.com:5079;appid=2-7;UserRegInfo=002-02-00-0b80-04-172.30.48.143;BACaddr=172.30.48.143;BACport=2944>;expires=1800;+sip.instance="<urn:uuid:172.30.35.41-000>";reg-id=1
P-Associated-URI: <tel:+985137054518>
P-Associated-URI: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>>
Date: Sat, 25 Aug 2018 12:25:17 GMT
Authentication-Info:
nextnonce="00cfbd64b136c12a4e27b67fd28d19fb",qop=auth,rspauth="91ca956c5eb6ee9f1934e2e770750077",cnonce="79d36600575648a1cc7221d8e1b5d53d",nc=00000001
> Content-Length: 0
> ============================SEMS========================
> 172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5e16 ->
> 0xe11e!] UDP, length 721
> E...C.@.@.................^.
>
> REGISTER sip:r-kh.com <http://r-kh.com> SIP/2.0
> Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bK~0uk0ahN;rport
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
To: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
> User-Agent: Z 3.3.25608 r25552
> Allow-Events: presence, kpml
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.790414 IP (tos 0x0, ttl 255, id 35790, offset 0, flags
[none], proto UDP (17), length 593)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP,
length 565
> E..Q.....................=..SIP/2.0 401 Unauthorized
> Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bK~0uk0ahN
To: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=ztesipDEmH2AWT*3-5-16648*egei.3
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=34384541-5B814A44000AE296-4B5F5700
Call-ID: 37B52BC0-5B814A44000AE592-4B5F5700
CSeq: 10 REGISTER
Content-Length: 0
WWW-Authenticate: Digest
realm="r-kh.com <http://r-kh.com>",domain="sip:scscf1.r-kh.com
<http://scscf1.r-kh.com>",nonce="179797f920a09d65b5641e5e87df0d8c",opaque="aW1zLmNvbS5jbg==",stale=TRUE,algorithm=MD5,qop="auth"
>
>
> 08:23:32.855067 IP (tos 0x0, ttl 64, id 17364, offset 0, flags [DF],
> proto UDP (17), length 1071)
> 172.23.1.252.5080 > 172.23.1.1.5080: [bad udp cksum 0x5f58 ->
> 0xf553!] UDP, length 1043
> E../C.@.@................._X
>
> REGISTER sip:r-kh.com <http://r-kh.com> SIP/2.0
> Via: SIP/2.0/UDP 172.23.1.252:5080;branch=z9hG4bKeAfKkaZa;rport
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
To: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>
CSeq: 10 REGISTER
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
Route: <sip:172.23.1.1:5080;lr>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS,
INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, timer,
X-cisco-serviceuri
User-Agent: Z 3.3.25608 r25552
Authorization: Digest
username="+985137054518(a)r-kh.com
<mailto:985137054518@r-kh.com>",realm="r-kh.com
<http://r-kh.com>",nonce="179797f920a09d65b5641e5e87df0d8c",uri="sip:r-kh.com
<http://r-kh.com>;transport=UDP",response="017efb986e17506a82bb01e8eb136b90",cnonce="3764fd5eb2ea9539d61ec14196a2bf00",nc=00000001,qop=auth,algorithm=MD5,opaque="aW1zLmNvbS5jbg=="
> Allow-Events: presence, kpml
Contact:
<sip:+985137054518@192.168.122.1:64407;rinstance=868560f8328d39e9;transport=UDP>;expires=3600
Content-Length: 0
08:23:32.860417 IP (tos 0x0, ttl 255, id 35804, offset 0, flags
[none], proto UDP (17), length 508)
172.23.1.1.5080 > 172.23.1.252.5080: [udp sum ok] UDP,
length 480
> E...........................SIP/2.0 503 Service Unavailable
> Via: SIP/2.0/UDP 172.23.1.252:5080;rport=5080;branch=z9hG4bKeAfKkaZa
To: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=ztesipxxsD3FR2VG8e9zxR_1dx*1-1-16648*ihad.1
From: <sip:+985137054518@r-kh.com
<mailto:sip%3A%2B985137054518@r-kh.com>;transport=UDP>;tag=5A64C27D-5B814A44000CD034-4B6F6700
Call-ID: 5380C97E-5B814A44000CD2A5-4B6F6700
CSeq: 10 REGISTER
X-ZTE-Cause: "CSCF-1.1.BC004016-BC004288-0-0.pcscf1.r-kh.com
<http://CSCF-1.1.BC004016-BC004288-0-0.pcscf1.r-kh.com>"
Retry-After: 30
Content-Length: 0
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
2278
days inactive
2279
days old
3 comments
2 participants
participants (2)
-
Ivailo Dobrev -
Mojtaba