Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [MS-1]----[OpenBSC]--[LCR on Interface bridge and rtp-bridge]-----[yate]----[LCR on Interface bridge and rtp-bridge]--[Openbsc]----[MS-2]
- MS-1 : 0778899201
- MS-2 : 0778899202
- OpenBSC/LCR - 192.168.100.30
- Yate - 192.168.100.25
- LCR
- ===
- 15.03.12 16:58:45.710 CH(15): New call ref LCR<->BSC callref new=0x80000022
- 15.03.12 16:58:45.711 CH(15): Codec negotiation LCR<->BSC bearer capa='given by MS' speech version='AMR given' version='5 given' ignored='Not supported by LCR' version='EFR given' version='Full Rate given' version='Half Rate given'
- 15.03.12 16:58:45.717 CH(15): MNCC_SETUP_IND LCR<->BSC calling number=0778899201 imsi=413011492012312 dialing number=0778899202
- 15.03.12 16:58:45.718 CH(15): MNCC_CALL_PROC_REQ LCR<->BSC progress coding=3 location=1 descr=8
- 15.03.12 16:58:45.718 CH(15): unknown LCR<->BSC
- 15.03.12 16:58:45.722 CH(16): NEW handle handle new=0x948bef8
- 15.03.12 16:58:45.722 CH(16): INVITE from uri=sip:0778899201@192.168.100.30 to uri=sip:0778899202@192.168.100.25 rtp ip=192.168.100.30 port=30026,30027 payload=AMR:96 payload=GSM-EFR:97 payload=GSM:3 payload=GSM-HR:98
- 15.03.12 16:58:45.782 CH(17): Payload received rtp payload=AMR:96 payload=GSM:3 payload=telephone-event:101
- 15.03.12 16:58:45.782 CH(17): NEW handle handle new=0x94913d0
- 15.03.12 16:58:45.782 CH(17): INVITE rtp port=30026 calling present=allowed number=0778899201 dialing number=0778899202 bearer capa=speech mode=circuit
- 15.03.12 16:58:45.794 CH(18): Codec negotiation LCR<->BSC rtp payload='AMR:96 supported' payload='GSM:3 supported'
- 15.03.12 16:58:45.795 CH(18): New call ref LCR<->BSC callref new=0x3
- 15.03.12 16:58:45.795 CH(18): MNCC_SETUP_REQ LCR<->BSC calling type=0 plan=1 present=0 screen=3 number=0778899201 dialing number=0778899202
- 15.03.12 16:58:49.156 CH(18): MNCC_CALL_CONF_IND LCR<->BSC
- 15.03.12 16:58:49.156 CH(18): Codec negotiation LCR<->BSC bearer capa='given by MS' speech version='AMR given' version='EFR given' version='Full Rate given' version='5 given' ignored='Not supported by LCR' version='Half Rate given'
- 15.03.12 16:58:49.156 CH(18): MNCC_LCHAN_MODIFY LCR<->BSC speech version='AMR given' mode 0x41
- 15.03.12 16:58:49.804 CH(18): MNCC_ALERT_IND LCR<->BSC
- 15.03.12 16:58:49.804 CH(17): RESPOND respond value='180 Ringing'
- 15.03.12 16:58:49.824 CH(16): RESPOND respond value=180
- 15.03.12 16:58:49.834 CH(15): MNCC_ALERT_REQ LCR<->BSC progress coding=3 location=1 descr=8
- 15.03.12 16:58:56.285 CH(18): MNCC_SETUP_CNF LCR<->BSC connect number=0778899202 imsi=234109003491209
- 15.03.12 16:58:56.286 CH(18): MNCC_SETUP_COMPL_REQ LCR<->BSC
- 15.03.12 16:58:56.286 CH(18): unknown LCR<->BSC
- 15.03.12 16:58:56.307 CH(17): RESPOND respond value='200 OK' reason 'call connected' rtp ip=192.168.100.30 port=30030,30031 payload=AMR:96
- 15.03.12 16:58:56.327 CH(16): RESPOND respond value=200
- 15.03.12 16:58:56.327 CH(16): Payload received rtp payload=AMR:96 payload=telephone-event:101
- 15.03.12 16:58:56.338 CH(15): MNCC_SETUP_RSP LCR<->BSC connected type=0 plan=1 present=0 screen=3 number=
- 15.03.12 16:58:56.338 CH(15): MNCC_LCHAN_MODIFY LCR<->BSC speech version='AMR given' mode 0x41
- 15.03.12 16:58:57.188 CH(15): MNCC_SETUP_COMPL_IND LCR<->BSC
- 15.03.12 16:59:05.404 CH(18): MNCC_DISC_IND LCR<->BSC cause coding=3 location=0 value=16
- 15.03.12 16:59:05.404 CH(18): MNCC_REL_REQ LCR<->BSC
- 15.03.12 16:59:05.404 CH(17): BYE cause value=16
- 15.03.12 16:59:05.425 CH(16): BYE
- 15.03.12 16:59:05.425 CH(16): RESPOND respond value='200 OK'
- 15.03.12 16:59:05.444 CH(15): MNCC_REL_REQ LCR<->BSC cause coding=3 location=10 value=16
- OpenBSC
- =======
- <0004> abis_rsl.c:578 (bts=0,trx=0,ts=2,ss=0) DEACTivate SACCH CMD
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- <0004> abis_rsl.c:967 (bts=0,trx=0,ts=2,ss=0): MEAS RES for inactive channel
- <0004> abis_rsl.c:967 (bts=0,trx=0,ts=3,ss=0): MEAS RES for inactive channel
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- received RTP frame with unknown payload type 98
- Yate
- ====
- <sip:INFO> 'udp:192.168.100.25:5060' received 709 bytes SIP message from 192.168.100.30:5060 [0x8fcf8a0]
- ------
- INVITE sip:0778899202@192.168.100.25 SIP/2.0
- Via: SIP/2.0/UDP 192.168.100.30;rport;branch=z9hG4bK6raaBZ8DaKHFm
- Max-Forwards: 70
- From: <sip:0778899201@192.168.100.30>;tag=Xr5N6ya6KZe1D
- To: <sip:0778899202@192.168.100.25>
- Call-ID: 73bc21b2-e935-122f-918d-0800273d5152
- CSeq: 25569524 INVITE
- Contact: <sip:192.168.100.30>
- User-Agent: sofia-sip/1.12.10
- Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, INFO
- Supported: timer, 100rel
- Min-SE: 120
- Content-Type: application/sdp
- Content-Length: 208
- v=0
- o=LCR-Sofia-SIP 0 0 IN IP4 192.168.100.30
- s=SIP Call
- c=IN IP4 192.168.100.30
- t=0 0
- m=audio 30032 RTP/AVP 96 97 3 98
- a=rtpmap:96 AMR/8000
- a=rtpmap:97 GSM-EFR/8000
- a=rtpmap:3 GSM/8000
- a=rtpmap:98 GSM-HR/8000
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' sending code 100 0x8fd9ab0 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 100 Trying
- Via: SIP/2.0/UDP 192.168.100.30;rport=5060;branch=z9hG4bK6raaBZ8DaKHFm;received=192.168.100.30
- From: <sip:0778899201@192.168.100.30>;tag=Xr5N6ya6KZe1D
- To: <sip:0778899202@192.168.100.25>
- Call-ID: 73bc21b2-e935-122f-918d-0800273d5152
- CSeq: 25569524 INVITE
- Server: Yate
- Content-Length: 0
- ------
- <INFO> Routing call to '0778899202' in context 'default' via 'sip/sip:0778899202@192.168.100.30' in 542 usec
- <sip:INFO> 'udp:192.168.100.25:5060' sending 'INVITE sip:0778899202@192.168.100.30' 0x8fd9810 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- INVITE sip:0778899202@192.168.100.30 SIP/2.0
- Max-Forwards: 19
- Via: SIP/2.0/UDP 192.168.100.25:5060;rport;branch=z9hG4bK1827813378
- From: <sip:0778899201@192.168.100.25>;tag=1572119568
- To: <sip:0778899202@192.168.100.30>
- Call-ID: 429880400@192.168.100.25
- CSeq: 9 INVITE
- User-Agent: Yate
- Contact: <sip:0778899201@192.168.100.25:5060>
- Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
- Content-Type: application/sdp
- Content-Length: 234
- v=0
- o=yate 1331811763 1331811763 IN IP4 192.168.100.30
- s=SIP Call
- c=IN IP4 192.168.100.30
- t=0 0
- m=audio 30032 RTP/AVP 96 3 101
- a=rtpmap:96 AMR/8000
- a=fmtp:96 octet-align=0
- a=rtpmap:3 GSM/8000
- a=rtpmap:101 telephone-event/8000
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' received 284 bytes SIP message from 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 100 Trying
- Via: SIP/2.0/UDP 192.168.100.25:5060;rport=5060;branch=z9hG4bK1827813378
- From: <sip:0778899201@192.168.100.25>;tag=1572119568
- To: <sip:0778899202@192.168.100.30>
- Call-ID: 429880400@192.168.100.25
- CSeq: 9 INVITE
- User-Agent: sofia-sip/1.12.10
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' received 440 bytes SIP message from 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 180 Ringing
- Via: SIP/2.0/UDP 192.168.100.25:5060;rport=5060;branch=z9hG4bK1827813378
- From: <sip:0778899201@192.168.100.25>;tag=1572119568
- To: <sip:0778899202@192.168.100.30>;tag=y1ye8SU9g84KS
- Call-ID: 429880400@192.168.100.25
- CSeq: 9 INVITE
- Contact: <sip:192.168.100.30>
- User-Agent: sofia-sip/1.12.10
- Accept: application/sdp
- Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, INFO
- Supported: timer, 100rel
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' sending code 180 0x8fe6b30 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 180 Ringing
- Via: SIP/2.0/UDP 192.168.100.30;rport=5060;branch=z9hG4bK6raaBZ8DaKHFm;received=192.168.100.30
- From: <sip:0778899201@192.168.100.30>;tag=Xr5N6ya6KZe1D
- To: <sip:0778899202@192.168.100.25>;tag=1654589846
- Call-ID: 73bc21b2-e935-122f-918d-0800273d5152
- CSeq: 25569524 INVITE
- Server: Yate
- Contact: <sip:0778899202@192.168.100.25:5060>
- Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' received 587 bytes SIP message from 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 200 OK
- Via: SIP/2.0/UDP 192.168.100.25:5060;rport=5060;branch=z9hG4bK1827813378
- From: <sip:0778899201@192.168.100.25>;tag=1572119568
- To: <sip:0778899202@192.168.100.30>;tag=y1ye8SU9g84KS
- Call-ID: 429880400@192.168.100.25
- CSeq: 9 INVITE
- Contact: <sip:192.168.100.30>
- User-Agent: sofia-sip/1.12.10
- Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, INFO
- Supported: timer, 100rel
- Min-SE: 120
- Content-Type: application/sdp
- Content-Length: 131
- v=0
- o=LCR-Sofia-SIP 0 0 IN IP4 192.168.100.30
- s=SIP Call
- c=IN IP4 192.168.100.30
- t=0 0
- m=audio 30036 RTP/AVP 96
- a=rtpmap:96 AMR/8000
- ------
- <INFO> Choosing offered 'audio' format 'amr' [0x8ff2168]
- <sip:INFO> 'udp:192.168.100.25:5060' sending 'ACK sip:192.168.100.30' 0x8fe6a60 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- ACK sip:192.168.100.30 SIP/2.0
- Via: SIP/2.0/UDP 192.168.100.25:5060;rport;branch=z9hG4bK1790740462
- From: <sip:0778899201@192.168.100.25>;tag=1572119568
- To: <sip:0778899202@192.168.100.30>;tag=y1ye8SU9g84KS
- Call-ID: 429880400@192.168.100.25
- CSeq: 9 ACK
- Max-Forwards: 19
- Contact: <sip:0778899201@192.168.100.25:5060>
- User-Agent: Yate
- Content-Length: 0
- ------
- <INFO> Choosing offered 'audio' format 'amr' [0x8fe7648]
- <sip:NOTE> Formats for 'audio' changed to 'amr' [0x8fe4554]
- <sip:INFO> 'udp:192.168.100.25:5060' sending code 200 0x8fea120 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 200 OK
- Via: SIP/2.0/UDP 192.168.100.30;rport=5060;branch=z9hG4bK6raaBZ8DaKHFm;received=192.168.100.30
- From: <sip:0778899201@192.168.100.30>;tag=Xr5N6ya6KZe1D
- To: <sip:0778899202@192.168.100.25>;tag=1654589846
- Call-ID: 73bc21b2-e935-122f-918d-0800273d5152
- CSeq: 25569524 INVITE
- Server: Yate
- Contact: <sip:0778899202@192.168.100.25:5060>
- Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
- Content-Type: application/sdp
- Content-Length: 211
- v=0
- o=yate 1331811771 1331811771 IN IP4 192.168.100.30
- s=SIP Call
- c=IN IP4 192.168.100.30
- t=0 0
- m=audio 30036 RTP/AVP 96 101
- a=rtpmap:96 AMR/8000
- a=fmtp:96 octet-align=0
- a=rtpmap:101 telephone-event/8000
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' received 326 bytes SIP message from 192.168.100.30:5060 [0x8fcf8a0]
- ------
- ACK sip:0778899202@192.168.100.25:5060 SIP/2.0
- Via: SIP/2.0/UDP 192.168.100.30;rport;branch=z9hG4bK7132ctSH7U71F
- Max-Forwards: 70
- From: <sip:0778899201@192.168.100.30>;tag=Xr5N6ya6KZe1D
- To: <sip:0778899202@192.168.100.25>;tag=1654589846
- Call-ID: 73bc21b2-e935-122f-918d-0800273d5152
- CSeq: 25569524 ACK
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' received 478 bytes SIP message from 192.168.100.30:5060 [0x8fcf8a0]
- ------
- BYE sip:0778899201@192.168.100.25:5060 SIP/2.0
- Via: SIP/2.0/UDP 192.168.100.30;rport;branch=z9hG4bK8aXUeNaN44XmB
- Max-Forwards: 70
- From: <sip:0778899202@192.168.100.30>;tag=y1ye8SU9g84KS
- To: <sip:0778899201@192.168.100.25>;tag=1572119568
- Call-ID: 429880400@192.168.100.25
- CSeq: 25569530 BYE
- User-Agent: sofia-sip/1.12.10
- Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, INFO
- Supported: timer, 100rel
- Reason: Q.850;cause=16;text="Normal call clearing"
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' sending code 100 0x8fd8f38 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 100 Trying
- Via: SIP/2.0/UDP 192.168.100.30;rport=5060;branch=z9hG4bK8aXUeNaN44XmB;received=192.168.100.30
- From: <sip:0778899202@192.168.100.30>;tag=y1ye8SU9g84KS
- To: <sip:0778899201@192.168.100.25>;tag=1572119568
- Call-ID: 429880400@192.168.100.25
- CSeq: 25569530 BYE
- Server: Yate
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' sending code 200 0x8fe6b30 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 200 OK
- Via: SIP/2.0/UDP 192.168.100.30;rport=5060;branch=z9hG4bK8aXUeNaN44XmB;received=192.168.100.30
- From: <sip:0778899202@192.168.100.30>;tag=y1ye8SU9g84KS
- To: <sip:0778899201@192.168.100.25>;tag=1572119568
- Call-ID: 429880400@192.168.100.25
- CSeq: 25569530 BYE
- Server: Yate
- Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' sending 'BYE sip:192.168.100.30' 0x8fd8f38 to 192.168.100.30:5060 [0x8fcf8a0]
- ------
- BYE sip:192.168.100.30 SIP/2.0
- Call-ID: 73bc21b2-e935-122f-918d-0800273d5152
- From: <sip:0778899202@192.168.100.25>;tag=1654589846
- To: <sip:0778899201@192.168.100.30>;tag=Xr5N6ya6KZe1D
- Reason: SIP;text="Normal call clearing"
- Via: SIP/2.0/UDP 192.168.100.25:5060;rport;branch=z9hG4bK54387627
- CSeq: 10 BYE
- User-Agent: Yate
- Max-Forwards: 70
- Allow: ACK, INVITE, BYE, CANCEL, REGISTER, REFER, OPTIONS, INFO
- Content-Length: 0
- ------
- <sip:INFO> 'udp:192.168.100.25:5060' received 389 bytes SIP message from 192.168.100.30:5060 [0x8fcf8a0]
- ------
- SIP/2.0 200 OK
- Via: SIP/2.0/UDP 192.168.100.25:5060;rport=5060;branch=z9hG4bK54387627
- From: <sip:0778899202@192.168.100.25>;tag=1654589846
- To: <sip:0778899201@192.168.100.30>;tag=Xr5N6ya6KZe1D
- Call-ID: 73bc21b2-e935-122f-918d-0800273d5152
- CSeq: 10 BYE
- User-Agent: sofia-sip/1.12.10
- Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, NOTIFY, INFO
- Supported: timer, 100rel
- Content-Length: 0
- ------
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement