BrianCosta
Systems Engineer
Hello ...
I have completed configuring the SIP trunk between Avaya IPOSE 11.1, and NEC, I can call the NEC side with no problems, When the NEC user calls any User on IPOSE, the call is disconnected after 1 minute and 49 sec.
Here is the trace captured form sysmonitor:
UPDATE sip:200@172.16.133.228:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.70.2:5060;rport;branch=z9hG4bK36223039c45150d1995c6f7756b9cbad
From: <sip:3086@172.16.70.2>;tag=d5f3c507f0b6164d
To: "220" <sip:200@172.16.133.228>;tag=178832463135364102741D00
Call-ID: 0214E4AC7A81400000000089@172.16.133.228
CSeq: 2 UPDATE
P-Asserted-Identity: "Yousef Al Shrid" <sip:3086@172.16.70.2:5060>
Contact: "Yousef Al Shrid" <sip:3086@172.16.70.2:5060;transport=tcp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 11.1.1.1.0 build 18
Min-SE: 120
Session-Expires: 120;refresher=uac
Content-Length: 0
13:15:51 1644178232mS CMExtnEvt: Yousef Al Shrid:3086: No user activity
13:15:51 1644178277mS SIP Rx: TCP 172.16.133.228:5060 -> 172.16.70.2:61495
SIP/2.0 422 Session Timer Too Small
Min-SE: 1800
From: <sip:3086@172.16.70.2:5060>;tag=d5f3c507f0b6164d
To: "220"<sip:200@172.16.133.228>;tag=178832463135364102741D00
Call-ID: 0214E4AC7A81400000000089@172.16.133.228
CSeq: 2 UPDATE
Server: NEC SL2100/2.1
Via: SIP/2.0/TCP 172.16.70.2:5060;rport;branch=z9hG4bK36223039c45150d1995c6f7756b9cbad
Content-Length: 0
I noted the following message from the trace:
SIP/2.0 422 Session Timer Too Small
is there something can i do from the IPO side, or it's an NEC issue???
Thanks
I have completed configuring the SIP trunk between Avaya IPOSE 11.1, and NEC, I can call the NEC side with no problems, When the NEC user calls any User on IPOSE, the call is disconnected after 1 minute and 49 sec.
Here is the trace captured form sysmonitor:
UPDATE sip:200@172.16.133.228:5060 SIP/2.0
Via: SIP/2.0/TCP 172.16.70.2:5060;rport;branch=z9hG4bK36223039c45150d1995c6f7756b9cbad
From: <sip:3086@172.16.70.2>;tag=d5f3c507f0b6164d
To: "220" <sip:200@172.16.133.228>;tag=178832463135364102741D00
Call-ID: 0214E4AC7A81400000000089@172.16.133.228
CSeq: 2 UPDATE
P-Asserted-Identity: "Yousef Al Shrid" <sip:3086@172.16.70.2:5060>
Contact: "Yousef Al Shrid" <sip:3086@172.16.70.2:5060;transport=tcp>
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,INFO,NOTIFY,UPDATE
Supported: timer
User-Agent: IP Office 11.1.1.1.0 build 18
Min-SE: 120
Session-Expires: 120;refresher=uac
Content-Length: 0
13:15:51 1644178232mS CMExtnEvt: Yousef Al Shrid:3086: No user activity
13:15:51 1644178277mS SIP Rx: TCP 172.16.133.228:5060 -> 172.16.70.2:61495
SIP/2.0 422 Session Timer Too Small
Min-SE: 1800
From: <sip:3086@172.16.70.2:5060>;tag=d5f3c507f0b6164d
To: "220"<sip:200@172.16.133.228>;tag=178832463135364102741D00
Call-ID: 0214E4AC7A81400000000089@172.16.133.228
CSeq: 2 UPDATE
Server: NEC SL2100/2.1
Via: SIP/2.0/TCP 172.16.70.2:5060;rport;branch=z9hG4bK36223039c45150d1995c6f7756b9cbad
Content-Length: 0
I noted the following message from the trace:
SIP/2.0 422 Session Timer Too Small
is there something can i do from the IPO side, or it's an NEC issue???
Thanks