Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP headers in Source Numbers

Status
Not open for further replies.

CyMac6poD

Programmer
Jun 15, 2011
17
UA
Good day
first of all - my situation:
AVAYA IPO R7.0(12) and SIP trunk.
The problem is - outgoing call works perfectly well, but incoming calls disconnects. call come to my PBX, but in the moment of answer providers side give me BYE with Reason: SIP;text="SSF00159L00761 Session Timer Check Message Failed". i think this happens because provider Required:timer, but my IPO only Supported:timer.
My question is - is there some source numbers command to operate SIP Headers and replace Supported:timer to Required:timer

 
I dont think there is.

is the provider Avaya approved and tested?

If not, there wont be any documentation so its going to be a bit of trial and error.

ACSS - SME
General Geek

1832163.png
 
about provider i can't say. but IPO R5 at another client works fine with this provider. The difference is that IPO R5 communicate with SIP with registration, and this IPO R7 works without registration. I don't know, but is there any possibility to edit SIP headers from IPO another than by Source Numbers?
 
Then use registration.
This is still there in 7.0 :)


BAZINGA!

I'm not insane, my mother had me tested!
 
Check the SIP URI, try Use Authentication Name for PAI;

PAI: Default = None. Software level = 6.1
Select whether the PAI should be set and if so, the source of the value to use in the PAI field. The value can either be entered manually or one of the following options can be selected.

· None
Do not use the PAI field.

· Use Authentication Name: Software level = 4.0 to 5.0.
Use the appropriate Authentication Name on the SIP Line tab as indicated by the Registration setting below.

· Use Credentials User Name: Software level = 6.0+.
Use the User Name from the SIP Credentials entry used for the call.

· Use Internal Data
Use the SIP Name value from the User | SIP tab of the user making the call. IP Office 6.0: The system can also use SIP URI information configured for a hunt group (Hunt Group | SIP) or for the voicemail (System | Voicemail).



Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
registration can't be used.
About PAI. At this time Use Credential User Name. Tried all other options - no results.
Provider has Huawei SoftX3000. They tried to solve this problem from their side. Asked help from China. Waiting for answers. that's all at the moment :(
 
I dont get the point here:
if the provider has a message Required:timer and IPO replies with supported:timer then there is no problem here as IPO tells the provider it is supporting the required timer option.
There must be another reason for the call to disconnect upon answering the call, most likely it is related to a codec mismatch or unsupported credentials/options between the two.
Catch a SIP trace with monitor of the events covering the disconnect of the call and post it here, maybe we can help you out.

If it ain't dutch it ain't much
 
I'll post trace tomorrow. but i read it many times and think that headers is only reason.
recalling one more time - when IPO initiate SIP session all works. I think this headers are some kind of soft and hard requirement. So when initiating side give Supported(soft requirement) and corresponding side confirms with Require(hard requirement) it works. But if the initiating side give Require and corresponding side give Supported it doesn't satisfy initiating side and than it ends the call with BYE.
 
Provider has changed his header and it doesn't work! The problem is still the same. So I don't know what to do now. There is a monitor log for incoming call. Sorry for the dimensions of message.


********** Warning: Logging to Screen Started **********
175530204mS SIP Rx: UDP 193.xxx.xxx.219:5060 -> 94.xxx.xxx.230:5060
OPTIONS sip:94.xxx.xxx.230:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKk8c7vkl78k7ejbe8eilxeyuyv
Call-ID: khvilhulyccnjhuvohhbioc7hncvvkk8@SE2000
From: <sip:SBC@193.xxx.xxx.219;user=phone>;tag=ceyu8ukx
To: <sip:94.xxx.xxx.230;user=phone>
CSeq: 1 OPTIONS
Max-Forwards: 70
Content-Length: 0

175530207mS SIP Tx: UDP 94.xxx.xxx.230:5060 -> 193.xxx.xxx.219:5060
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKk8c7vkl78k7ejbe8eilxeyuyv
From: <sip:SBC@193.xxx.xxx.219;user=phone>;tag=ceyu8ukx
To: <sip:94.xxx.xxx.230;user=phone>;tag=cd3b92b7b5f40e10
Call-ID: khvilhulyccnjhuvohhbioc7hncvvkk8@SE2000
CSeq: 1 OPTIONS
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Content-Type: application/sdp
Content-Length: 232

v=0
o=UserA 1132038749 995177595 IN IP4 0.0.0.0
s=Session SDP
c=IN IP4 0.0.0.0
t=0 0
m=audio 8000 RTP/AVP 18 8 0 4
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:4 G723/16000
175530212mS SIP Rx: UDP 193.xxx.xxx.219:5060 -> 94.xxx.xxx.230:5060
INVITE sip:57xxxxxx21@94.xxx.xxx.230:5060;user=phone SIP/2.0
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKoxoynebvicin7k8oo77yohxul
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>
CSeq: 1 INVITE
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,SUBSCRIBE,NOTIFY,UPDATE,MESSAGE,REFER
Max-Forwards: 70
Supported: 100rel,timer
User-Agent: Huawei SoftX3000 V300R010
Session-Expires: 300
Min-SE: 90
Contact: <sip:50xxxxxx46@193.xxx.xxx.219:5060;user=phone>
Content-Length: 338
Content-Type: application/sdp

v=0
o=HuaweiSoftX3000 3799071 3799071 IN IP4 193.xxx.xxx.219
s=Sip Call
c=IN IP4 193.xxx.xxx.219
t=0 0
m=audio 14182 RTP/AVP 8 0 18 4 2 97
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=rtpmap:4 G723/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:97 telephone-event/8000
a=ptime:20
a=fmtp:97 0-15
a=fmtp:18 annexb=no
175530216mS CMCallEvt: 0.1303.0 -1 BaseEP: NEW CMEndpoint f5539220 TOTAL NOW=1 CALL_LIST=0
175530218mS SIP Tx: UDP 94.xxx.xxx.230:5060 -> 193.xxx.xxx.219:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKoxoynebvicin7k8oo77yohxul
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
CSeq: 1 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
Content-Length: 0

175530221mS CMCallEvt: CREATE CALL:29 (f54835e4)
175530221mS CMCallEvt: 0.1304.0 -1 BaseEP: NEW CMEndpoint f54821d0 TOTAL NOW=2 CALL_LIST=0
175530223mS CMLineRx: v=0
CMSetup
Line: type=SIPLine 17 Call: lid=17 id=1303 in=1
Called[57xxxxxx21] Type=Default (100) Reason=CMDRdirect SndComp Calling[50xxxxxx46@193.xxx.xxx.219] Type=Unknown Plan=Default
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
IE CMIEFastStartInfoData (6)
IE CMIEMediaWaitForConnect (16) CMIEMediaWaitForConnect
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=50xxxxxx46@193.xxx.xxx.219
IE CMIEDeviceDetail (231) LOCALE=rus HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1303 ipaddr=192.168.93.200 apps=0
175530223mS CD: CALL: 17.1303.1 BState=Idle Cut=1 Music=0.0 Aend="Line 17" (0.0) Bend="" [] (0.0) CalledNum=57xxxxxx21 () CallingNum=50xxxxxx46@193.xxx.xxx.219 () Internal=0 Time=2 AState=Idle
175530223mS CMCallEvt: 17.1303.1 29 SIPTrunk Endpoint: StateChange: END=A CMCSIdle->CMCSDialInitiated
175530224mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: LOOKUP CALL ROUTE: type=100 called_party=57xxxxxx21 sub= calling=50xxxxxx46@193.xxx.xxx.219 dir=in complete=1 ses=0
175530224mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: SET BESTMATCH: length 9 vs -1 match=57xxxxxx21 dest=2001
175530224mS CMCallEvt: Priority hike: call 29 priority 0->1
175530224mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: LOOKUP ICR: DDI=57xxxxxx21 CGPN=50xxxxxx46@193.xxx.xxx.219 (Destination 2001 ) => CDPN=2001
175530224mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: ADD TARGET (N): number=2001 type=100 depth=1 nobar=1 setorig=1 ses=0
175530225mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: SET USER: ????????? orig=1
175530225mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: ADD USER: ????????? depth=2 disallow_cw=0 dnd=0 real_call=1 group_call=0 type(CMNTypeDefault) incl(0x0) excpt(0x0), allow_redir(1) remote=00000000
175530225mS CMCallEvt: 0.1305.0 -1 BaseEP: NEW CMEndpoint f5483a40 TOTAL NOW=3 CALL_LIST=1
175530226mS CMCallEvt: 0.1305.0 -1 ?????????.-1: NEW CMExtnEndpoint f5483a40, Name=?????????, Extn=2001, Phys Extn=2001
175530227mS CMTARGET: 251.1305.0 29 ?????????.0: ADD PRIMARY
175530227mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: INITIAL TARGETING SUCCEEDED
175530227mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: GetNoAnswerTimer:15
175530228mS CMCallEvt: 17.1303.1 29 SIPTrunk Endpoint: StateChange: END=A CMCSDialInitiated->CMCSDialled
175530229mS CMLineTx: v=0
CMProceeding
Line: type=SIPLine 17 Call: lid=17 id=1303 in=1
175530229mS CMCallEvt: 0.1304.0 29 TargetingEP: StateChange: END=B CMCSIdle->CMCSOffering
175530230mS CMCallEvt: 251.1305.0 29 ?????????.0: StateChange: END=T CMCSIdle->CMCSOffering
175530231mS CMExtnEvt: ?????????: CMExtnHandler::SetCurrent( id: 0->1305 )
175530231mS CMExtnTx: v=2001, p1=0
CMSetup
Line: type=IPLine 250 Call: lid=251 id=1305 in=0
Called[2001] Type=Default (100) Reason=CMDRdirect SndComp Calling[50xxxxxx46@193.xxx.xxx.219] Type=Unknown Plan=Default
BC: CMTC=Speech CMTM=Circuit CMTR=64 CMST=Default CMU1=ALaw
IE CMIEMediaWaitForConnect (16) CMIEMediaWaitForConnect
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=50xxxxxx46@193.xxx.xxx.219
IE CMIEDeviceDetail (231) LOCALE=rus HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1303 ipaddr=192.168.93.200 apps=0
IE CMIECalledPartyName (224)(Type=CMNameDefault) name=?????????
IE CMIECalledPartyKName (225)(Type=CMNameDefault) name=Test Uzver
IE CMIEIcrPriorityDetail (239) Priority = 1
IE CMIEDIDNumber (245)(P:100 S:100 T:100 N:100 R:4) number=57xxxxxx21
IE CMIEMohSourceId (247) MOH Source = 1
IE CMIEFastStartInfoData (6)
IE CMIECallSignalChannelData (8) unknown
Display [50xxxxxx46>?????????]
Timed: 17/06/11 14:21
Locale: rus
175530232mS CMExtnRx: v=2001, p1=0
CMAlerting
Line: type=IPLine 250 Call: lid=251 id=1305 in=0
175530232mS CMCallEvt: 251.1305.0 29 ?????????.0: StateChange: END=T CMCSOffering->CMCSRinging
175530232mS CMExtnEvt: v=1 State, new=Ringing old=Idle,0,0,?????????
175530232mS CMCallEvt: 0.1304.0 29 TargetingEP: StateChange: END=B CMCSOffering->CMCSRinging
175530233mS CMCallEvt: 17.1303.1 29 SIPTrunk Endpoint: StateChange: END=A CMCSDialled->CMCSRingBack
175530234mS CMLineTx: v=0
CMAlerting
Line: type=SIPLine 17 Call: lid=17 id=1303 in=1
IE CMIERespondingPartyName (228)(Type=CMNameDefault) name=?????????
IE CMIERespondingPartyKName (229)(Type=CMNameDefault) name=Test Uzver
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=2001
IE CMIEDeviceDetail (231) LOCALE=rus HW=15 VER=7 class=CMDeviceH323Phone type=88 number=8000 channel=0 rx_gain=32 tx_gain=32 ep_callid=1305 ipaddr=192.168.93.200 apps=0
175530235mS SIP Tx: UDP 94.xxx.xxx.230:5060 -> 193.xxx.xxx.219:5060
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKoxoynebvicin7k8oo77yohxul
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
CSeq: 1 INVITE
Contact: "57xxxxxx21" <sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
P-Asserted-Identity: <sip:57xxxxxx21@94.xxx.xxx.230:5060>
Supported: timer
Content-Length: 0

175530371mS CD: CALL: 17.1303.1 BState=Ringing Cut=1 Music=0.0 Aend="Line 17" (0.0) Bend="?????????(2001)" [?????????(2001)] (0.0) CalledNum=2001 (?????????) CallingNum=50xxxxxx46@193.xxx.xxx.219 () Internal=0 Time=150 AState=Ringing
175530528mS RES: Fri 17/6/2011 14:21:32 FreeMem=67071656(2) CMMsg=5 (5) Buff=200 960 1000 7479 3 Links=1099
175530528mS RES2: IP 500 V2 7.0(12) Tasks=38 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=56 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
175533844mS CMExtnRx: v=2001, p1=0
CMConnect
Line: type=IPLine 250 Call: lid=251 id=1305 in=0
IE CMIEFastStartInfoData (6)
IE CMIEFastStartInfoData (6)
175533844mS CMCallEvt: 251.1305.0 29 ?????????.0: StateChange: END=T CMCSRinging->CMCSConnReq
175533844mS CMCallEvt: 0.1304.0 29 TargetingEP: RequestEnd 251.1305.0 29 ?????????.0
175533845mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: CancelTimer CMTCCoverageTimeout
175533845mS CMCallEvt: 0.1304.0 -1 BaseEP: DELETE CMEndpoint f54821d0 TOTAL NOW=2 CALL_LIST=1
175533845mS CMExtnEvt: v=1 State, new=Connected old=Ringing,0,0,?????????
175533846mS CMCallEvt: 17.1303.1 29 SIPTrunk Endpoint: StateChange: END=A CMCSRingBack->CMCSOGConnReq
175533850mS CMLineTx: v=0
CMConnect
Line: type=SIPLine 17 Call: lid=17 id=1303 in=1
IE CMIEFastStartInfoData (6)
IE CMIERespondingPartyName (228)(Type=CMNameDefault) name=?????????
IE CMIERespondingPartyKName (229)(Type=CMNameDefault) name=Test Uzver
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:101 N:100 R:4) number=2001
IE CMIEDeviceDetail (231) LOCALE=rus HW=15 VER=7 class=CMDeviceH323Phone type=88 number=8000 channel=0 rx_gain=32 tx_gain=32 ep_callid=1305 ipaddr=192.168.93.200 apps=0
175533852mS SIP Tx: UDP 94.xxx.xxx.230:5060 -> 193.xxx.xxx.219:5060
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKoxoynebvicin7k8oo77yohxul
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
CSeq: 1 INVITE
Contact: "57xxxxxx21" <sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
P-Asserted-Identity: <sip:57xxxxxx21@94.xxx.xxx.230:5060>
Supported: timer
Min-SE: 300
Session-Expires: 300;refresher=uac
Content-Type: application/sdp
Content-Length: 228

v=0
o=UserA 3403314180 2382925321 IN IP4 94.xxx.xxx.230
s=Session SDP
c=IN IP4 94.xxx.xxx.230
t=0 0
m=audio 49156 RTP/AVP 18 97
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:97 telephone-event/8000
a=fmtp:97 0-15
175533854mS CMExtnTx: v=2001, p1=0
CMFacility
Line: type=IPLine 250 Call: lid=251 id=1305 in=0
Timed: 17/06/11 14:21
175533856mS CD: CALL: 17.1303.1 BState=Connected Cut=3 Music=0.0 Aend="Line 17" (0.0) Bend="?????????(2001)" [?????????(2001)] (0.0) CalledNum=2001 (?????????) CallingNum=50xxxxxx46@193.xxx.xxx.219 () Internal=0 Time=3635 AState=Connected
175533857mS CMMap: PCG::MapBChan pcp[364]b0r1 cp_b 0 other_cp_b 0 type CGTypeSimple
175533858mS H323Evt: SetRfc2833 (1): rx payload 97 tx payload 97
175533858mS CMMap: PCG::MapBChan pcp[363]b0r1 cp_b 0 other_cp_b 0 type CGTypeSimple
175533902mS SIP Rx: UDP 193.xxx.xxx.219:5060 -> 94.xxx.xxx.230:5060
ACK sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bK77unbhnil8oocc8lkkje8xy7k
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0

175533904mS CMLineRx: v=0
CMConnectAck
Line: type=SIPLine 17 Call: lid=17 id=1303 in=1
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=50xxxxxx46@193.xxx.xxx.219
IE CMIEDeviceDetail (231) LOCALE=rus HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1303 ipaddr=192.168.93.200 apps=0
175533904mS CMCallEvt: 17.1303.1 29 SIPTrunk Endpoint: StateChange: END=A CMCSOGConnReq->CMCSConnected
175533905mS CMTARGET: 17.1303.1 29 SIPTrunk Endpoint: ~CMTargetHandler f547c670 ep f5539220
175533906mS CMCallEvt: 251.1305.0 29 ?????????.0: StateChange: END=B CMCSConnReq->CMCSConnected
175533907mS CMExtnTx: v=2001, p1=0
CMConnectAck
Line: type=IPLine 250 Call: lid=251 id=1305 in=0
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=50xxxxxx46@193.xxx.xxx.219
IE CMIEDeviceDetail (231) LOCALE=rus HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1303 ipaddr=192.168.93.200 apps=0
Timed: 17/06/11 14:21
175533907mS CMExtnTx: v=2001, p1=8000
CMFacility
Line: type=IPLine 250 Call: lid=251 id=1 in=1
IE CMIEFastStartInfoData (6)
175533908mS SIP Rx: UDP 193.xxx.xxx.219:5060 -> 94.xxx.xxx.230:5060
BYE sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKyee7bxbci8hxbjcke7xchcche
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
CSeq: 2 BYE
Max-Forwards: 70
Reason: SIP;text="SSF00159L00761 Session Timer Check Message Failed"
Content-Length: 0

175533911mS SIP Tx: UDP 94.xxx.xxx.230:5060 -> 193.xxx.xxx.219:5060
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKyee7bxbci8hxbjcke7xchcche
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
CSeq: 2 BYE
Supported: timer
Content-Length: 0

175533912mS CMLineRx: v=0
CMReleaseComp
Line: type=SIPLine 17 Call: lid=17 id=1303 in=1
IE CMIERespondingPartyNumber (230)(P:100 S:100 T:0 N:100 R:4) number=50xxxxxx46@193.xxx.xxx.219
IE CMIEDeviceDetail (231) LOCALE=rus HW=15 VER=7 class=CMDeviceSIPTrunk type=0 number=17 channel=1 rx_gain=32 tx_gain=32 ep_callid=1303 ipaddr=192.168.93.200 apps=0
Cause=16, Normal call clearing
175533912mS CMCallEvt: 17.1303.1 29 SIPTrunk Endpoint: StateChange: END=A CMCSConnected->CMCSCompleted
175533914mS CMExtnTx: v=2001, p1=0
CMFacility
Line: type=IPLine 250 Call: lid=251 id=1305 in=0
IE CMIEFastStartInfoData (6)
Timed: 17/06/11 14:21
175533914mS CMExtnTx: v=2001, p1=8000
CMFacility
Line: type=IPLine 250 Call: lid=251 id=1 in=1
IE CMIEFastStartInfoData (6)
175533916mS CMLOGGING: CALL:2011/06/1714:21,00:00:01,003,50xxxxxx46@193.xxx.xxx.219,I,2001,57xxxxxx21,,,,0,,""n/a,0
175533916mS CD: CALL: 17.1303.1 BState=Connected Cut=2 Music=0.0 Aend="Line 17" (0.0) Bend="?????????(2001)" [?????????(2001)] (0.0) CalledNum=2001 (?????????) CallingNum=50xxxxxx46@193.xxx.xxx.219 () Internal=0 Time=3695 AState=Idle
175533916mS CD: CALL: 17.1303.1 Deleted
175533917mS CMCallEvt: 17.1303.1 -1 SIPTrunk Endpoint: StateChange: END=X CMCSCompleted->CMCSDelete
175533918mS CMExtnEvt: ?????????: CALL LOST (CMCauseNormal)
175533918mS CMExtnEvt: ?????????: Extn(2001) Calling Party Number(50xxxxxx46@193.xxx.xxx.219) Type(CMNTypeUnknown)
175533919mS CMCallEvt: 251.1305.0 -1 ?????????.0: StateChange: END=X CMCSConnected->CMCSCompletedTone
175533921mS CMExtnTx: v=2001, p1=0
CMFacility
Line: type=IPLine 250 Call: lid=251 id=1305 in=0
IE CMIEFastStartInfoData (6)
Timed: 17/06/11 14:21
175533921mS CMExtnTx: v=2001, p1=8000
CMFacility
Line: type=IPLine 250 Call: lid=251 id=1 in=1
IE CMIEFastStartInfoData (6)
175533921mS CMExtnEvt: v=1 State, new=CMESCompleted old=Connected,0,0,?????????
175533922mS CMCallEvt: END CALL:29 (f54835e4)
175533923mS CMCallEvt: 17.1303.1 -1 BaseEP: DELETE CMEndpoint f5539220 TOTAL NOW=1 CALL_LIST=0
175533924mS CMMap: PCG::UnmapBChan pcp[364]b0r1 cp_b 0 other_cp_b 0
175533925mS CMMap: PCG::UnmapBChan pcp[363]b0r1 cp_b 0 other_cp_b 0
175533925mS CMMap: PCG::AddToneGenerator g B1[4] for cp[364]b0r1 append pcp[365]b0r1 (total 1)
175533925mS CMMap: PlatformConnectionAudioSAP::ConnectVoice pcp[365]b0r1 Configure 0.0
175533925mS CMMap: PlatformConnectionAudioSAP::ConnectVoice pcp[365]b0r1 ConnectIndication 0.0
175533925mS CMMap: a=0.0 b=0.0 pcp[364]b0r1 RTPB1
175533926mS H323Evt: RTP(END): 94.xxx.xxx.230/49156 193.xxx.xxx.219/14182 CODEC=G729A8K(6) PKTSZ=20 RFC2833=on AGE=68 SENT=0 RECV=0 RTdelay=0 jitter=0 loss=0 remotejitter=0 remoteloss=0
175534924mS H323Evt: RTP(50t): 192.168.93.200/49152 192.168.93.203/49296 CODEC=G729A8K(6) PKTSZ=20 RFC2833=off AGE=1067 SENT=50 (avg size=20) RECV=39 (avg size=20)

********** Warning: Logging to Screen Stopped **********
 
On the SIP LINE > SIP Credentials tab ; the expiry timer is it set to 3? That's 3 minutes, put the on 60 or so.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
It is related to the timer.

IP Office responds correct to the Huwaei acking to accept the timer (1st message)and assume the UAC (the Huwaei) to control the timer.
The Huwaei does not ACK that (2nd message) with a "Session Expires: xxx" message which is madatory so IPO refuses the connection (3th message) stating that the "Session Timer Check Message Failed".

IPO responds according to RFC 2026 document.


SIP/2.0 200 Ok
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKoxoynebvicin7k8oo77yohxul
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
CSeq: 1 INVITE
Contact: "57xxxxxx21" <sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
P-Asserted-Identity: <sip:57xxxxxx21@94.xxx.xxx.230:5060>
Supported: timer
Min-SE: 300
Session-Expires: 300;refresher=uac

Content-Type: application/sdp
Content-Length: 228
v=0
o=UserA 3403314180 2382925321 IN IP4 94.xxx.xxx.230
s=Session SDP
c=IN IP4 94.xxx.xxx.230
t=0 0
m=audio 49156 RTP/AVP 18 97
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:97 telephone-event/8000
a=fmtp:97 0-15


175533902mS SIP Rx: UDP 193.xxx.xxx.219:5060 -> 94.xxx.xxx.230:5060
ACK sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bK77unbhnil8oocc8lkkje8xy7k
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
CSeq: 1 ACK
Max-Forwards: 70
Content-Length: 0

175533908mS SIP Rx: UDP 193.xxx.xxx.219:5060 -> 94.xxx.xxx.230:5060
BYE sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKyee7bxbci8hxbjcke7xchcche
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
CSeq: 2 BYE
Max-Forwards: 70
Reason: SIP;text="SSF00159L00761 Session Timer Check Message Failed"
Content-Length: 0

If it ain't dutch it ain't much
 
Addendum :
It is the Huwaei disconnecting as IPO does not respond to the Huwaei as it is waiting for a ack on the timer message and the Huwaei does not do that.

Solution:
Use a registrated line, set up a SIP phone on the ipo with registration or place a SIP converter in between ( Session Border Controller ).

If it ain't dutch it ain't much
 
Try changing the refer from auto to disabled.


BAZINGA!

I'm not insane, my mother had me tested!
 
I understand about IPO don't respond for timer requirement, but I'm confused of that thing - at first INVITE:

User-Agent: Huawei SoftX3000 V300R010
Session-Expires: 300
Min-SE: 90

and than IPO changes this timers to

175533852mS SIP Tx: UDP 94.xxx.xxx.230:5060 -> 193.xxx.xxx.219:5060
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 193.xxx.xxx.219:5060;branch=z9hG4bKoxoynebvicin7k8oo77yohxul
From: <sip:50xxxxxx46@193.xxx.xxx.219;user=phone>;tag=c5da7f8c-CC-25
To: <sip:57xxxxxx21@94.xxx.xxx.230;user=phone>;tag=463a3a3adeb46feb
Call-ID: SBCb957a70a5ebf7d45215a26530de814ea@SoftX3000
CSeq: 1 INVITE
Contact: "57xxxxxx21" <sip:57xxxxxx21@94.xxx.xxx.230:5060;transport=udp>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
P-Asserted-Identity: <sip:57xxxxxx21@94.xxx.xxx.230:5060>
Supported: timer
Min-SE: 300
Session-Expires: 300;refresher=uac


Why does IPO equals this values. Provider changes Session-Expires:1800 and IPO again equals Min-SE to Session-Expires. Is that right?
 
And I repeat that this is incoming call. So UAC is IPO.
 
IPO cannot be a UAC and the HUWAEI is neither so that is the root of your problem.
make a SIP phone on either the ipo or on the huwaei and make a registered connection then it will work.

If it ain't dutch it ain't much
 
I haven't any SIP phones, and Session Border Controllers. Just IPO. And I need this SIP trunk to receive incoming calls. No other options.
 
Then you need to change providers, Avaya test with many providers and create a list of them to save people wasting their money on trunks that are incompatible/rubbish. Use one from the list and you will have no issues like this :)

ACSS (SME)
APSS (SME)


"I'm just off to Hartlepool to buy some exploding trousers
 
No. this is not the right decision. I can't change provider. So i'll continue my attempts to make this work. Some particular questions I'll post here.
Now I'm looking for the way to operate with SIP timers in IPO. Any thought about this topic?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top